[web] Publish Deployment Guide to draft documentation
dsilas
dsilas at fedoraproject.org
Mon Jul 19 20:51:14 UTC 2010
commit 22dd4670094eae9761d00d6328f020e604c03dab
Author: Douglas Silas <dhensley at redhat.com>
Date: Mon Jul 19 22:46:20 2010 +0200
Publish Deployment Guide to draft documentation
fedoradocs.db | Bin 350208 -> 352256 bytes
public_html/Sitemap | 24 +
public_html/as-IN/Site_Statistics.html | 4 +-
public_html/as-IN/toc.html | 15 +
public_html/bg-BG/Site_Statistics.html | 4 +-
public_html/bg-BG/toc.html | 15 +
public_html/bn-IN/Site_Statistics.html | 4 +-
public_html/bn-IN/toc.html | 15 +
public_html/bs-BA/Site_Statistics.html | 4 +-
public_html/bs-BA/toc.html | 15 +
public_html/ca-ES/Site_Statistics.html | 4 +-
public_html/ca-ES/toc.html | 15 +
public_html/cs-CZ/Site_Statistics.html | 4 +-
public_html/cs-CZ/toc.html | 15 +
public_html/da-DK/Site_Statistics.html | 4 +-
public_html/da-DK/toc.html | 15 +
public_html/de-DE/Site_Statistics.html | 4 +-
public_html/de-DE/toc.html | 15 +
public_html/el-GR/Site_Statistics.html | 4 +-
public_html/el-GR/toc.html | 15 +
...t_Documentation-0.1-Deployment_Guide-en-US.epub | Bin 0 -> 7701362 bytes
.../Deployment_Guide/Common_Content/css/common.css | 1467 ++
.../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 -> 690 bytes
.../Deployment_Guide/Common_Content/images/1.svg | 22 +
.../Deployment_Guide/Common_Content/images/10.png | Bin 0 -> 982 bytes
.../Deployment_Guide/Common_Content/images/10.svg | 22 +
.../Deployment_Guide/Common_Content/images/11.png | Bin 0 -> 806 bytes
.../Deployment_Guide/Common_Content/images/11.svg | 22 +
.../Deployment_Guide/Common_Content/images/12.png | Bin 0 -> 953 bytes
.../Deployment_Guide/Common_Content/images/12.svg | 22 +
.../Deployment_Guide/Common_Content/images/13.png | Bin 0 -> 1015 bytes
.../Deployment_Guide/Common_Content/images/13.svg | 22 +
.../Deployment_Guide/Common_Content/images/14.png | Bin 0 -> 933 bytes
.../Deployment_Guide/Common_Content/images/14.svg | 22 +
.../Deployment_Guide/Common_Content/images/15.png | Bin 0 -> 996 bytes
.../Deployment_Guide/Common_Content/images/15.svg | 22 +
.../Deployment_Guide/Common_Content/images/16.png | Bin 0 -> 1030 bytes
.../Deployment_Guide/Common_Content/images/16.svg | 22 +
.../Deployment_Guide/Common_Content/images/17.png | Bin 0 -> 870 bytes
.../Deployment_Guide/Common_Content/images/17.svg | 22 +
.../Deployment_Guide/Common_Content/images/18.png | Bin 0 -> 1001 bytes
.../Deployment_Guide/Common_Content/images/18.svg | 22 +
.../Deployment_Guide/Common_Content/images/19.png | Bin 0 -> 1013 bytes
.../Deployment_Guide/Common_Content/images/19.svg | 22 +
.../Deployment_Guide/Common_Content/images/2.png | Bin 0 -> 808 bytes
.../Deployment_Guide/Common_Content/images/2.svg | 22 +
.../Deployment_Guide/Common_Content/images/20.png | Bin 0 -> 1121 bytes
.../Deployment_Guide/Common_Content/images/20.svg | 22 +
.../Deployment_Guide/Common_Content/images/21.png | Bin 0 -> 981 bytes
.../Deployment_Guide/Common_Content/images/21.svg | 22 +
.../Deployment_Guide/Common_Content/images/22.png | Bin 0 -> 1057 bytes
.../Deployment_Guide/Common_Content/images/22.svg | 22 +
.../Deployment_Guide/Common_Content/images/23.png | Bin 0 -> 1120 bytes
.../Deployment_Guide/Common_Content/images/23.svg | 22 +
.../Deployment_Guide/Common_Content/images/3.png | Bin 0 -> 868 bytes
.../Deployment_Guide/Common_Content/images/3.svg | 22 +
.../Deployment_Guide/Common_Content/images/4.png | Bin 0 -> 794 bytes
.../Deployment_Guide/Common_Content/images/4.svg | 22 +
.../Deployment_Guide/Common_Content/images/5.png | Bin 0 -> 853 bytes
.../Deployment_Guide/Common_Content/images/5.svg | 22 +
.../Deployment_Guide/Common_Content/images/6.png | Bin 0 -> 865 bytes
.../Deployment_Guide/Common_Content/images/6.svg | 22 +
.../Deployment_Guide/Common_Content/images/7.png | Bin 0 -> 742 bytes
.../Deployment_Guide/Common_Content/images/7.svg | 22 +
.../Deployment_Guide/Common_Content/images/8.png | Bin 0 -> 862 bytes
.../Deployment_Guide/Common_Content/images/8.svg | 22 +
.../Deployment_Guide/Common_Content/images/9.png | Bin 0 -> 860 bytes
.../Deployment_Guide/Common_Content/images/9.svg | 22 +
.../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/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 +
.../Common_Content/images/redhat-logo.svg | 94 +
.../Common_Content/images/rhlogo.png | Bin 0 -> 2278 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
.../Deployment_Guide/images/ABRT-Main_Window.png | Bin 0 -> 70322 bytes
.../images/ABRT-Notification_Area_alarm_icon.png | Bin 0 -> 1009 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
.../Deployment_Guide/images/abrt_main.png | Bin 0 -> 45328 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
.../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
.../Deployment_Guide/images/genkey1.png | Bin 0 -> 9587 bytes
.../Deployment_Guide/images/genkey10.png | Bin 0 -> 16485 bytes
.../Deployment_Guide/images/genkey11.png | Bin 0 -> 7436 bytes
.../Deployment_Guide/images/genkey2.png | Bin 0 -> 10374 bytes
.../Deployment_Guide/images/genkey3.png | Bin 0 -> 18324 bytes
.../Deployment_Guide/images/genkey4.png | Bin 0 -> 6604 bytes
.../Deployment_Guide/images/genkey5.png | Bin 0 -> 9053 bytes
.../Deployment_Guide/images/genkey6.png | Bin 0 -> 12479 bytes
.../Deployment_Guide/images/genkey7.png | Bin 0 -> 17567 bytes
.../Deployment_Guide/images/genkey8.png | Bin 0 -> 10794 bytes
.../Deployment_Guide/images/genkey9.png | Bin 0 -> 11766 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 -> 23184 bytes
.../images/gnome-system-monitor-memory.png | Bin 0 -> 11217 bytes
.../images/gnome-system-monitor-processes.png | Bin 0 -> 14094 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
.../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
.../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-logviewer-add.png | Bin 0 -> 13899 bytes
.../images/redhat-logviewer-monitoring1.png | Bin 0 -> 20495 bytes
.../images/redhat-logviewer-monitoring2.png | Bin 0 -> 27489 bytes
.../images/redhat-logviewer-monitoring3.png | Bin 0 -> 26805 bytes
.../images/redhat-logviewer-prefs.png | Bin 0 -> 27983 bytes
.../images/redhat-logviewer-sample.png | Bin 0 -> 21035 bytes
.../Deployment_Guide/images/redhat-logviewer.png | Bin 0 -> 26264 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
.../0.1/html-single/Deployment_Guide/index.html |14583 ++++++++++++++++++++
.../html/Deployment_Guide/Acknowledgements.html | 5 +
.../Deployment_Guide/Common_Content/css/common.css | 1467 ++
.../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 -> 690 bytes
.../Deployment_Guide/Common_Content/images/1.svg | 22 +
.../Deployment_Guide/Common_Content/images/10.png | Bin 0 -> 982 bytes
.../Deployment_Guide/Common_Content/images/10.svg | 22 +
.../Deployment_Guide/Common_Content/images/11.png | Bin 0 -> 806 bytes
.../Deployment_Guide/Common_Content/images/11.svg | 22 +
.../Deployment_Guide/Common_Content/images/12.png | Bin 0 -> 953 bytes
.../Deployment_Guide/Common_Content/images/12.svg | 22 +
.../Deployment_Guide/Common_Content/images/13.png | Bin 0 -> 1015 bytes
.../Deployment_Guide/Common_Content/images/13.svg | 22 +
.../Deployment_Guide/Common_Content/images/14.png | Bin 0 -> 933 bytes
.../Deployment_Guide/Common_Content/images/14.svg | 22 +
.../Deployment_Guide/Common_Content/images/15.png | Bin 0 -> 996 bytes
.../Deployment_Guide/Common_Content/images/15.svg | 22 +
.../Deployment_Guide/Common_Content/images/16.png | Bin 0 -> 1030 bytes
.../Deployment_Guide/Common_Content/images/16.svg | 22 +
.../Deployment_Guide/Common_Content/images/17.png | Bin 0 -> 870 bytes
.../Deployment_Guide/Common_Content/images/17.svg | 22 +
.../Deployment_Guide/Common_Content/images/18.png | Bin 0 -> 1001 bytes
.../Deployment_Guide/Common_Content/images/18.svg | 22 +
.../Deployment_Guide/Common_Content/images/19.png | Bin 0 -> 1013 bytes
.../Deployment_Guide/Common_Content/images/19.svg | 22 +
.../Deployment_Guide/Common_Content/images/2.png | Bin 0 -> 808 bytes
.../Deployment_Guide/Common_Content/images/2.svg | 22 +
.../Deployment_Guide/Common_Content/images/20.png | Bin 0 -> 1121 bytes
.../Deployment_Guide/Common_Content/images/20.svg | 22 +
.../Deployment_Guide/Common_Content/images/21.png | Bin 0 -> 981 bytes
.../Deployment_Guide/Common_Content/images/21.svg | 22 +
.../Deployment_Guide/Common_Content/images/22.png | Bin 0 -> 1057 bytes
.../Deployment_Guide/Common_Content/images/22.svg | 22 +
.../Deployment_Guide/Common_Content/images/23.png | Bin 0 -> 1120 bytes
.../Deployment_Guide/Common_Content/images/23.svg | 22 +
.../Deployment_Guide/Common_Content/images/3.png | Bin 0 -> 868 bytes
.../Deployment_Guide/Common_Content/images/3.svg | 22 +
.../Deployment_Guide/Common_Content/images/4.png | Bin 0 -> 794 bytes
.../Deployment_Guide/Common_Content/images/4.svg | 22 +
.../Deployment_Guide/Common_Content/images/5.png | Bin 0 -> 853 bytes
.../Deployment_Guide/Common_Content/images/5.svg | 22 +
.../Deployment_Guide/Common_Content/images/6.png | Bin 0 -> 865 bytes
.../Deployment_Guide/Common_Content/images/6.svg | 22 +
.../Deployment_Guide/Common_Content/images/7.png | Bin 0 -> 742 bytes
.../Deployment_Guide/Common_Content/images/7.svg | 22 +
.../Deployment_Guide/Common_Content/images/8.png | Bin 0 -> 862 bytes
.../Deployment_Guide/Common_Content/images/8.svg | 22 +
.../Deployment_Guide/Common_Content/images/9.png | Bin 0 -> 860 bytes
.../Deployment_Guide/Common_Content/images/9.svg | 22 +
.../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/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 +
.../Common_Content/images/redhat-logo.svg | 94 +
.../Common_Content/images/rhlogo.png | Bin 0 -> 2278 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
.../Deployment_Guide/app-Revision_History.html | 9 +
.../ch-Authentication_Configuration.html | 421 +
.../html/Deployment_Guide/ch-Automated_Tasks.html | 76 +
.../html/Deployment_Guide/ch-Console_Access.html | 32 +
.../ch-Controlling_Access_to_Services.html | 57 +
...h-Dynamic_Host_Configuration_Protocol_DHCP.html | 9 +
.../0.1/html/Deployment_Guide/ch-FTP.html | 19 +
.../ch-Gathering_System_Information.html | 116 +
.../ch-General_Parameters_and_Modules.html | 93 +
...ackage_Management-sec-Additional_Resources.html | 9 +
.../ch-Keyboard_Configuration.html | 31 +
...Lightweight_Directory_Access_Protocol_LDAP.html | 31 +
.../0.1/html/Deployment_Guide/ch-Log_Files.html | 13 +
.../ch-Manually_Upgrading_the_Kernel.html | 60 +
.../Deployment_Guide/ch-Network_Configuration.html | 22 +
.../Deployment_Guide/ch-Network_Interfaces.html | 33 +
.../0.1/html/Deployment_Guide/ch-OProfile.html | 66 +
.../0.1/html/Deployment_Guide/ch-OpenSSH.html | 89 +
.../0.1/html/Deployment_Guide/ch-PackageKit.html | 44 +
.../Deployment_Guide/ch-Printer_Configuration.html | 47 +
.../0.1/html/Deployment_Guide/ch-RPM.html | 47 +
.../0.1/html/Deployment_Guide/ch-Samba.html | 41 +
.../ch-The_Apache_HTTP_Server.html | 31 +
.../Deployment_Guide/ch-The_BIND_DNS_Server.html | 45 +
.../Deployment_Guide/ch-The_X_Window_System.html | 27 +
.../ch-The_sysconfig_Directory.html | 243 +
.../0.1/html/Deployment_Guide/ch-abrt.html | 31 +
.../0.1/html/Deployment_Guide/ch-email.html | 84 +
.../0.1/html/Deployment_Guide/ch-intro.html | 41 +
.../0.1/html/Deployment_Guide/ch-proc.html | 58 +
.../0.1/html/Deployment_Guide/ch-yum.html | 95 +
.../0.1/html/Deployment_Guide/ch10s02s03.html | 32 +
.../0.1/html/Deployment_Guide/ch23s07s02.html | 11 +
.../0.1/html/Deployment_Guide/ch23s07s03.html | 9 +
.../0.1/html/Deployment_Guide/ch23s07s04.html | 19 +
.../0.1/html/Deployment_Guide/ch28s02.html | 22 +
.../0.1/html/Deployment_Guide/ch28s04.html | 10 +
.../0.1/html/Deployment_Guide/ch28s05.html | 25 +
.../0.1/html/Deployment_Guide/ch28s05s02.html | 17 +
.../0.1/html/Deployment_Guide/ch28s05s03.html | 5 +
.../chap-Date_and_Time_Configuration.html | 45 +
.../chap-SSSD_User_Guide-Configuring_Domains.html | 229 +
.../chap-SSSD_User_Guide-Configuring_Services.html | 57 +
.../chap-SSSD_User_Guide-Introduction.html | 11 +
.../chap-SSSD_User_Guide-Setting_Up_SSSD.html | 145 +
.../chap-SSSD_User_Guide-Troubleshooting.html | 105 +
.../0.1/html/Deployment_Guide/configuring.html | 37 +
.../html/Deployment_Guide/dhcp-relay-agent.html | 11 +
.../0.1/html/Deployment_Guide/ers_and_Groups.html | 73 +
.../Deployment_Guide/images/ABRT-Main_Window.png | Bin 0 -> 70322 bytes
.../images/ABRT-Notification_Area_alarm_icon.png | Bin 0 -> 1009 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
.../0.1/html/Deployment_Guide/images/PS2port.png | Bin 0 -> 574 bytes
.../0.1/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
.../0.1/html/Deployment_Guide/images/abrt_main.png | Bin 0 -> 45328 bytes
.../0.1/html/Deployment_Guide/images/apol-DIF.png | Bin 0 -> 8924 bytes
.../images/apol-TE-rule-search.png | Bin 0 -> 8384 bytes
.../html/Deployment_Guide/images/apol-plain.png | Bin 0 -> 6980 bytes
.../0.1/html/Deployment_Guide/images/arrow.png | Bin 0 -> 117 bytes
.../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
.../0.1/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
.../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
.../html/Deployment_Guide/images/flask-arch.png | Bin 0 -> 4352 bytes
.../html/Deployment_Guide/images/flow-diagram.png | Bin 0 -> 29692 bytes
.../0.1/html/Deployment_Guide/images/genkey1.png | Bin 0 -> 9587 bytes
.../0.1/html/Deployment_Guide/images/genkey10.png | Bin 0 -> 16485 bytes
.../0.1/html/Deployment_Guide/images/genkey11.png | Bin 0 -> 7436 bytes
.../0.1/html/Deployment_Guide/images/genkey2.png | Bin 0 -> 10374 bytes
.../0.1/html/Deployment_Guide/images/genkey3.png | Bin 0 -> 18324 bytes
.../0.1/html/Deployment_Guide/images/genkey4.png | Bin 0 -> 6604 bytes
.../0.1/html/Deployment_Guide/images/genkey5.png | Bin 0 -> 9053 bytes
.../0.1/html/Deployment_Guide/images/genkey6.png | Bin 0 -> 12479 bytes
.../0.1/html/Deployment_Guide/images/genkey7.png | Bin 0 -> 17567 bytes
.../0.1/html/Deployment_Guide/images/genkey8.png | Bin 0 -> 10794 bytes
.../0.1/html/Deployment_Guide/images/genkey9.png | Bin 0 -> 11766 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 -> 23184 bytes
.../images/gnome-system-monitor-memory.png | Bin 0 -> 11217 bytes
.../images/gnome-system-monitor-processes.png | Bin 0 -> 14094 bytes
.../0.1/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
.../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
.../0.1/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
.../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
.../0.1/html/Deployment_Guide/images/lvg.png | Bin 0 -> 27939 bytes
.../Deployment_Guide/images/lvm-auto-config.png | Bin 0 -> 25658 bytes
.../0.1/html/Deployment_Guide/images/lvm-main1.png | Bin 0 -> 9761 bytes
.../html/Deployment_Guide/images/lvm-main10.png | Bin 0 -> 8497 bytes
.../html/Deployment_Guide/images/lvm-main12.png | Bin 0 -> 8161 bytes
.../html/Deployment_Guide/images/lvm-main13.png | Bin 0 -> 12158 bytes
.../html/Deployment_Guide/images/lvm-main14.png | Bin 0 -> 13559 bytes
.../html/Deployment_Guide/images/lvm-main15.png | Bin 0 -> 14775 bytes
.../html/Deployment_Guide/images/lvm-main16.png | Bin 0 -> 9029 bytes
.../html/Deployment_Guide/images/lvm-main17.png | Bin 0 -> 16327 bytes
.../html/Deployment_Guide/images/lvm-main18.png | Bin 0 -> 12662 bytes
.../0.1/html/Deployment_Guide/images/lvm-main2.png | Bin 0 -> 10383 bytes
.../html/Deployment_Guide/images/lvm-main21.png | Bin 0 -> 11896 bytes
.../html/Deployment_Guide/images/lvm-main23.png | Bin 0 -> 15371 bytes
.../html/Deployment_Guide/images/lvm-main26.png | Bin 0 -> 12412 bytes
.../html/Deployment_Guide/images/lvm-main27.png | Bin 0 -> 17553 bytes
.../html/Deployment_Guide/images/lvm-main28.png | Bin 0 -> 14745 bytes
.../0.1/html/Deployment_Guide/images/lvm-main3.png | Bin 0 -> 10968 bytes
.../html/Deployment_Guide/images/lvm-main30.png | Bin 0 -> 10820 bytes
.../html/Deployment_Guide/images/lvm-main31.png | Bin 0 -> 11317 bytes
.../html/Deployment_Guide/images/lvm-main32.png | Bin 0 -> 23900 bytes
.../html/Deployment_Guide/images/lvm-main33.png | Bin 0 -> 24557 bytes
.../html/Deployment_Guide/images/lvm-main34.png | Bin 0 -> 17170 bytes
.../html/Deployment_Guide/images/lvm-main36.png | Bin 0 -> 18375 bytes
.../0.1/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
.../0.1/html/Deployment_Guide/images/lvm/lvg.svg | 684 +
.../0.1/html/Deployment_Guide/images/lvm/lvols.svg | 286 +
.../0.1/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
.../0.1/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
.../html/Deployment_Guide/images/neat-hosts.png | Bin 0 -> 14239 bytes
.../Deployment_Guide/images/neat-isdn-settings.png | Bin 0 -> 14132 bytes
.../0.1/html/Deployment_Guide/images/neat-isdn.png | Bin 0 -> 18341 bytes
.../images/neat-modem-settings.png | Bin 0 -> 14411 bytes
.../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
.../0.1/html/Deployment_Guide/images/neat-xdsl.png | Bin 0 -> 18410 bytes
.../0.1/html/Deployment_Guide/images/neat.png | Bin 0 -> 19286 bytes
.../0.1/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
.../0.1/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-logviewer-add.png | Bin 0 -> 13899 bytes
.../images/redhat-logviewer-monitoring1.png | Bin 0 -> 20495 bytes
.../images/redhat-logviewer-monitoring2.png | Bin 0 -> 27489 bytes
.../images/redhat-logviewer-monitoring3.png | Bin 0 -> 26805 bytes
.../images/redhat-logviewer-prefs.png | Bin 0 -> 27983 bytes
.../images/redhat-logviewer-sample.png | Bin 0 -> 21035 bytes
.../Deployment_Guide/images/redhat-logviewer.png | Bin 0 -> 26264 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
.../0.1/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
.../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
.../0.1/html/Deployment_Guide/images/usbport.png | Bin 0 -> 277 bytes
.../0.1/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
.../0.1/html/Deployment_Guide/images/your-rhn.png | Bin 0 -> 20572 bytes
.../0.1/html/Deployment_Guide/index.html | 26 +
.../0.1/html/Deployment_Guide/ix01.html | 3 +
.../0.1/html/Deployment_Guide/lease-database.html | 11 +
.../0.1/html/Deployment_Guide/pr01.html | 88 +
.../Deployment_Guide/pt-kernel-configuration.html | 5 +
.../pt-network-related-config.html | 5 +
.../html/Deployment_Guide/pt-pkg-management.html | 5 +
.../0.1/html/Deployment_Guide/pt-sysconfig.html | 5 +
.../Deployment_Guide/pt-system-monitoring.html | 5 +
.../Deployment_Guide/s1-access-console-define.html | 11 +
.../Deployment_Guide/s1-access-console-enable.html | 33 +
.../Deployment_Guide/s1-access-console-files.html | 25 +
.../s1-access-console-program.html | 13 +
.../html/Deployment_Guide/s1-access-floppy.html | 9 +
.../s1-apache-additional-resources.html | 11 +
.../html/Deployment_Guide/s1-apache-addmods.html | 23 +
.../html/Deployment_Guide/s1-apache-config-ui.html | 45 +
.../html/Deployment_Guide/s1-apache-config.html | 327 +
.../html/Deployment_Guide/s1-apache-startstop.html | 43 +
.../Deployment_Guide/s1-apache-virtualhosts.html | 36 +
.../s1-autotasks-additional-resources.html | 13 +
.../Deployment_Guide/s1-autotasks-at-batch.html | 35 +
.../s1-bind-additional-resources.html | 29 +
.../html/Deployment_Guide/s1-bind-features.html | 13 +
.../html/Deployment_Guide/s1-bind-mistakes.html | 27 +
.../html/Deployment_Guide/s1-bind-namedconf.html | 193 +
.../0.1/html/Deployment_Guide/s1-bind-rndc.html | 35 +
.../0.1/html/Deployment_Guide/s1-bind-zone.html | 31 +
.../html/Deployment_Guide/s1-check-rpm-sig.html | 31 +
.../s1-dhcp-additional-resources.html | 17 +
.../s1-dhcp-configuring-client.html | 27 +
.../s1-dhcp-configuring-server.html | 116 +
.../Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.html | 19 +
.../s1-email-additional-resources.html | 29 +
.../0.1/html/Deployment_Guide/s1-email-mda.html | 58 +
.../0.1/html/Deployment_Guide/s1-email-mta.html | 120 +
.../0.1/html/Deployment_Guide/s1-email-mua.html | 59 +
.../html/Deployment_Guide/s1-email-switchmail.html | 9 +
.../0.1/html/Deployment_Guide/s1-email-types.html | 15 +
.../html/Deployment_Guide/s1-ftp-resources.html | 15 +
.../0.1/html/Deployment_Guide/s1-ftp-servers.html | 29 +
.../html/Deployment_Guide/s1-ftp-vsftpd-conf.html | 35 +
.../html/Deployment_Guide/s1-ftp-vsftpd-start.html | 61 +
.../0.1/html/Deployment_Guide/s1-httpd-mig.html | 15 +
.../Deployment_Guide/s1-httpd-secure-server.html | 23 +
.../Deployment_Guide/s1-kernel-boot-loader.html | 98 +
.../html/Deployment_Guide/s1-kernel-download.html | 17 +
.../s1-kernel-modules-additional-resources.html | 14 +
.../s1-kernel-modules-persistant.html | 18 +
.../s1-kernel-perform-upgrade.html | 14 +
.../html/Deployment_Guide/s1-kernel-preparing.html | 64 +
.../html/Deployment_Guide/s1-keyboard-break.html | 13 +
.../Deployment_Guide/s1-keyboard-indicator.html | 15 +
.../s1-ldap-additional-resources.html | 41 +
.../Deployment_Guide/s1-ldap-daemonsutils.html | 71 +
.../Deployment_Guide/s1-ldap-files-schemas.html | 22 +
.../0.1/html/Deployment_Guide/s1-ldap-files.html | 13 +
.../0.1/html/Deployment_Guide/s1-ldap-migrate.html | 11 +
.../0.1/html/Deployment_Guide/s1-ldap-pam.html | 31 +
.../html/Deployment_Guide/s1-ldap-quickstart.html | 51 +
.../html/Deployment_Guide/s1-ldap-terminology.html | 26 +
.../html/Deployment_Guide/s1-logfiles-adding.html | 11 +
.../Deployment_Guide/s1-logfiles-examining.html | 15 +
.../html/Deployment_Guide/s1-logfiles-viewing.html | 19 +
.../html/Deployment_Guide/s1-modules-ethernet.html | 386 +
.../s1-modules-parameters-specifying.html | 11 +
.../0.1/html/Deployment_Guide/s1-modules-scsi.html | 268 +
.../s1-networkscripts-control.html | 49 +
.../s1-networkscripts-functions.html | 9 +
.../s1-networkscripts-interfaces.html | 100 +
.../s1-networkscripts-resources.html | 9 +
.../s1-networkscripts-static-routes.html | 62 +
.../s1-openssh-additional-resources.html | 19 +
.../s1-oprofile-additional-resources.html | 9 +
.../s1-oprofile-analyzing-data.html | 56 +
.../Deployment_Guide/s1-oprofile-configuring.html | 23 +
.../Deployment_Guide/s1-oprofile-dev-oprofile.html | 27 +
.../s1-oprofile-example-usage.html | 9 +
.../0.1/html/Deployment_Guide/s1-oprofile-gui.html | 31 +
.../Deployment_Guide/s1-oprofile-saving-data.html | 11 +
.../Deployment_Guide/s1-oprofile-starting.html | 17 +
.../s1-printing-additional-resources.html | 17 +
.../html/Deployment_Guide/s1-printing-edit.html | 13 +
.../Deployment_Guide/s1-printing-ipp-printer.html | 17 +
.../s1-printing-jetdirect-printer.html | 19 +
.../Deployment_Guide/s1-printing-managing.html | 20 +
.../Deployment_Guide/s1-printing-select-model.html | 23 +
.../Deployment_Guide/s1-printing-smb-printer.html | 29 +
.../Deployment_Guide/s1-printing-test-page.html | 7 +
.../s1-proc-additional-resources.html | 17 +
.../html/Deployment_Guide/s1-proc-directories.html | 112 +
.../0.1/html/Deployment_Guide/s1-proc-sysctl.html | 24 +
.../html/Deployment_Guide/s1-proc-topfiles.html | 17 +
.../s1-rpm-additional-resources.html | 9 +
.../html/Deployment_Guide/s1-rpm-impressing.html | 81 +
.../0.1/html/Deployment_Guide/s1-rpm-using.html | 25 +
.../s1-samba-account-info-dbs.html | 27 +
.../Deployment_Guide/s1-samba-configuring.html | 83 +
.../Deployment_Guide/s1-samba-connect-share.html | 31 +
.../0.1/html/Deployment_Guide/s1-samba-cups.html | 33 +
.../html/Deployment_Guide/s1-samba-daemons.html | 21 +
.../html/Deployment_Guide/s1-samba-mounting.html | 11 +
.../s1-samba-network-browsing.html | 13 +
.../html/Deployment_Guide/s1-samba-programs.html | 200 +
.../html/Deployment_Guide/s1-samba-resources.html | 9 +
.../Deployment_Guide/s1-samba-security-modes.html | 48 +
.../html/Deployment_Guide/s1-samba-servers.html | 86 +
.../html/Deployment_Guide/s1-samba-startstop.html | 33 +
.../Deployment_Guide/s1-secureserver-oldcert.html | 32 +
.../s1-services-additional-resources.html | 11 +
.../Deployment_Guide/s1-services-configuring.html | 80 +
.../html/Deployment_Guide/s1-services-running.html | 32 +
.../html/Deployment_Guide/s1-ssh-beyondshell.html | 16 +
.../0.1/html/Deployment_Guide/s1-ssh-clients.html | 28 +
.../Deployment_Guide/s1-ssh-configuration.html | 90 +
.../s1-sysconfig-additional-resources.html | 7 +
.../s1-sysconfig-etcsysconf-dir.html | 29 +
.../s1-sysinfo-additional-resources.html | 20 +
.../Deployment_Guide/s1-sysinfo-filesystems.html | 15 +
.../html/Deployment_Guide/s1-sysinfo-hardware.html | 17 +
.../Deployment_Guide/s1-sysinfo-memory-usage.html | 11 +
.../0.1/html/Deployment_Guide/s1-use-new-key.html | 16 +
.../s1-users-groups-additional-resources.html | 37 +
.../s1-users-groups-private-groups.html | 38 +
.../s1-users-groups-shadow-utilities.html | 25 +
.../s1-users-groups-standard-groups.html | 322 +
.../s1-users-groups-standard-users.html | 514 +
.../0.1/html/Deployment_Guide/s1-users-tools.html | 194 +
.../s1-x-additional-resources.html | 11 +
.../0.1/html/Deployment_Guide/s1-x-clients.html | 19 +
.../0.1/html/Deployment_Guide/s1-x-fonts.html | 41 +
.../0.1/html/Deployment_Guide/s1-x-runlevels.html | 21 +
.../s1-x-server-configuration.html | 266 +
.../Deployment_Guide/s2-apache-mpm-containers.html | 25 +
.../Deployment_Guide/s2-apache-sslcommands.html | 15 +
.../s2-autotasks-at-batch-controlling-access.html | 11 +
.../s2-autotasks-at-batch-service.html | 5 +
.../s2-autotasks-at-batch-viewing.html | 5 +
.../s2-autotasks-batch-configuring.html | 13 +
.../s2-autotasks-commandline-options.html | 21 +
.../s2-bind-configuration-zone-reverse.html | 43 +
.../Deployment_Guide/s2-bind-features-ipv6.html | 7 +
.../s2-bind-features-security.html | 17 +
.../Deployment_Guide/s2-bind-features-views.html | 9 +
.../Deployment_Guide/s2-bind-namedconf-comm.html | 11 +
.../s2-bind-namedconf-state-other.html | 35 +
.../Deployment_Guide/s2-bind-related-books.html | 7 +
.../s2-bind-rndc-configuration-rndcconf.html | 29 +
.../Deployment_Guide/s2-bind-rndc-options.html | 34 +
.../Deployment_Guide/s2-bind-useful-websites.html | 7 +
.../Deployment_Guide/s2-bind-zone-examples.html | 58 +
.../Deployment_Guide/s2-email-mta-fetchmail.html | 105 +
.../Deployment_Guide/s2-email-mta-postfix.html | 55 +
.../s2-email-procmail-recipes.html | 137 +
.../Deployment_Guide/s2-email-related-books.html | 13 +
.../html/Deployment_Guide/s2-email-types-mda.html | 7 +
.../html/Deployment_Guide/s2-email-types-mua.html | 7 +
.../Deployment_Guide/s2-email-useful-websites.html | 19 +
.../Deployment_Guide/s2-ftp-useful-websites.html | 9 +
.../s2-ftp-vsftpd-conf-opt-anon.html | 35 +
.../s2-ftp-vsftpd-conf-opt-dir.html | 33 +
.../s2-ftp-vsftpd-conf-opt-file.html | 21 +
.../s2-ftp-vsftpd-conf-opt-log.html | 39 +
.../s2-ftp-vsftpd-conf-opt-login.html | 55 +
.../s2-ftp-vsftpd-conf-opt-net.html | 87 +
.../s2-ftp-vsftpd-conf-opt-usr.html | 49 +
.../html/Deployment_Guide/s2-ftp-vsftpd-conf.html | 17 +
.../s2-httpd-default-settings.html | 139 +
.../s2-kernel-boot-loader-iseries.html | 16 +
.../s2-kernel-boot-loader-pseries.html | 20 +
.../html/Deployment_Guide/s2-keys-checking.html | 11 +
.../s2-ldap-additional-resources-web.html | 11 +
.../Deployment_Guide/s2-ldap-applications.html | 7 +
.../0.1/html/Deployment_Guide/s2-ldap-migrate.html | 63 +
.../html/Deployment_Guide/s2-ldap-other-apps.html | 11 +
.../Deployment_Guide/s2-ldap-related-books.html | 9 +
.../html/Deployment_Guide/s2-modules-bonding.html | 193 +
.../s2-networkscripts-interfaces-alias.html | 21 +
.../s2-networkscripts-interfaces-chan.html | 36 +
.../s2-networkscripts-interfaces-other.html | 13 +
.../s2-networkscripts-interfaces-ppp0.html | 67 +
.../s2-openssh-useful-websites.html | 9 +
.../html/Deployment_Guide/s2-oprofile-events.html | 172 +
.../s2-oprofile-module-output.html | 43 +
.../s2-oprofile-reading-opannotate.html | 13 +
.../s2-oprofile-reading-opreport-single.html | 29 +
.../s2-oprofile-starting-separate.html | 37 +
.../s2-oprofile-useful-websites.html | 5 +
.../s2-printing-useful-websites.html | 7 +
.../0.1/html/Deployment_Guide/s2-proc-cmdline.html | 15 +
.../0.1/html/Deployment_Guide/s2-proc-cpuinfo.html | 41 +
.../0.1/html/Deployment_Guide/s2-proc-crypto.html | 16 +
.../0.1/html/Deployment_Guide/s2-proc-devices.html | 42 +
.../0.1/html/Deployment_Guide/s2-proc-dir-bus.html | 27 +
.../html/Deployment_Guide/s2-proc-dir-driver.html | 25 +
.../0.1/html/Deployment_Guide/s2-proc-dir-fs.html | 5 +
.../0.1/html/Deployment_Guide/s2-proc-dir-irq.html | 11 +
.../0.1/html/Deployment_Guide/s2-proc-dir-net.html | 47 +
.../html/Deployment_Guide/s2-proc-dir-scsi.html | 90 +
.../0.1/html/Deployment_Guide/s2-proc-dir-sys.html | 326 +
.../html/Deployment_Guide/s2-proc-dir-sysvipc.html | 5 +
.../0.1/html/Deployment_Guide/s2-proc-dma.html | 7 +
.../html/Deployment_Guide/s2-proc-execdomains.html | 9 +
.../0.1/html/Deployment_Guide/s2-proc-fb.html | 7 +
.../html/Deployment_Guide/s2-proc-filesystems.html | 31 +
.../html/Deployment_Guide/s2-proc-interrupts.html | 43 +
.../0.1/html/Deployment_Guide/s2-proc-iomem.html | 23 +
.../0.1/html/Deployment_Guide/s2-proc-ioports.html | 31 +
.../0.1/html/Deployment_Guide/s2-proc-kcore.html | 9 +
.../0.1/html/Deployment_Guide/s2-proc-kmsg.html | 5 +
.../0.1/html/Deployment_Guide/s2-proc-loadavg.html | 11 +
.../0.1/html/Deployment_Guide/s2-proc-locks.html | 17 +
.../0.1/html/Deployment_Guide/s2-proc-mdstat.html | 15 +
.../0.1/html/Deployment_Guide/s2-proc-meminfo.html | 81 +
.../0.1/html/Deployment_Guide/s2-proc-misc.html | 9 +
.../0.1/html/Deployment_Guide/s2-proc-modules.html | 34 +
.../0.1/html/Deployment_Guide/s2-proc-mounts.html | 23 +
.../0.1/html/Deployment_Guide/s2-proc-mtrr.html | 14 +
.../html/Deployment_Guide/s2-proc-partitions.html | 22 +
.../0.1/html/Deployment_Guide/s2-proc-pci.html | 20 +
.../0.1/html/Deployment_Guide/s2-proc-pid.html | 51 +
.../html/Deployment_Guide/s2-proc-slabinfo.html | 60 +
.../0.1/html/Deployment_Guide/s2-proc-stat.html | 42 +
.../0.1/html/Deployment_Guide/s2-proc-swaps.html | 10 +
.../Deployment_Guide/s2-proc-sysrq-trigger.html | 7 +
.../0.1/html/Deployment_Guide/s2-proc-tty.html | 23 +
.../0.1/html/Deployment_Guide/s2-proc-uptime.html | 9 +
.../0.1/html/Deployment_Guide/s2-proc-version.html | 9 +
.../s2-redhat-config-users-process.html | 66 +
.../html/Deployment_Guide/s2-rpm-freshening.html | 17 +
.../0.1/html/Deployment_Guide/s2-rpm-querying.html | 29 +
.../Deployment_Guide/s2-rpm-related-books.html | 7 +
.../html/Deployment_Guide/s2-rpm-uninstalling.html | 20 +
.../Deployment_Guide/s2-rpm-useful-websites.html | 7 +
.../html/Deployment_Guide/s2-rpm-verifying.html | 45 +
.../s2-samba-configuring-cmdline.html | 25 +
.../s2-samba-domain-controller.html | 57 +
.../Deployment_Guide/s2-samba-domain-member.html | 61 +
.../s2-samba-encrypted-passwords.html | 5 +
.../s2-samba-resources-community.html | 11 +
.../s2-samba-resources-published.html | 9 +
.../Deployment_Guide/s2-samba-share-level.html | 12 +
.../0.1/html/Deployment_Guide/s2-samba-wins.html | 14 +
.../Deployment_Guide/s2-secureserver-certs.html | 38 +
.../s2-secureserver-generatingkey.html | 62 +
.../s2-secureserver-overview-certs.html | 15 +
.../s2-services-additional-resources-books.html | 5 +
.../Deployment_Guide/s2-services-chkconfig.html | 55 +
.../html/Deployment_Guide/s2-services-ntsysv.html | 34 +
.../Deployment_Guide/s2-ssh-beyondshell-tcpip.html | 25 +
.../html/Deployment_Guide/s2-ssh-clients-scp.html | 23 +
.../html/Deployment_Guide/s2-ssh-clients-sftp.html | 44 +
.../s2-ssh-configuration-keypairs.html | 143 +
.../s2-ssh-configuration-requiring.html | 12 +
.../s2-ssh-configuration-sshd.html | 22 +
.../Deployment_Guide/s2-x-clients-winmanagers.html | 29 +
.../0.1/html/Deployment_Guide/s2-x-fonts-core.html | 51 +
.../html/Deployment_Guide/s2-x-runlevels-5.html | 27 +
.../Deployment_Guide/s2-x-useful-websites.html | 11 +
.../0.1/html/Deployment_Guide/s3-bind-zone-rr.html | 131 +
.../0.1/html/Deployment_Guide/s3-httpd-v2-mig.html | 343 +
.../Deployment_Guide/sec-Additional_Resources.html | 7 +
.../sec-Configuration_File_Changes.html | 17 +
.../sec-Configuring_Connection_Settings.html | 60 +
.../sec-Configuring_IPv4_Settings.html | 33 +
.../sec-Configuring_IPv6_Settings.html | 19 +
...uring_New_and_Editing_Existing_Connections.html | 14 +
...ec-Configuring_PPP_Point-to-Point_Settings.html | 10 +
.../sec-Configuring_Wireless_Security.html | 18 +
.../sec-Configuring_Yum_and_Yum_Repositories.html | 97 +
.../sec-Connecting_to_a_Network_Automatically.html | 13 +
.../sec-Creating_a_Yum_Repository.html | 15 +
.../sec-Establishing_Connections.html | 51 +
.../Deployment_Guide/sec-Establishing_Routes.html | 15 +
.../sec-Establishing_a_DSL_Connection.html | 7 +
...Establishing_a_Mobile_Broadband_Connection.html | 80 +
.../sec-Establishing_a_VPN_Connection.html | 53 +
.../sec-Establishing_a_Wireless_Connection.html | 94 +
.../sec-Finding_Packages_with_Filters.html | 51 +
.../0.1/html/Deployment_Guide/sec-Installing.html | 57 +
.../sec-Installing_More_Yum_Plugins.html | 7 +
...sec-Installing_and_Removing_Package_Groups.html | 9 +
...ing_and_Removing_Packages_and_Dependencies.html | 24 +
.../sec-Installing_and_Upgrading.html | 83 +
.../sec-Interacting_with_NetworkManager.html | 26 +
.../sec-NetworkManager_Architecture.html | 5 +
.../sec-PackageKit_Architecture.html | 87 +
.../sec-Packages_and_Package_Groups.html | 128 +
.../Deployment_Guide/sec-Plugin_Descriptions.html | 38 +
.../0.1/html/Deployment_Guide/sec-Removing.html | 31 +
.../sec-Setting_repository_Options.html | 39 +
.../sec-User_and_System_Connections.html | 27 +
.../sec-Using_Add_Remove_Software.html | 20 +
.../Deployment_Guide/sec-Using_Yum_Variables.html | 13 +
.../sec-Verifying_the_Initial_RAM_Disk_Image.html | 67 +
.../sec-Viewing_the_Transaction_Log.html | 14 +
.../0.1/html/Deployment_Guide/sec-Yum_Plugins.html | 33 +
.../sect-Configuring_a_Multihomed_DHCP_Server.html | 124 +
...d_Line_Configuration-Network_Time_Protocol.html | 42 +
...e_Configuration-Command_Line_Configuration.html | 21 +
.../sect-RedHat-We_Need_Feedback.html | 21 +
...Domains-Setting_up_Kerberos_Authentication.html | 30 +
...SSSD_User_Guide-Introduction-SSSD_Features.html | 31 +
...ation_Files-SSSD_Configuration_File_Format.html | 64 +
...ft_Documentation-0.1-Deployment_Guide-en-US.pdf | Bin 0 -> 6516012 bytes
public_html/en-US/Site_Statistics.html | 4 +-
public_html/en-US/toc.html | 15 +
public_html/es-ES/Site_Statistics.html | 4 +-
public_html/es-ES/toc.html | 15 +
public_html/fi-FI/Site_Statistics.html | 4 +-
public_html/fi-FI/toc.html | 15 +
public_html/fr-FR/Site_Statistics.html | 4 +-
public_html/fr-FR/toc.html | 15 +
public_html/gu-IN/Site_Statistics.html | 4 +-
public_html/gu-IN/toc.html | 15 +
public_html/he-IL/Site_Statistics.html | 4 +-
public_html/he-IL/toc.html | 15 +
public_html/hi-IN/Site_Statistics.html | 4 +-
public_html/hi-IN/toc.html | 15 +
public_html/hu-HU/Site_Statistics.html | 4 +-
public_html/hu-HU/toc.html | 15 +
public_html/id-ID/Site_Statistics.html | 4 +-
public_html/id-ID/toc.html | 15 +
public_html/it-IT/Site_Statistics.html | 4 +-
public_html/it-IT/toc.html | 15 +
public_html/ja-JP/Site_Statistics.html | 4 +-
public_html/ja-JP/toc.html | 15 +
public_html/kn-IN/Site_Statistics.html | 4 +-
public_html/kn-IN/toc.html | 15 +
public_html/ko-KR/Site_Statistics.html | 4 +-
public_html/ko-KR/toc.html | 15 +
public_html/ml-IN/Site_Statistics.html | 4 +-
public_html/ml-IN/toc.html | 15 +
public_html/mr-IN/Site_Statistics.html | 4 +-
public_html/mr-IN/toc.html | 15 +
public_html/nb-NO/Site_Statistics.html | 4 +-
public_html/nb-NO/toc.html | 15 +
public_html/nl-NL/Site_Statistics.html | 4 +-
public_html/nl-NL/toc.html | 15 +
public_html/or-IN/Site_Statistics.html | 4 +-
public_html/or-IN/toc.html | 15 +
public_html/pa-IN/Site_Statistics.html | 4 +-
public_html/pa-IN/toc.html | 15 +
public_html/pl-PL/Site_Statistics.html | 4 +-
public_html/pl-PL/toc.html | 15 +
public_html/pt-BR/Site_Statistics.html | 4 +-
public_html/pt-BR/toc.html | 15 +
public_html/pt-PT/Site_Statistics.html | 4 +-
public_html/pt-PT/toc.html | 15 +
public_html/ru-RU/Site_Statistics.html | 4 +-
public_html/ru-RU/toc.html | 15 +
public_html/sk-SK/Site_Statistics.html | 4 +-
public_html/sk-SK/toc.html | 15 +
public_html/sr-Latn-RS/Site_Statistics.html | 4 +-
public_html/sr-Latn-RS/toc.html | 15 +
public_html/sr-RS/Site_Statistics.html | 4 +-
public_html/sr-RS/toc.html | 15 +
public_html/sv-SE/Site_Statistics.html | 4 +-
public_html/sv-SE/toc.html | 15 +
public_html/ta-IN/Site_Statistics.html | 4 +-
public_html/ta-IN/toc.html | 15 +
public_html/te-IN/Site_Statistics.html | 4 +-
public_html/te-IN/toc.html | 15 +
public_html/toc.html | 15 +
public_html/uk-UA/Site_Statistics.html | 4 +-
public_html/uk-UA/toc.html | 15 +
public_html/zh-CN/Site_Statistics.html | 4 +-
public_html/zh-CN/toc.html | 15 +
public_html/zh-TW/Site_Statistics.html | 4 +-
public_html/zh-TW/toc.html | 15 +
1172 files changed, 39229 insertions(+), 82 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index 64f3973..d1ecb11 100644
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 6803ccc..49a196e 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -2995,6 +2995,30 @@
<priority>0.8</priority>
</url>
<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub</loc>
+ <lastmod>2010-07-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html</loc>
+ <lastmod>2010-07-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html</loc>
+ <lastmod>2010-07-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf</loc>
+ <lastmod>2010-07-19</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/epub/RPM_Guide/Fedora_Draft_Documentation-0.1-RPM_Guide-en-US.epub</loc>
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
diff --git a/public_html/as-IN/Site_Statistics.html b/public_html/as-IN/Site_Statistics.html
index 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/as-IN/toc.html b/public_html/as-IN/toc.html
index 06a8017..6f58659 100644
--- a/public_html/as-IN/toc.html
+++ b/public_html/as-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/bg-BG/toc.html b/public_html/bg-BG/toc.html
index c70567a..3685660 100644
--- a/public_html/bg-BG/toc.html
+++ b/public_html/bg-BG/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/bn-IN/toc.html b/public_html/bn-IN/toc.html
index 97f3e00..f149e26 100644
--- a/public_html/bn-IN/toc.html
+++ b/public_html/bn-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/bs-BA/toc.html b/public_html/bs-BA/toc.html
index fffa945..0f9dc0d 100644
--- a/public_html/bs-BA/toc.html
+++ b/public_html/bs-BA/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/ca-ES/toc.html b/public_html/ca-ES/toc.html
index ca2107e..7f4d5d9 100644
--- a/public_html/ca-ES/toc.html
+++ b/public_html/ca-ES/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/cs-CZ/toc.html b/public_html/cs-CZ/toc.html
index 1fdaa34..f6689f8 100644
--- a/public_html/cs-CZ/toc.html
+++ b/public_html/cs-CZ/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/da-DK/toc.html b/public_html/da-DK/toc.html
index e609950..9072647 100644
--- a/public_html/da-DK/toc.html
+++ b/public_html/da-DK/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/de-DE/toc.html b/public_html/de-DE/toc.html
index ef091e5..c4fbaf1 100644
--- a/public_html/de-DE/toc.html
+++ b/public_html/de-DE/toc.html
@@ -1453,6 +1453,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/el-GR/toc.html b/public_html/el-GR/toc.html
index b866e49..06a80f0 100644
--- a/public_html/el-GR/toc.html
+++ b/public_html/el-GR/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub b/public_html/en-US/Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub
new file mode 100644
index 0000000..8780275
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..a196f22
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/common.css
@@ -0,0 +1,1467 @@
+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: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;
+}
+
+sup {
+ color:#999;
+}
+
+/* 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 {
+ background-color:#ede7c8;
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+ color:#444;
+}
+
+.guibutton, .guilabel {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+ white-space:nowrap;
+}
+
+.example {
+ background-color:#dc9f2e;
+ padding:5px;
+ margin-bottom: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:#eeeeee;
+ 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 {
+ color:white;
+}
+
+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.note, div.important, div.warning {
+ padding:1em;
+ padding-bottom:20px;
+ margin-top:.5em;
+ margin-bottom:1.5em;
+ background-repeat:no-repeat;
+ background-position:1em 1em;
+}
+
+div.note pre, div.important pre, div.warning pre {
+ background-color: #333;
+ color: white;
+ margin-left: 4.5em;
+}
+
+
+div.note {
+ background-image:url(../images/note.png);
+ background-color:#8e9f00;
+ color:white;
+}
+
+div.important {
+ background-color:#d08e13;
+ color:white;
+ background-image:url(../images/important.png);
+}
+
+div.warning {
+ background-color:#9e292b;
+ color:white;
+ background-image:url(../images/warning.png);
+}
+
+
+/* Admonition Headings */
+div.note h2, div.important h2, div.warning h2 {
+ height:32px;
+ font-size:1.3em;
+}
+
+div.note h2, div.important h2, div.warning h2 {
+ color:white;
+}
+
+/* Admonition Inlines */
+div.note .replaceable, div.important .replaceable, div.warning .replaceable {
+ color:#e3dcc0;
+}
+
+pre .replaceable, tt .replaceable {
+ color:#444;
+}
+
+div.note .guilabel, div.important .guilabel, div.warning .guilabel {
+ color:#e3dcc0;
+}
+
+
+/* Admonition Lists ... really? */
+div.note li, div.warning li, div.important li {
+ padding-left:10px;
+ margin:0em;
+}
+
+div.note ul, div.warning ul, div.important ul {
+ padding-left:40px;
+ margin:0em;
+}
+
+/* Admonition links in verbatim ... *really* */
+div.note pre pre a:visited, div.important pre pre a:visited,
+ div.warning pre pre a:visited, div.note pre a:link, div.important pre a:link, div.warning pre a:link {
+ color:#0066cc;
+}
+
+/* Admonition links */
+div.note a:visited, div.important a:visited, div.warning a:visited, div.note a:link , div.important a:link , div.warning a:link {
+ color:#f7f2d0;
+}
+
+/*notification icons*/
+div.note h2, div.note p, div.note div.para, div.warning h2, div.warning p, div.warning div.para, div.important h2, .important p, .important div.para {
+ padding:0em;
+ margin:0em;
+ padding-left:56px;
+}
+
+/*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 {
+ padding:.2em 1em;
+ background-color:#c8c5ac;
+ font-size: .7em;
+ margin:0em;
+ margin-bottom:.5em;
+ color:#222;
+}
+
+table .footnote {
+ margin:1em .5em;
+}
+
+sup {
+ padding:0em .3em;
+ 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 {
+ color:#fff;
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:5em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+ color:white;
+}
+
+/**/
+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
+{
+ color:white;
+}
+
+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:15px;
+ -webkit-border-radius:15px;
+ border-radius: 15px;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/default.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/lang.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/overrides.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..895173d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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;
+}
+
+.edition {
+ color: #3c6eb4;
+}
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/print.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..1098dab
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/1.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..3736523
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/1.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 17.993,22.013004 L 17.993,10.113004 L 15.239,10.113004 C 14.899001,11.218003 14.286999,11.643004 12.757,11.728004 L 12.757,13.819004 L 14.763,13.819004 L 14.763,22.013004 L 17.993,22.013004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/10.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..ef058e3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/10.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/10.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..84ee18f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/10.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.252562,22 L 12.252562,10.1 L 9.4985624,10.1 C 9.1585628,11.204999 8.5465609,11.63 7.0165624,11.715 L 7.0165624,13.806 L 9.0225624,13.806 L 9.0225624,22 L 12.252562,22 M 24.983438,16.033 C 24.983438,12.072004 22.705435,9.913 19.611438,9.913 C 16.517441,9.913 14.205438,12.106004 14.205438,16.067 C 14.205438,20.027996 16.483441,22.187 19.577438,22.187 C 22.671435,22.187 24.983438,19.993996 24.983438,16.033 M 21.600438,16.067 C 21.600438,18.242998 20.886437,19.348 19.611438,19.348 C 18.336439,19.348 17.588438,18.208998 17.588438,16.033 C 17.588438,13.857002 18.302439,12.752 19.577438,12.752 C 20.852437,12.752 21.600438,13.891002 21.600438,16.067"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/11.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..fa20ec4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/11.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/11.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..47f0c80
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/11.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 14.623052,22 L 14.623052,10.1 L 11.869052,10.1 C 11.529053,11.204999 10.917051,11.63 9.3870527,11.715 L 9.3870527,13.806 L 11.393052,13.806 L 11.393052,22 L 14.623052,22 M 21.794928,22 L 21.794928,10.1 L 19.040928,10.1 C 18.700928,11.204999 18.088926,11.63 16.558928,11.715 L 16.558928,13.806 L 18.564928,13.806 L 18.564928,22 L 21.794928,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/12.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..84c132a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/12.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/12.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..94ddaac
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/12.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.677562,22 L 12.677562,10.1 L 9.9235624,10.1 C 9.5835628,11.204999 8.9715609,11.63 7.4415624,11.715 L 7.4415624,13.806 L 9.4475624,13.806 L 9.4475624,22 L 12.677562,22 M 24.558438,22 L 24.558438,19.314 L 18.353438,19.314 C 18.608438,18.600001 19.27144,17.936999 21.651438,16.832 C 23.929436,15.778001 24.473438,14.825998 24.473438,13.262 C 24.473438,11.103002 22.926435,9.913 19.968438,9.913 C 17.92844,9.913 16.381436,10.491001 14.868438,11.46 L 16.381438,13.891 C 17.571437,13.092001 18.727439,12.684 19.917438,12.684 C 20.869437,12.684 21.243438,12.973001 21.243438,13.5 C 21.243438,13.976 21.056437,14.163001 19.798438,14.724 C 16.823441,16.049999 14.936438,17.988004 14.834438,22 L 24.558438,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/13.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..f41ec8f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/13.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/13.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..040dd6c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/13.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.550062,22 L 12.550062,10.1 L 9.7960624,10.1 C 9.4560628,11.204999 8.8440609,11.63 7.3140624,11.715 L 7.3140624,13.806 L 9.3200624,13.806 L 9.3200624,22 L 12.550062,22 M 24.685938,18.226 C 24.685938,16.713002 23.716937,15.914 22.611938,15.659 C 23.427937,15.268 24.192938,14.638999 24.192938,13.33 C 24.192938,10.814003 22.288935,9.913 19.432938,9.913 C 17.35894,9.913 15.930937,10.610001 14.825938,11.46 L 16.389938,13.602 C 17.307937,12.939001 18.191939,12.582 19.347938,12.582 C 20.520937,12.582 20.996938,12.922001 20.996938,13.551 C 20.996938,14.332999 20.656937,14.554 19.619938,14.554 L 18.089938,14.554 L 18.089938,17.121 L 19.806938,17.121 C 21.013937,17.121 21.489938,17.427001 21.489938,18.26 C 21.489938,19.075999 20.911937,19.467 19.534938,19.467 C 18.225939,19.467 17.120937,18.973999 16.151938,18.226 L 14.451938,20.368 C 15.726937,21.489999 17.44394,22.187 19.466938,22.187 C 22.696935,22.187 24.685938,20.979997 24.685938,18.226"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/14.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..c491206
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/14.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/14.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..7f4fcfd
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/14.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.040062,22 L 12.040062,10.1 L 9.2860624,10.1 C 8.9460628,11.204999 8.3340609,11.63 6.8040624,11.715 L 6.8040624,13.806 L 8.8100624,13.806 L 8.8100624,22 L 12.040062,22 M 25.195938,19.96 L 25.195938,17.172 L 23.665938,17.172 L 23.665938,10.1 L 20.401938,10.1 L 13.992938,17.461 L 13.992938,19.875 L 20.707938,19.875 L 20.707938,22 L 23.665938,22 L 23.665938,19.96 L 25.195938,19.96 M 20.758938,13.432 C 20.724938,13.992999 20.707938,15.302001 20.707938,15.999 L 20.707938,17.172 L 19.823938,17.172 C 19.007939,17.172 18.191937,17.189 17.596938,17.223 C 18.038938,16.798 18.531939,16.253999 19.160938,15.489 L 19.330938,15.285 C 20.112937,14.350001 20.435938,13.925 20.758938,13.432"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/15.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..7656c94
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/15.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/15.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..a8eba4d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/15.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.388562,22 L 12.388562,10.1 L 9.6345624,10.1 C 9.2945628,11.204999 8.6825609,11.63 7.1525624,11.715 L 7.1525624,13.806 L 9.1585624,13.806 L 9.1585624,22 L 12.388562,22 M 24.847438,17.852 C 24.847438,15.200003 23.164435,13.908 20.597438,13.908 C 19.407439,13.908 18.693437,14.112 18.030438,14.435 L 18.132438,12.786 L 24.133438,12.786 L 24.133438,10.1 L 15.463438,10.1 L 15.055438,16.271 L 17.877438,17.223 C 18.472437,16.798 19.067439,16.543 20.070438,16.543 C 21.090437,16.543 21.668438,17.019001 21.668438,17.937 C 21.668438,18.888999 21.107436,19.45 19.577438,19.45 C 18.302439,19.45 16.891437,18.956999 15.752438,18.277 L 14.409438,20.742 C 15.871436,21.625999 17.43544,22.187 19.492438,22.187 C 22.875435,22.187 24.847438,20.622997 24.847438,17.852"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/16.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..1f2535a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/16.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/16.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..1adc217
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/16.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.405562,22 L 12.405562,10.1 L 9.6515624,10.1 C 9.3115628,11.204999 8.6995609,11.63 7.1695624,11.715 L 7.1695624,13.806 L 9.1755624,13.806 L 9.1755624,22 L 12.405562,22 M 24.830438,17.903 C 24.830438,15.387003 23.096435,14.214 20.631438,14.214 C 19.203439,14.214 18.336437,14.486 17.571438,14.911 C 18.472437,13.534001 20.104441,12.616 23.215438,12.616 L 23.215438,9.913 C 16.415445,9.913 14.341438,14.112003 14.341438,17.257 C 14.341438,20.537997 16.415441,22.187 19.407438,22.187 C 22.773435,22.187 24.830438,20.588997 24.830438,17.903 M 21.651438,18.124 C 21.651438,19.075999 20.818437,19.586 19.577438,19.586 C 18.132439,19.586 17.486438,18.990999 17.486438,18.141 C 17.486438,17.206001 18.183439,16.645 19.645438,16.645 C 20.903437,16.645 21.651438,17.206001 21.651438,18.124"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/17.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..67fe7ce
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/17.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/17.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..b007799
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/17.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.652062,22 L 12.652062,10.1 L 9.8980624,10.1 C 9.5580628,11.204999 8.9460609,11.63 7.4160624,11.715 L 7.4160624,13.806 L 9.4220624,13.806 L 9.4220624,22 L 12.652062,22 M 24.583938,12.48 L 24.583938,10.1 L 14.740938,10.1 L 14.740938,12.786 L 20.656938,12.786 C 18.36194,15.131998 17.239938,17.920004 17.205938,22 L 20.435938,22 C 20.435938,18.141004 21.098941,15.675997 24.583938,12.48"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/18.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..76aa05b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/18.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/18.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..140c8ec
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/18.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.176062,22 L 12.176062,10.1 L 9.4220624,10.1 C 9.0820628,11.204999 8.4700609,11.63 6.9400624,11.715 L 6.9400624,13.806 L 8.9460624,13.806 L 8.9460624,22 L 12.176062,22 M 25.059938,18.294 C 25.059938,16.764002 23.971937,15.948 23.206938,15.642 C 23.954937,15.166 24.549938,14.519999 24.549938,13.449 C 24.549938,11.171002 22.526935,9.913 19.653938,9.913 C 16.780941,9.913 14.723938,11.171002 14.723938,13.449 C 14.723938,14.519999 15.352939,15.251 16.066938,15.676 C 15.301939,15.982 14.213938,16.764002 14.213938,18.294 C 14.213938,20.707998 16.287941,22.187 19.619938,22.187 C 22.951935,22.187 25.059938,20.707998 25.059938,18.294 M 21.387938,13.5 C 21.387938,14.094999 20.945937,14.639 19.653938,14.639 C 18.361939,14.639 17.885938,14.094999 17.885938,13.5 C 17.885938,12.905001 18.327939,12.31 19.619938,12.31 C 20.911937,12.31 21.387938,12.905001 21.387938,13.5 M 21.897938,18.26 C 21.897938,19.075999 21.149936,19.688 19.653938,19.688 C 18.157939,19.688 17.375938,19.07599
9 17.375938,18.26 C 17.375938,17.444001 18.106939,16.849 19.619938,16.849 C 21.115936,16.849 21.897938,17.444001 21.897938,18.26"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/19.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..5f5ada0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/19.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/19.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..ae864c4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/19.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.414062,22 L 12.414062,10.1 L 9.6600624,10.1 C 9.3200628,11.204999 8.7080609,11.63 7.1780624,11.715 L 7.1780624,13.806 L 9.1840624,13.806 L 9.1840624,22 L 12.414062,22 M 24.821938,14.843 C 24.821938,11.562003 22.747935,9.913 19.755938,9.913 C 16.389941,9.913 14.332938,11.511003 14.332938,14.197 C 14.332938,16.712997 16.06694,17.886 18.531938,17.886 C 19.959937,17.886 20.826939,17.614 21.591938,17.189 C 20.690939,18.565999 19.058935,19.484 15.947938,19.484 L 15.947938,22.187 C 22.747931,22.187 24.821938,17.987997 24.821938,14.843 M 21.676938,13.959 C 21.676938,14.893999 20.979936,15.455 19.517938,15.455 C 18.259939,15.455 17.511938,14.893999 17.511938,13.976 C 17.511938,13.024001 18.344939,12.514 19.585938,12.514 C 21.030936,12.514 21.676938,13.109001 21.676938,13.959"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..8fe3709
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/2.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..ee96128
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/2.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 20.862,22.013004 L 20.862,19.327004 L 14.657,19.327004 C 14.912,18.613005 15.575003,17.950003 17.955,16.845004 C 20.232998,15.791005 20.777,14.839003 20.777,13.275004 C 20.777,11.116006 19.229997,9.9260043 16.272,9.9260043 C 14.232002,9.9260043 12.684999,10.504005 11.172,11.473004 L 12.685,13.904004 C 13.874999,13.105005 15.031001,12.697004 16.221,12.697004 C 17.172999,12.697004 17.547,12.986005 17.547,13.513004 C 17.547,13.989004 17.359999,14.176005 16.102,14.737004 C 13.127003,16.063003 11.24,18.001008 11.138,22.013004 L 20.862,22.013004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/20.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..5e2ad33
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/20.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/20.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..1678a9f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/20.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 14.685,22 L 14.685,19.314 L 8.4799999,19.314 C 8.7349997,18.600001 9.3980023,17.936999 11.778,16.832 C 14.055998,15.778001 14.6,14.825998 14.6,13.262 C 14.6,11.103002 13.052997,9.913 10.095,9.913 C 8.055002,9.913 6.5079984,10.491001 4.9949999,11.46 L 6.5079999,13.891 C 7.6979988,13.092001 8.8540011,12.684 10.044,12.684 C 10.995999,12.684 11.37,12.973001 11.37,13.5 C 11.37,13.976 11.182999,14.163001 9.9249999,14.724 C 6.9500029,16.049999 5.0629998,17.988004 4.9609999,22 L 14.685,22 M 27.421719,16.033 C 27.421719,12.072004 25.143716,9.913 22.049719,9.913 C 18.955722,9.913 16.643719,12.106004 16.643719,16.067 C 16.643719,20.027996 18.921722,22.187 22.015719,22.187 C 25.109716,22.187 27.421719,19.993996 27.421719,16.033 M 24.038719,16.067 C 24.038719,18.242998 23.324717,19.348 22.049719,19.348 C 20.77472,19.348 20.026719,18.208998 20.026719,16.033 C 20.026719,13.857002 20.74072,12.752 22.015719,12.752 C 23.290717,12.752 24.038719,13.891002 24.038719,16.067"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/21.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..cfafd1f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/21.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/21.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..4199512
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/21.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 16.648141,22 L 16.648141,19.314 L 10.44314,19.314 C 10.69814,18.600001 11.361143,17.936999 13.741141,16.832 C 16.019139,15.778001 16.563141,14.825998 16.563141,13.262 C 16.563141,11.103002 15.016138,9.913 12.058141,9.913 C 10.018143,9.913 8.471139,10.491001 6.9581405,11.46 L 8.4711405,13.891 C 9.661139,13.092001 10.817142,12.684 12.007141,12.684 C 12.95914,12.684 13.333141,12.973001 13.333141,13.5 C 13.333141,13.976 13.14614,14.163001 11.88814,14.724 C 8.9131435,16.049999 7.0261404,17.988004 6.9241405,22 L 16.648141,22 M 23.82586,22 L 23.82586,10.1 L 21.07186,10.1 C 20.73186,11.204999 20.119858,11.63 18.58986,11.715 L 18.58986,13.806 L 20.59586,13.806 L 20.59586,22 L 23.82586,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/22.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..5415d35
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/22.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/22.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..c1f4479
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/22.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 14.685,22 L 14.685,19.314 L 8.4799999,19.314 C 8.7349997,18.600001 9.3980023,17.936999 11.778,16.832 C 14.055998,15.778001 14.6,14.825998 14.6,13.262 C 14.6,11.103002 13.052997,9.913 10.095,9.913 C 8.055002,9.913 6.5079984,10.491001 4.9949999,11.46 L 6.5079999,13.891 C 7.6979988,13.092001 8.8540011,12.684 10.044,12.684 C 10.995999,12.684 11.37,12.973001 11.37,13.5 C 11.37,13.976 11.182999,14.163001 9.9249999,14.724 C 6.9500029,16.049999 5.0629998,17.988004 4.9609999,22 L 14.685,22 M 26.571719,22 L 26.571719,19.314 L 20.366719,19.314 C 20.621718,18.600001 21.284721,17.936999 23.664719,16.832 C 25.942716,15.778001 26.486719,14.825998 26.486719,13.262 C 26.486719,11.103002 24.939716,9.913 21.981719,9.913 C 19.941721,9.913 18.394717,10.491001 16.881719,11.46 L 18.394719,13.891 C 19.584718,13.092001 20.74072,12.684 21.930719,12.684 C 22.882718,12.684 23.256719,12.973001 23.256719,13.5 C 23.256719,13.976 23.069717,14.163001 21.811719,14.724 C 18.836722,16.049999 16.94971
9,17.988004 16.847719,22 L 26.571719,22"
+ id="number"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/23.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..658e22b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/23.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/23.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..ea3c85a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/23.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 15.32239,22.013004 L 15.32239,19.327004 L 9.1173907,19.327004 C 9.3723904,18.613005 10.035393,17.950003 12.41539,16.845004 C 14.693388,15.791005 15.23739,14.839003 15.23739,13.275004 C 15.23739,11.116006 13.690387,9.9260043 10.73239,9.9260043 C 8.6923927,9.9260043 7.1453891,10.504005 5.6323906,11.473004 L 7.1453906,13.904004 C 8.3353896,13.105005 9.4913919,12.697004 10.68139,12.697004 C 11.633389,12.697004 12.00739,12.986005 12.00739,13.513004 C 12.00739,13.989004 11.820389,14.176005 10.56239,14.737004 C 7.5873937,16.063003 5.7003905,18.001008 5.5983906,22.013004 L 15.32239,22.013004 M 26.401609,18.239004 C 26.401609,16.726006 25.432608,15.927004 24.327609,15.672004 C 25.143608,15.281005 25.908609,14.652003 25.908609,13.343004 C 25.908609,10.827007 24.004606,9.9260043 21.148609,9.9260043 C 19.074611,9.9260043 17.646608,10.623005 16.541609,11.473004 L 18.105609,13.615004 C 19.023608,12.952005 19.90761,12.595004 21.063609,12.595004 C 22.236608,12.595004 22.712609,12.
935005 22.712609,13.564004 C 22.712609,14.346004 22.372608,14.567004 21.335609,14.567004 L 19.805609,14.567004 L 19.805609,17.134004 L 21.522609,17.134004 C 22.729608,17.134004 23.205609,17.440005 23.205609,18.273004 C 23.205609,19.089003 22.627608,19.480004 21.250609,19.480004 C 19.94161,19.480004 18.836608,18.987004 17.867609,18.239004 L 16.167609,20.381004 C 17.442608,21.503003 19.159611,22.200004 21.182609,22.200004 C 24.412606,22.200004 26.401609,20.993002 26.401609,18.239004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..449ef5a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/3.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..d3a7e73
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/3.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 21.117,18.239004 C 21.117,16.726006 20.147999,15.927004 19.043,15.672004 C 19.858999,15.281005 20.624,14.652003 20.624,13.343004 C 20.624,10.827007 18.719997,9.9260043 15.864,9.9260043 C 13.790002,9.9260043 12.361999,10.623005 11.257,11.473004 L 12.821,13.615004 C 13.738999,12.952005 14.623001,12.595004 15.779,12.595004 C 16.951999,12.595004 17.428,12.935005 17.428,13.564004 C 17.428,14.346004 17.087999,14.567004 16.051,14.567004 L 14.521,14.567004 L 14.521,17.134004 L 16.238,17.134004 C 17.444999,17.134004 17.921,17.440005 17.921,18.273004 C 17.921,19.089003 17.342999,19.480004 15.966,19.480004 C 14.657002,19.480004 13.551999,18.987004 12.583,18.239004 L 10.883,20.381004 C 12.157999,21.503003 13.875002,22.200004 15.898,22.200004 C 19.127997,22.200004 21.117,20.993002 21.117,18.239004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..0a2634a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/4.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..e6bbe8e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/4.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 20.573772,19.96 L 20.573772,17.172 L 19.043772,17.172 L 19.043772,10.1 L 15.779772,10.1 L 9.3707718,17.461 L 9.3707718,19.875 L 16.085772,19.875 L 16.085772,22 L 19.043772,22 L 19.043772,19.96 L 20.573772,19.96 M 16.136772,13.432 C 16.102772,13.992999 16.085772,15.302001 16.085772,15.999 L 16.085772,17.172 L 15.201772,17.172 C 14.385773,17.172 13.569771,17.189 12.974772,17.223 C 13.416772,16.798 13.909773,16.253999 14.538772,15.489 L 14.708772,15.285 C 15.490771,14.350001 15.813772,13.925 16.136772,13.432"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..bc1d337
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/5.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..d8578f2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/5.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 21.219,17.852 C 21.219,15.200003 19.535997,13.908 16.969,13.908 C 15.779001,13.908 15.064999,14.112 14.402,14.435 L 14.504,12.786 L 20.505,12.786 L 20.505,10.1 L 11.835,10.1 L 11.427,16.271 L 14.249,17.223 C 14.843999,16.798 15.439001,16.543 16.442,16.543 C 17.461999,16.543 18.04,17.019001 18.04,17.937 C 18.04,18.888999 17.478998,19.45 15.949,19.45 C 14.674001,19.45 13.262999,18.956999 12.124,18.277 L 10.781,20.742 C 12.242999,21.625999 13.807002,22.187 15.864,22.187 C 19.246997,22.187 21.219,20.622997 21.219,17.852"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..68cb4b6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/6.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..14d62e0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/6.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 21.2445,17.903 C 21.2445,15.387003 19.510497,14.214 17.0455,14.214 C 15.617501,14.214 14.750499,14.486 13.9855,14.911 C 14.886499,13.534001 16.518503,12.616 19.6295,12.616 L 19.6295,9.913 C 12.829507,9.913 10.7555,14.112003 10.7555,17.257 C 10.7555,20.537997 12.829503,22.187 15.8215,22.187 C 19.187497,22.187 21.2445,20.588997 21.2445,17.903 M 18.0655,18.124 C 18.0655,19.075999 17.232499,19.586 15.9915,19.586 C 14.546501,19.586 13.9005,18.990999 13.9005,18.141 C 13.9005,17.206001 14.597501,16.645 16.0595,16.645 C 17.317499,16.645 18.0655,17.206001 18.0655,18.124"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..3b6cc72
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/7.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..8d71ee3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/7.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 20.9215,12.48 L 20.9215,10.1 L 11.0785,10.1 L 11.0785,12.786 L 16.9945,12.786 C 14.699502,15.131998 13.5775,17.920004 13.5435,22 L 16.7735,22 C 16.7735,18.141004 17.436503,15.675997 20.9215,12.48"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/8.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..b092185
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/8.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..1c31e86
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/8.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 21.423,18.294 C 21.423,16.764002 20.334999,15.948 19.57,15.642 C 20.317999,15.166 20.913,14.519999 20.913,13.449 C 20.913,11.171002 18.889997,9.913 16.017,9.913 C 13.144003,9.913 11.087,11.171002 11.087,13.449 C 11.087,14.519999 11.716001,15.251 12.43,15.676 C 11.665001,15.982 10.577,16.764002 10.577,18.294 C 10.577,20.707998 12.651003,22.187 15.983,22.187 C 19.314997,22.187 21.423,20.707998 21.423,18.294 M 17.751,13.5 C 17.751,14.094999 17.308999,14.639 16.017,14.639 C 14.725001,14.639 14.249,14.094999 14.249,13.5 C 14.249,12.905001 14.691001,12.31 15.983,12.31 C 17.274999,12.31 17.751,12.905001 17.751,13.5 M 18.261,18.26 C 18.261,19.075999 17.512998,19.688 16.017,19.688 C 14.521001,19.688 13.739,19.075999 13.739,18.26 C 13.739,17.444001 14.470002,16.849 15.983,16.849 C 17.478998,16.849 18.261,17.444001 18.261,18.26"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/9.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..7706583
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/9.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..851e9a3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/9.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 22.128383,14.843 C 22.128383,11.562003 20.05438,9.913 17.062383,9.913 C 13.696386,9.913 11.639383,11.511003 11.639383,14.197 C 11.639383,16.712997 13.373385,17.886 15.838383,17.886 C 17.266382,17.886 18.133384,17.614 18.898383,17.189 C 17.997384,18.565999 16.36538,19.484 13.254383,19.484 L 13.254383,22.187 C 20.054376,22.187 22.128383,17.987997 22.128383,14.843 M 18.983383,13.959 C 18.983383,14.893999 18.286381,15.455 16.824383,15.455 C 15.566384,15.455 14.818383,14.893999 14.818383,13.976 C 14.818383,13.024001 15.651384,12.514 16.892383,12.514 C 18.337381,12.514 18.983383,13.109001 18.983383,13.959"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/documentation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/dot.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/dot2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/h1-bg.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/image_left.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/image_right.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/important.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/important.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/important.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/logo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/note.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/note.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/note.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/redhat-logo.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/redhat-logo.svg
new file mode 100644
index 0000000..1001776
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/redhat-logo.svg
@@ -0,0 +1,94 @@
+<?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://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"
+ width="300"
+ height="140"
+ id="svg2812"
+ sodipodi:version="0.32"
+ inkscape:version="0.45+devel"
+ version="1.0"
+ sodipodi:docname="redhat-logo.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape">
+ <defs
+ id="defs3" />
+ <sodipodi:namedview
+ inkscape:document-units="mm"
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="1"
+ inkscape:cx="174.26394"
+ inkscape:cy="40.358463"
+ inkscape:current-layer="layer1"
+ inkscape:window-width="722"
+ inkscape:window-height="523"
+ inkscape:window-x="71"
+ inkscape:window-y="636"
+ width="300px"
+ height="140px" />
+ <metadata
+ id="metadata4">
+ <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>
+ <g
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ id="layer1"
+ transform="translate(-13.714282,-252.57246)">
+ <g
+ transform="matrix(2.1166666,0,0,2.1166666,-32.193429,187.76029)"
+ id="shadowman">
+ <path
+ d="M 55.68466,68.503937 C 55.68466,79.688581 46.617715,88.755526 35.433071,88.755526 C 24.248427,88.755526 15.181482,79.688581 15.181482,68.503937 C 15.181482,57.319293 24.248427,48.252348 35.433071,48.252348 C 46.617715,48.252348 55.68466,57.319293 55.68466,68.503937 z"
+ transform="matrix(1.10693,0,0,1.10693,5.005761,-12.00975)"
+ style="fill:#ffffff"
+ id="path4548" />
+ <path
+ d="M 147.81332,72.126073 C 147.81332,73.329962 147.86057,74.57586 148.03519,75.740362 L 146.64882,75.740362 L 146.42826,73.559712 L 146.35605,73.559712 C 145.61822,74.733404 143.92333,76.086957 141.50635,76.086957 C 138.4461,76.086957 137.02164,73.933874 137.02164,71.904202 C 137.02164,68.394942 140.11998,66.27862 146.30878,66.34295 L 146.30878,65.937278 C 146.30878,64.432747 146.01471,61.431561 142.41879,61.45388 C 141.08756,61.45388 139.70118,61.810976 138.5997,62.588186 L 138.1205,61.494579 C 139.51083,60.551948 141.20703,60.180411 142.58291,60.180411 C 146.97178,60.180411 147.81201,63.475677 147.81201,66.194597 L 147.81201,72.126073 L 147.81332,72.126073 z M 146.30878,67.609855 C 142.99645,67.514016 138.62333,68.015527 138.62333,71.667888 C 138.62333,73.853791 140.06616,74.835806 141.65077,74.835806 C 144.1859,74.835806 145.62742,73.266945 146.15124,71.786044 C 146.26152,71.460456 146.3101,71.134869 146.3101,70.874924 L 146.3101,67.609855 L 146.30878,67.609855 z
M 153.80387,57.175286 L 153.80387,60.527004 L 158.13891,60.527004 L 158.13891,61.747959 L 153.80387,61.747959 L 153.80387,71.635066 C 153.80387,73.568902 154.40385,74.780665 156.03835,74.780665 C 156.82343,74.780665 157.37877,74.676951 157.76606,74.541727 L 157.94856,75.707542 C 157.45754,75.912347 156.76567,76.072514 155.84798,76.072514 C 154.73862,76.072514 153.81831,75.723296 153.22358,74.994662 C 152.53566,74.195133 152.29934,72.917726 152.29934,71.365932 L 152.29934,61.746646 L 149.7314,61.746646 L 149.7314,60.525692 L 152.29934,60.525692 L 152.29934,57.729312 L 153.80387,57.175286 z M 129.02767,60.179099 C 127.87105,60.179099 126.8339,60.512563 125.96348,61.052146 C 125.05891,61.581226 124.3224,62.399135 123.88522,63.247239 L 123.8222,63.247239 L 123.8222,55.719331 L 122.31767,55.309721 L 122.31767,75.740362 L 123.8222,75.740362 L 123.8222,66.437475 C 123.8222,65.819121 123.86947,65.39113 124.02832,64.938196 C 124.67818,63.046372 126.45974,61.493265 128.61545,61.49326
5 C 131.72953,61.493265 132.80739,63.990315 132.80739,66.730242 L 132.80739,75.73905 L 134.31191,75.73905 L 134.31191,66.564822 C 134.31191,60.899855 130.4692,60.179099 129.02767,60.179099 z"
+ id="path620" />
+ <path
+ d="M 78.208384,65.270348 C 78.208384,63.205228 78.16506,61.686255 78.08235,60.311696 L 81.460325,60.311696 L 81.604739,63.240675 L 81.713705,63.240675 C 82.473849,61.069213 84.273772,59.961164 85.938472,59.961164 C 86.319199,59.961164 86.541071,59.976918 86.853532,60.045187 L 86.853532,63.719867 C 86.488557,63.648972 86.147215,63.609587 85.677213,63.609587 C 83.819525,63.609587 82.528988,64.792469 82.181081,66.560884 C 82.115438,66.904852 82.079992,67.318401 82.079992,67.738514 L 82.079992,75.73905 L 78.176875,75.73905 L 78.208384,65.270348 z M 91.56274,69.076313 C 91.666455,71.871381 93.83004,73.093647 96.328402,73.093647 C 98.123074,73.093647 99.405732,72.814009 100.58599,72.379455 L 101.16365,75.064243 C 99.842914,75.623519 98.010169,76.042319 95.771752,76.042319 C 90.763211,76.042319 87.82767,72.949234 87.82767,68.220332 C 87.82767,63.961432 90.411366,59.933594 95.372644,59.933594 C 100.38906,59.933594 102.02225,64.059896 102.02225,67.436558 C 102.02225,68.16256
6 101.95792,68.744161 101.88309,69.103883 L 91.56274,69.076313 z M 98.348885,66.358704 C 98.365952,64.929006 97.743659,62.59869 95.129766,62.59869 C 92.728556,62.59869 91.730785,64.778027 91.554863,66.358704 L 98.348885,66.358704 z M 118.82942,54.363153 L 114.93024,53.307617 L 114.93024,61.97377 L 114.8659,61.97377 C 114.17665,60.834212 112.65375,59.962477 110.54268,59.962477 C 106.83386,59.962477 103.60162,63.033244 103.62656,68.201952 C 103.62656,72.945296 106.54372,76.086957 110.22759,76.086957 C 112.45288,76.086957 114.31582,75.024857 115.23745,73.297141 L 115.30703,73.297141 L 115.48164,75.73905 L 118.95675,75.73905 C 118.88586,74.690078 118.82809,72.991246 118.82809,71.411881 L 118.82809,54.363153 L 118.82942,54.363153 z M 114.92893,69.050056 C 114.92893,69.459667 114.90136,69.840395 114.81077,70.189614 C 114.41823,71.877945 113.0371,72.966301 111.44198,72.966301 C 108.98563,72.966301 107.57957,70.894617 107.57957,68.060164 C 107.57957,65.198141 108.97382,62.983355 111
.48662,62.983355 C 113.2406,62.983355 114.49568,64.220064 114.84228,65.72197 C 114.90922,66.038368 114.92893,66.428286 114.92893,66.738119 L 114.92893,69.050056 L 114.92893,69.050056 z"
+ id="path616" />
+ <path
+ d="M 161.80517,73.528501 C 160.90479,73.528501 160.18937,74.243893 160.18939,75.144292 C 160.18939,76.044668 160.90478,76.760094 161.80517,76.760081 C 162.70554,76.760081 163.42095,76.041202 163.42097,75.144292 C 163.42097,74.24046 162.70554,73.528501 161.80517,73.528501 z M 161.80517,73.803529 C 162.54687,73.803529 163.14594,74.402585 163.14593,75.144292 C 163.14593,75.882533 162.54342,76.485053 161.80517,76.485053 C 161.06348,76.485053 160.46441,75.882523 160.46441,75.144292 C 160.46441,74.402596 161.06346,73.80354 161.80517,73.803529 z M 161.25512,74.319207 L 161.25512,75.969376 L 161.49577,75.969376 L 161.49577,75.247426 L 161.80517,75.247426 L 162.2521,75.969376 L 162.52712,75.969376 L 162.04582,75.247426 C 162.29078,75.216382 162.49274,75.06625 162.49274,74.766128 C 162.49273,74.438393 162.30159,74.319207 161.90832,74.319207 L 161.25512,74.319207 z M 161.49577,74.525479 L 161.83955,74.525479 C 162.0155,74.525467 162.21771,74.562596 162.21771,74.766128 C 162.21
773,75.02142 162.01906,75.041156 161.80517,75.041156 L 161.49577,75.041156 L 161.49577,74.525479 z"
+ id="path650" />
+ <path
+ d="M 63.115808,76.090895 C 60.810796,75.504093 58.522203,75.797079 56.285026,76.486064 C 56.010655,76.526189 56.159301,76.830359 56.114355,76.953441 C 56.240389,77.319727 56.032958,77.717522 54.998429,77.944646 C 53.465014,78.282048 52.496128,79.864039 51.942103,80.389181 C 51.290927,81.007536 49.45293,81.388262 49.729943,81.01935 C 49.946565,80.730522 50.773662,79.83253 51.276485,78.861018 C 51.726795,77.99322 52.127215,77.746405 52.678614,76.919305 C 52.841408,76.676428 53.46764,75.824385 53.650127,75.149578 C 53.854932,74.490525 53.786663,73.663427 53.865435,73.323398 C 53.97834,72.83239 54.440465,71.767665 54.477226,71.166377 C 54.496918,70.825035 53.056716,71.650821 52.372719,71.650821 C 51.688722,71.650821 51.024417,71.242523 50.412627,71.21364 C 49.657736,71.17688 49.17198,71.795235 48.489295,71.68758 C 48.098065,71.625877 47.769852,71.281909 47.087167,71.255652 C 46.115654,71.220205 44.928834,71.795235 42.698294,71.724341 C 40.507139,71.653447 38.480092,68.9
52905 38.204394,68.523601 C 37.880118,68.019465 37.484949,68.019465 37.054333,68.414634 C 36.622404,68.809804 36.090697,68.498657 35.939718,68.234773 C 35.652203,67.73195 34.882871,66.258927 33.692111,65.951719 C 32.044479,65.523729 31.210817,66.864153 31.31847,67.928878 C 31.427438,69.010669 32.127189,69.31394 32.451465,69.887656 C 32.77574,70.462687 32.94116,70.834225 33.54901,71.088919 C 33.980939,71.267467 34.142421,71.53529 34.013762,71.888448 C 33.900856,72.198281 33.451859,72.269175 33.156467,72.282304 C 31.933813,72.291845 31.468231,71.67907 30.76576,70.807968 C 30.388969,70.188301 29.79556,69.919166 29.103685,69.919166 C 28.774159,69.919166 28.465638,70.005814 28.191252,70.147603 C 27.106833,70.710817 25.817611,71.045595 24.429922,71.045595 L 22.863688,71.045595 C 22.102232,68.784859 21.688683,66.365268 21.688683,63.847213 C 21.688683,51.409229 31.770093,41.32782 44.208077,41.32782 C 56.646061,41.32782 66.72747,51.410542 66.72747,63.847213 C 66.730097,68.36212 65.40
1488,72.565881 63.115808,76.090895 z M 49.170707,74.025807 C 49.286239,74.138712 49.485793,74.518127 49.241602,75.001258 C 49.105065,75.257265 48.956712,75.437126 48.694141,75.647183 C 48.37643,75.900564 47.758075,76.194643 46.908658,75.65506 C 46.451785,75.364919 46.424215,75.267768 45.794044,75.349165 C 45.343735,75.408243 45.163874,74.953995 45.326668,74.575893 C 45.488149,74.199104 46.152454,73.893208 46.980865,74.378965 C 47.353716,74.598211 47.932685,75.059024 48.44076,74.649413 C 48.65213,74.481367 48.778164,74.368462 49.069618,74.031058 C 49.082746,74.015304 49.101126,74.007427 49.122132,74.007427 C 49.140512,74.007427 49.157579,74.013991 49.170707,74.025807 z"
+ id="path632" />
+ <path
+ d="M 63.115853,76.089615 C 65.401534,72.564599 66.72883,68.36215 66.72883,63.849868 C 66.72883,51.411879 56.647417,41.330466 44.209428,41.330466 C 31.77144,41.330466 21.690027,51.413192 21.690027,63.849868 C 21.690027,66.367923 22.103576,68.787515 22.865032,71.046939 C 25.868844,79.95466 34.290809,86.367957 44.209428,86.367957 C 52.133821,86.367957 59.101143,82.275788 63.115853,76.089615 z"
+ style="fill:none"
+ id="path646" />
+ <path
+ d="M 56.917822,57.857972 C 56.694636,58.606299 56.378238,59.562056 54.970858,60.285439 C 54.766053,60.390468 54.687282,60.218483 54.781807,60.057003 C 55.313513,59.151133 55.409352,58.925322 55.562956,58.568226 C 55.779577,58.047022 55.892482,57.303946 55.463179,55.754779 C 54.615075,52.707643 52.849285,48.633855 51.564001,47.31181 C 50.32598,46.037029 48.079686,45.677306 46.050011,46.19851 C 45.302998,46.390186 43.839164,47.151642 41.126807,46.539852 C 36.433353,45.483004 35.738853,47.833013 35.468405,48.857041 C 35.197956,49.881066 34.552032,52.791666 34.552032,52.791666 C 34.33541,53.977174 34.05446,56.038354 41.342116,57.426043 C 44.737158,58.071966 44.910455,58.950266 45.060119,59.58175 C 45.329254,60.712117 45.761183,61.360667 46.245627,61.682316 C 46.731383,62.006591 46.245627,62.274414 45.707356,62.329554 C 44.260592,62.480532 38.917273,60.947118 35.754607,59.151133 C 33.168283,57.570457 33.124958,56.147322 33.717056,54.939495 C 29.808689,54.516756 26.877084
,55.304469 26.345378,57.155594 C 25.431631,60.330077 33.324513,65.752165 42.311003,68.473712 C 51.741236,71.329172 61.440606,69.336258 62.519772,63.40872 C 63.012093,60.71343 60.74348,58.721829 56.917822,57.857972 z M 42.458041,52.053841 C 39.857276,52.241579 39.586829,52.52253 39.099759,53.041108 C 38.411824,53.772368 37.507268,52.090601 37.507268,52.090601 C 36.965059,51.976382 36.306006,51.100708 36.661789,50.2828 C 37.012321,49.474082 37.658246,49.71696 37.860425,49.969029 C 38.107242,50.274923 38.633697,50.777747 39.315068,50.759366 C 39.997753,50.7423 40.785465,50.597886 41.884324,50.597886 C 42.998938,50.597886 43.745953,51.014061 43.789276,51.371156 C 43.823411,51.675739 43.698689,51.964567 42.458041,52.053841 z M 45.191406,47.754243 C 45.187466,47.754243 45.183528,47.755556 45.179589,47.755556 C 45.138891,47.755556 45.107383,47.72536 45.107383,47.687287 C 45.107383,47.659717 45.123137,47.636085 45.14808,47.625583 C 45.652218,47.359073 46.404482,47.147704 47.265715,4
7.059743 C 47.524347,47.032172 47.776416,47.019045 48.019294,47.016418 C 48.062617,47.016418 48.103316,47.016418 48.147954,47.017731 C 49.592094,47.04924 50.746092,47.622957 50.729025,48.299078 C 50.711958,48.973884 49.527763,49.495088 48.084936,49.46358 C 47.617561,49.453076 47.179067,49.384807 46.800965,49.275842 C 46.756328,49.264025 46.723506,49.225952 46.723506,49.181315 C 46.723506,49.135365 46.756328,49.097292 46.802278,49.08679 C 47.702895,48.878046 48.310747,48.538016 48.268737,48.215055 C 48.212283,47.788376 47.03334,47.557315 45.637776,47.696476 C 45.484171,47.713544 45.334507,47.733237 45.191406,47.754243 z"
+ style="fill:#cc0000"
+ id="path648" />
+ <use
+ transform="translate(-94.61853,1.913321)"
+ id="use4312"
+ x="0"
+ y="0"
+ width="744.09448"
+ height="1052.3622"
+ xlink:href="#path650" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/rhlogo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/rhlogo.png
new file mode 100644
index 0000000..ecd4856
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/rhlogo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/shade.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/shine.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/stock-go-back.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/stock-go-forward.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/stock-go-up.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/stock-home.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/title_logo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/title_logo.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/warning.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/warning.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/watermark-draft.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ABRT-Main_Window.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ABRT-Main_Window.png
new file mode 100644
index 0000000..4e5b8b9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ABRT-Main_Window.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png
new file mode 100644
index 0000000..f737aff
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-Authentication.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-Authentication.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-Options.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-Options.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-SSSD_Settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-SSSD_Settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-User_Information.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-User_Information.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Change_Runtime_Boolean.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Change_Runtime_Boolean.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/FirefoxWithKerberosSSO.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/FirefoxWithKerberosSSO.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-Software_Log_Viewer.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-Software_Log_Viewer.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-Software_Update_Preferences.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-Software_Update_Preferences.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-add_remove_software.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-add_remove_software.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-additional_updates.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-additional_updates.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-authenticate.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-authenticate.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-filters-only_available.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-filters-only_available.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-filters-only_end_user.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-filters-only_end_user.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-htop.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-htop.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-installing_a_package_group.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-installing_a_package_group.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-removal_in_progress.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-removal_in_progress.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-remove.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-remove.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-removing_a_package.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-removing_a_package.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-software_update.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-software_update.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-updates_available.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Graphical_Package_Management-updates_available.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Load_New_Policy.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Load_New_Policy.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Connect_automatically.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Connect_automatically.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-IPv4_Settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-IPv4_Settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-Wired.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-Wired.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Addresses.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Addresses.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DHCP_Client_ID.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DHCP_Client_ID.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DNS_Servers.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DNS_Servers.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Method.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Method.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Routes.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Routes.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Search_domains.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Search_domains.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-System_eth0-Routes.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-System_eth0-Routes.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-applet_states.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-applet_states.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/PS2port.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/PS2port.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/SCLogin.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/SCLogin.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/SCLoginEnrollment.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/SCLoginEnrollment.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/SELinux_Decision_Process.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/SELinux_Decision_Process.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Screenshot-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Screenshot-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Screenshot-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Screenshot-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Users_Groups-Create_New_User.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Users_Groups-Create_New_User.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Users_Groups-User_Manager.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/Users_Groups-User_Manager.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/abrt_main.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/abrt_main.png
new file mode 100644
index 0000000..9d1e162
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/abrt_main.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/apol-DIF.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/apol-DIF.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/apol-TE-rule-search.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/apol-TE-rule-search.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/apol-plain.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/apol-plain.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/arrow.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/arrow.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/auth-panel.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/auth-panel.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authconfig-auth.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authconfig-auth.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authconfig-options.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authconfig-options.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authconfig-user-info.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authconfig-user-info.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authconfig_LDAP_kerb.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authconfig_LDAP_kerb.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authconfig_advanced.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authconfig_advanced.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authicon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/authicon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/bugworkflow_new4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/bugworkflow_new4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/bugworkflow_old8.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/bugworkflow_old8.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-authentication.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-authentication.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-ntsysv.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-ntsysv.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_configuration.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_configuration.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_disabled.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_disabled.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_enabled.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_enabled.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_running.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_running.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_selected.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_selected.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_stopped.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_stopped.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_unknown.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_unknown.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_wrong.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/controlling-access-to-services-service_wrong.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/date-and-time-authentication.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/date-and-time-authentication.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/date-and-time-date_and_time.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/date-and-time-date_and_time.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/date-and-time-network_time_protocol.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/date-and-time-network_time_protocol.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/date-and-time-time_zone.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/date-and-time-time_zone.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/devicemngr.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/devicemngr.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/display-dualhead.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/display-dualhead.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/display-hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/display-hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/display-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/display-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/flask-arch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/flask-arch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/flow-diagram.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/flow-diagram.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey1.png
new file mode 100644
index 0000000..bb1da26
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey10.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey10.png
new file mode 100644
index 0000000..87cf00e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey10.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey11.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey11.png
new file mode 100644
index 0000000..f1203af
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey11.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey2.png
new file mode 100644
index 0000000..6cbcf6f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey3.png
new file mode 100644
index 0000000..4755ef0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey4.png
new file mode 100644
index 0000000..a818c6c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey5.png
new file mode 100644
index 0000000..fb564a6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey6.png
new file mode 100644
index 0000000..214184c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey7.png
new file mode 100644
index 0000000..eade526
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey8.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey8.png
new file mode 100644
index 0000000..7d71471
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey8.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey9.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey9.png
new file mode 100644
index 0000000..048a406
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/genkey9.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-print-manager-list.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-print-manager-list.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-print-manager.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-print-manager.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-print-queue.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-print-queue.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-system-monitor-filesystems.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-system-monitor-filesystems.png
new file mode 100644
index 0000000..18854ce
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-system-monitor-filesystems.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-system-monitor-memory.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-system-monitor-memory.png
new file mode 100644
index 0000000..e432ce7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-system-monitor-memory.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-system-monitor-processes.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-system-monitor-processes.png
new file mode 100644
index 0000000..90e9df7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/gnome-system-monitor-processes.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/group-new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/group-new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/group-properties.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/group-properties.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-directories-add.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-directories-add.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-directories.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-directories.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-environment.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-environment.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-general-options.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-general-options.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-listen.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-listen.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-logging.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-logging.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-main.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-main.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-server.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-server.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-siteconfig.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-siteconfig.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-tuning.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-tuning.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-virtualhosts-ssl.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-virtualhosts-ssl.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-virtualhosts.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/httpd-virtualhosts.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/hwbrowser.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/hwbrowser.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/icon-greencheck-pkgs.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/icon-greencheck-pkgs.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/icon-install-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/icon-install-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/icon-removal-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/icon-removal-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/image_needed.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/image_needed.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/individual-pkgs.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/individual-pkgs.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/install-depend-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/install-depend-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/install-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/install-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-applet-addition.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-applet-addition.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-applet-observation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-applet-observation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-applet-selection.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-applet-selection.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-break-take.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-break-take.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-break.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-break.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts-default.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts-default.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts-new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts-new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts-prioritize.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts-prioritize.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts-separate.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts-separate.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts-test.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts-test.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/keyboard-configuration-layouts.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvg.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvg.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-auto-config.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-auto-config.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main10.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main10.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main12.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main12.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main13.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main13.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main14.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main14.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main15.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main15.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main16.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main16.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main17.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main17.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main18.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main18.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main21.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main21.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main23.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main23.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main26.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main26.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main27.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main27.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main28.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main28.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main30.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main30.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main31.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main31.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main32.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main32.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main33.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main33.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main34.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main34.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main36.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main36.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-main7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-boot.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-boot.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-done.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-done.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-free.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-free.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-lv.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-lv.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-lvdone.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-lvdone.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-postboot.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-postboot.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-pv01.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-pv01.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-pvdone.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-pvdone.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-vg.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm-manual-vg.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm/lvg.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm/lvg.svg
new file mode 100644
index 0000000..f564769
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm/lvols.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvm/lvols.svg
new file mode 100644
index 0000000..a2c6a8f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvols.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/lvols.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/mouseconfig.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/mouseconfig.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/n-t-n-ipsec-diagram.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/n-t-n-ipsec-diagram.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/n-to-n-ipsec-local.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/n-to-n-ipsec-local.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/n-to-n-ipsec-remote.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/n-to-n-ipsec-remote.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-aliases.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-aliases.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-dns.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-dns.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-ethernet-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-ethernet-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-ethernet.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-ethernet.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-home-profile.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-home-profile.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-hosts.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-hosts.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-isdn-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-isdn-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-isdn.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-isdn.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-modem-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-modem-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-modem.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-modem.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-office-profile.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-office-profile.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-tokenring-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-tokenring-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-tokenring.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-tokenring.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-tonline1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-tonline1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-tonlineAcctsetup.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-tonlineAcctsetup.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-tonlineProvidertab.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-tonlineProvidertab.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-wireless-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-wireless-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-wireless.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-wireless.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-xdsl-selectdevicetype.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-xdsl-selectdevicetype.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-xdsl-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-xdsl-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-xdsl.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat-xdsl.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/neat.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/nfs-add.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/nfs-add.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/nfs-general-options.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/nfs-general-options.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/nfs-server-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/nfs-server-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/nfs-user-access.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/nfs-user-access.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/oprof-start-config.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/oprof-start-config.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/oprof-start-setup.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/oprof-start-setup.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/originals/Graphical_Package_Management-software_update.xcf b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/originals/Graphical_Package_Management-software_update.xcf differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/package-selections.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/package-selections.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/pam-icon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/pam-icon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/print-manager-menu.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/print-manager-menu.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-add-printer.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-add-printer.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-config1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-config1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-config2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-config2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-config3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-config3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-config4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-config4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-config5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-config5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-default-icon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-default-icon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-edit.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-edit.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-ipp.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-ipp.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-jetdirect.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-jetdirect.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-local.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-local.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-lpd.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-lpd.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-main.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-main.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-ncp.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-ncp.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-queue-name.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-queue-name.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-select-model.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-select-model.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-sharing-general.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-sharing-general.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-sharing-hosts.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-sharing-hosts.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-sharing-queue.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-sharing-queue.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-smb.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-smb.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-test-page.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printconf-test-page.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printer-notification-icon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/printer-notification-icon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-boot-error.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-boot-error.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-final.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-final.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-free.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-free.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-lvm-final.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-lvm-final.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-mntpt.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-mntpt.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-part-add.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-part-add.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-part-bootready.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-part-bootready.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-part-opt.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-part-opt.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-part-opt2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/raid-manual-part-opt2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-config-packages.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-config-packages.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-config-users.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-config-users.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-add.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-add.png
new file mode 100644
index 0000000..7df9952
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-add.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-monitoring1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-monitoring1.png
new file mode 100644
index 0000000..2deec4c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-monitoring1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-monitoring2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-monitoring2.png
new file mode 100644
index 0000000..164b4c7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-monitoring2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-monitoring3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-monitoring3.png
new file mode 100644
index 0000000..e7daa2f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-monitoring3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-prefs.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-prefs.png
new file mode 100644
index 0000000..b3a1ff4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-prefs.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-sample.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-sample.png
new file mode 100644
index 0000000..99d2abd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer-sample.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer.png
new file mode 100644
index 0000000..e12c3ac
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-logviewer.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-optional-packages.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/redhat-optional-packages.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/registering.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/registering.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/relevant-errata.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/relevant-errata.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/removal-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/removal-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/remove-depend-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/remove-depend-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/rh-securitylevel.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/rh-securitylevel.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/rhl-common/networkconfig/n-t-n-ipsec-diagram.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/s-c-samba-basic.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/s-c-samba-basic.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/s-c-samba-create-share.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/s-c-samba-create-share.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/s-c-samba-security.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/s-c-samba-security.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/s-c-samba-users.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/s-c-samba-users.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/s-c-samba.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/s-c-samba.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/samba-nautilus-machines.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/samba-nautilus-machines.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/samba-nautilus.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/samba-nautilus.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/seaudit-Edit-filter.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/seaudit-Edit-filter.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/seaudit-Query-policy.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/seaudit-Query-policy.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/seaudit-Select-target-type-filtering.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/seaudit-Select-target-type-filtering.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/seaudit-View-filtering.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/seaudit-View-filtering.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/seaudit-plain.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/seaudit-plain.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/sec-ipsec-host2host.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/sec-ipsec-host2host.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/security-intro-to-mls.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/security-intro-to-mls.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/security-mls-data-flow.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/security-mls-data-flow.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/serialport.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/serialport.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/serv-config.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/serv-config.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ssh-passphrase-prompt.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ssh-passphrase-prompt.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ssh-startup-applications-add.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ssh-startup-applications-add.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ssh-startup-applications-check.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ssh-startup-applications-check.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ssh-startup-applications.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/ssh-startup-applications.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/switchmail-gui.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/switchmail-gui.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/system-config-nfs.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/system-config-nfs.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/tcp_wrap_diagram.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/tcp_wrap_diagram.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/usbport.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/usbport.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/user-new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/user-new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/user-properties.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/user-properties.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/user_pass_groups.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/user_pass_groups.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/user_pass_info.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/user_pass_info.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/images/your-rhn.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html-single/Deployment_Guide/images/your-rhn.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html
new file mode 100644
index 0000000..be68f5e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html
@@ -0,0 +1,14583 @@
+<?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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><meta name="description" content="The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 13." /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a c
lass="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="id2445309" 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 Draft Documentation</span> <span class="productnumber"></span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id2445309" 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 13</h2></div><p class="edition">Edition 13.0.1</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 cla
ss="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
+
+ </h3></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id782125" 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">
+ 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 Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 13.
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#id828957">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#id721124">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#id966299">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#id726864">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#id1780581">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-RedHat-We_Need_Feedback">2. We Need Feedback!</a></span></dt><dd><dl><dt><span class="section"><a href="#id788952">2.1. Technical Review Requests</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#sec-Checking_For_Updates">1.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="#sec-Updating_Packages">1.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="#sec-Updating_Security-Related_Packages">1.1.3. Updating Security-Related Packages</a></span></dt><dt><span class="section"><a href="#sec-Preserving_Configuration_File_Changes">1.1.4. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">1.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Searching_Listing_and_Displaying_Package_Information">1.2.1. Searching, Listing and Displaying Package Information</a></span></d
t><dt><span class="section"><a href="#sec-Installing">1.2.2. Installing</a></span></dt><dt><span class="section"><a href="#sec-Removing">1.2.3. Removing</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">1.3. Configuring Yum and Yum Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_main_Options">1.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="#sec-Setting_repository_Options">1.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="#sec-Using_Yum_Variables">1.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Yum_Repository">1.3.4. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Yum_Plugins">1.4. Yum Plugins</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">1.4.1. Enabling, Configuring and
Disabling Yum Plugins</a></span></dt><dt><span class="section"><a href="#sec-Installing_More_Yum_Plugins">1.4.2. Installing More Yum Plugins</a></span></dt><dt><span class="section"><a href="#sec-Plugin_Descriptions">1.4.3. Plugin Descriptions</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#sec-Refreshing_Software_Sources_Yum_Repositories">2.2.1. Refreshing Software Sources (Yum Repositories)</a></span></dt><dt><span class="section"><a href="#sec-Finding_Packages_with_Filters">2.2.2. Finding Packages with Filt
ers</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Packages_and_Dependencies">2.2.3. Installing and Removing Packages (and Dependencies)</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Package_Groups">2.2.4. Installing and Removing Package Groups</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Transaction_Log">2.2.5. Viewing the Transaction Log</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a hr
ef="#s2-rpm-finding">3.2.1. Finding RPM Packages</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Upgrading">3.2.2. Installing and Upgrading</a></span></dt><dt><span class="section"><a href="#sec-Configuration_File_Changes">3.2.3. Configuration File Changes</a></span></dt><dt><span class="section"><a href="#s2-rpm-uninstalling">3.2.4. Uninstalling</a></span></dt><dt><span class="section"><a href="#s2-rpm-freshening">3.2.5. Freshening</a></span></dt><dt><span class="section"><a href="#s2-rpm-querying">3.2.6. Querying</a></span></dt><dt><span class="section"><a href="#s2-rpm-verifying">3.2.7. Verifying</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-check-rpm-sig">3.3. Checking a Package's Signature</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-keys-importing">3.3.1. Importing Keys</a></span></dt><dt><span class="section"><a href="#s2-keys-checking">3.3.2. Verifying Signature of Packages</a></span></dt></dl></dd><dt><span cl
ass="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><dd><dl><dt><span class="section"><a href="#s2-rpm-installed-docs">3.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-rpm-useful-websites">3.5.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-rpm-related-books">3.5.3. Related Books</a></span></dt></dl></dd></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><dd><dl><dt><span class="section"><a href="#s2-networkscripts-interfaces-eth0">4.2.1. Ethernet Interfaces</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-chan">4.2.2. Channel Bonding Interfaces</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-alias">4.2.3. Alias and Clone Files</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-ppp0">4.2.4. Dialup Interfaces</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-other">4.2.5. Other Interfaces</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#s2-networkscripts-docs-inst">4.6.1. Installed Documentation</a></span></dt></dl></dd></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><dd><dl><dt><span class="section"><a href="#sec-Connecting_to_a_Network">5.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="#sec-Configuring_New_and_Editing_Existing_Connections">5.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Automatically">5.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="#sec-U
ser_and_System_Connections">5.2.4. User and System Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Establishing_Connections">5.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Wired_Ethernet_Connection">5.3.1. Establishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Wireless_Connection">5.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Mobile_Broadband_Connection">5.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_VPN_Connection">5.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_DSL_Connection">5.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_Routes">5.3.6. Establishing Routes</a></span></dt></dl
></dd><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">5.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_802.1x_Security">5.4.1. Configuring 802.1x Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Wireless_Security">5.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_PPP_Point-to-Point_Settings">5.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv4_Settings">5.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv6_Settings">5.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-NetworkManager_Architecture">5.5. NetworkManager Architecture</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Controlling_Access_to_Services">6. Controlling Access to
Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-services-runlevels">6.1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="#s1-services-configuring">6.2. Configuring the Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-serviceconf">6.2.1. Using the <span class="application"><strong>Service Configuration</strong></span> Utility</a></span></dt><dt><span class="section"><a href="#s2-services-ntsysv">6.2.2. Using the <span class="application"><strong>ntsysv</strong></span> Utility</a></span></dt><dt><span class="section"><a href="#s2-services-chkconfig">6.2.3. Using the <code class="command">chkconfig</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">6.3. Running the Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-service">6.3.1. Using the <span class="application"><strong>service</strong></span> Utility</a></span><
/dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-additional-resources-installed">6.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">6.4.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-The_BIND_DNS_Server">7. The BIND DNS Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-bind-introduction">7.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-introduction-zones">7.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="#s2-bind-introduction-nameservers">7.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="#s2-bind-introduction-bind">7.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-namedconf">7.2
. <code class="filename">/etc/named.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-namedconf-state">7.2.1. Common Statement Types</a></span></dt><dt><span class="section"><a href="#s2-bind-namedconf-state-other">7.2.2. Other Statement Types</a></span></dt><dt><span class="section"><a href="#s2-bind-namedconf-comm">7.2.3. Comment Tags</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-zone">7.3. Zone Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-zone-directives">7.3.1. Zone File Directives</a></span></dt><dt><span class="section"><a href="#s3-bind-zone-rr">7.3.2. Zone File Resource Records</a></span></dt><dt><span class="section"><a href="#s2-bind-zone-examples">7.3.3. Example Zone File</a></span></dt><dt><span class="section"><a href="#s2-bind-configuration-zone-reverse">7.3.4. Reverse Name Resolution Zone Files</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-rndc">7.4. Using
<code class="command">rndc</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-rndc-configuration-namedconf">7.4.1. Configuring <code class="filename">/etc/named.conf</code> </a></span></dt><dt><span class="section"><a href="#s2-bind-rndc-configuration-rndcconf">7.4.2. Configuring <code class="filename">/etc/rndc.conf</code> </a></span></dt><dt><span class="section"><a href="#s2-bind-rndc-options">7.4.3. Command Line Options</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-features">7.5. Advanced Features of BIND</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-features-protocol">7.5.1. DNS Protocol Enhancements</a></span></dt><dt><span class="section"><a href="#s2-bind-features-views">7.5.2. Multiple Views</a></span></dt><dt><span class="section"><a href="#s2-bind-features-security">7.5.3. Security</a></span></dt><dt><span class="section"><a href="#s2-bind-features-ipv6">7.5.4. IP version 6</a></span></dt></dl></d
d><dt><span class="section"><a href="#s1-bind-mistakes">7.6. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="#s1-bind-additional-resources">7.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-installed-docs">7.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-bind-useful-websites">7.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-bind-related-books">7.7.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-OpenSSH">8. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ssh-protocol">8.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">8.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">8.1.2. Main Features</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">8.1.3. Protocol Versions</a></span></dt><dt><spa
n class="section"><a href="#s2-ssh-conn">8.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-configuration">8.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">8.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-sshd">8.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">8.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">8.2.4. Using a Key-Based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">8.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-ssh">8.3.1. Using the <code class="command">ssh</code> Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">8.3.2. Us
ing the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-sftp">8.3.3. Using the <code class="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">8.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">8.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">8.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">8.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-openssh-installed-docs">8.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-openssh-useful-websites">8.5.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Samba">9. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#samba
-rgs-overview">9.1. Introduction to Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-abilities">9.1.1. Samba Features</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-daemons">9.2. Samba Daemons and Related Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-services">9.2.1. Samba Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-connect-share">9.3. Connecting to a Samba Share</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-connect-share-cmdline">9.3.1. Command Line</a></span></dt><dt><span class="section"><a href="#s1-samba-mounting">9.3.2. Mounting the Share</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-configuring">9.4. Configuring a Samba Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-configuring-gui">9.4.1. Graphical Configuration</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring-
cmdline">9.4.2. Command Line Configuration</a></span></dt><dt><span class="section"><a href="#s2-samba-encrypted-passwords">9.4.3. Encrypted Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-startstop">9.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="#s1-samba-servers">9.6. Samba Server Types and the <code class="command">smb.conf</code> File</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-standalone">9.6.1. Stand-alone Server</a></span></dt><dt><span class="section"><a href="#s2-samba-domain-member">9.6.2. Domain Member Server</a></span></dt><dt><span class="section"><a href="#s2-samba-domain-controller">9.6.3. Domain Controller</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-security-modes">9.7. Samba Security Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-user-level">9.7.1. User-Level Security</a></span></dt><dt><span class="section"><a href
="#s2-samba-share-level">9.7.2. Share-Level Security</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-account-info-dbs">9.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="#s1-samba-network-browsing">9.9. Samba Network Browsing</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-domain-browsing">9.9.1. Domain Browsing</a></span></dt><dt><span class="section"><a href="#s2-samba-wins">9.9.2. WINS (Windows Internetworking Name Server)</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-cups">9.10. Samba with CUPS Printing Support</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-cups-smb.conf">9.10.1. Simple <code class="filename">smb.conf</code> Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-programs">9.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="#s1-samba-resources">9.12. Additional Resources</a><
/span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-resources-installed">9.12.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-samba-resources-published">9.12.2. Related Books</a></span></dt><dt><span class="section"><a href="#s2-samba-resources-community">9.12.3. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Dynamic_Host_Configuration_Protocol_DHCP">10. Dynamic Host Configuration Protocol (DHCP)</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-dhcp-why">10.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-server">10.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#config-file">10.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="#lease-database">10.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="#id729711">10.2.3. Starting and Stopping the Server</a></sp
an></dt><dt><span class="section"><a href="#dhcp-relay-agent">10.2.4. DHCP Relay Agent</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp-configuring-client">10.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="#sect-Configuring_a_Multihomed_DHCP_Server">10.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-dns_Host_Configuration">10.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">10.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="#s1-dhcp-additional-resources">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-dhcp-installed-docs">10.6.1. Installed Documentation</a></span></dt></dl></dd></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-http
d-v2">11.1. Apache HTTP Server 2.2</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-httpd-v2-features">11.1.1. Features of Apache HTTP Server 2.2</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-httpd-mig">11.2. Migrating Apache HTTP Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-httpd-v22-mig">11.2.1. Migrating Apache HTTP Server 2.0 Configuration Files</a></span></dt><dt><span class="section"><a href="#s3-httpd-v2-mig">11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-apache-startstop">11.3. Starting and Stopping <code class="command">httpd</code> </a></span></dt><dt><span class="section"><a href="#s1-apache-config-ui">11.4. Apache HTTP Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-httpd-basic-settings">11.4.1. Basic Settings</a></span></dt><dt><span class="section"><a href="#s2-httpd-de
fault-settings">11.4.2. Default Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-apache-config">11.5. Configuration Directives in <code class="filename">httpd.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-tips">11.5.1. General Configuration Tips</a></span></dt><dt><span class="section"><a href="#s2-apache-sslcommands">11.5.2. Configuration Directives for SSL</a></span></dt><dt><span class="section"><a href="#s2-apache-mpm-containers">11.5.3. MPM Specific Server-Pool Directives</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-apache-addmods">11.6. Adding Modules</a></span></dt><dt><span class="section"><a href="#s1-apache-virtualhosts">11.7. Virtual Hosts</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-settingupvhosts">11.7.1. Setting Up Virtual Hosts</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-httpd-secure-server">11.8. Apache HTTP Secure Server Configuration</
a></span></dt><dd><dl><dt><span class="section"><a href="#s2-secureserver-optionalpackages">11.8.1. An Overview of Security-Related Packages</a></span></dt><dt><span class="section"><a href="#s2-secureserver-overview-certs">11.8.2. An Overview of Certificates and Security</a></span></dt><dt><span class="section"><a href="#s1-secureserver-oldcert">11.8.3. Using Pre-Existing Keys and Certificates</a></span></dt><dt><span class="section"><a href="#s2-secureserver-certs">11.8.4. Types of Certificates</a></span></dt><dt><span class="section"><a href="#s2-secureserver-generatingkey">11.8.5. Generating a Key</a></span></dt><dt><span class="section"><a href="#s1-use-new-key">11.8.6. How to configure the server to use the new key</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-apache-additional-resources">11.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-additional-resources-web">11.9.1. Useful Websites</a></span></dt></dl
></dd></dl></dd><dt><span class="chapter"><a href="#ch-FTP">12. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ftp-protocol">12.1. The File Transfer Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol-multiport">12.1.1. Multiple Ports, Multiple Modes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ftp-servers">12.2. FTP Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-servers-vsftpd">12.2.1. <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">12.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s1-ftp-vsftpd-start">12.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-vsftpd-start-multi">12.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </a></span></dt></dl></d
d><dt><span class="section"><a href="#s1-ftp-vsftpd-conf">12.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-daemon">12.5.1. Daemon Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-login">12.5.2. Log In Options and Access Controls</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-anon">12.5.3. Anonymous User Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-usr">12.5.4. Local User Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-dir">12.5.5. Directory Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-file">12.5.6. File Transfer Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-log">12.5.7. Logging Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-net">12.5.8. Network
Options</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ftp-resources">12.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-installed-documentation">12.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-ftp-useful-websites">12.6.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-email">13. Email</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-email-protocols">13.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-protocols-send">13.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">13.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">13.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-types-mta">13.2.1. Mail Transport Agent</a></span></dt
><dt><span class="section"><a href="#s2-email-types-mda">13.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">13.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mta">13.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-sendmail">13.3.1. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-postfix">13.3.2. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">13.3.3. Fetchmail</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-switchmail">13.4. Mail Transport Agent (MTA) Configuration</a></span></dt><dt><span class="section"><a href="#s1-email-mda">13.5. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">13.5.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="#s2-email-procmail-recipes">13.
5.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">13.6. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">13.6.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">13.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">13.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">13.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-email-related-books">13.7.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Lightweight_Directory_Access_Protocol_LDAP">14. Lightweight Directory Access Protocol (LDAP)</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ldap-adv">14.1. Why Use LDAP?</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ldap-v
3">14.1.1. OpenLDAP Features</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ldap-terminology">14.2. LDAP Terminology</a></span></dt><dt><span class="section"><a href="#s1-ldap-daemonsutils">14.3. OpenLDAP Daemons and Utilities</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-pam-nss">14.3.1. NSS, PAM, and LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-other-apps">14.3.2. PHP4, LDAP, and the Apache HTTP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-applications">14.3.3. LDAP Client Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ldap-files">14.4. OpenLDAP Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-ldap-files-schemas">14.5. The <code class="filename">/etc/openldap/schema/</code> Directory</a></span></dt><dt><span class="section"><a href="#s1-ldap-quickstart">14.6. OpenLDAP Setup Overview</a></span></dt><dd><dl><dt><span class="section"><a href="#s
2-ldap-files-slapd-conf">14.6.1. Editing <code class="filename">/etc/openldap/slapd.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ldap-pam">14.7. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-pamd">14.7.1. PAM and LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-migrate">14.7.2. Migrating Old Authentication Information to LDAP Format</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ldap-migrate">14.8. Migrating Directories from Earlier Releases</a></span></dt><dt><span class="section"><a href="#s1-ldap-additional-resources">14.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-installed-docs">14.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-ldap-additional-resources-web">14.9.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-ldap-related-books">
14.9.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Authentication_Configuration">15. Authentication Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool">15.1. The Authentication Configuration Tool</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">15.1.1. Identity & Authentication</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">15.1.2. Advanced Options</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Command_Line_Version">15.1.3. Command Line Version</a></span></dt></dl></dd><dt><span class="section"><a href="#chap-SSSD_User_Guide-Introduction">15.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introdu
ction-What_is_SSSD">15.2.1. What is SSSD?</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introduction-SSSD_Features">15.2.2. SSSD Features</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Setting_Up_SSSD">15.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Services">15.2.4. Configuring Services</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Domains">15.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">15.2.6. Setting up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Troubleshooting">15.2.7. Troubleshooting</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">15.2.8. SSSD Configuration File Format</a></spa
n></dt></dl></dd></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="#ch-Console_Access">16. Console Access</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-access-console-ctrlaltdel">16.1. Disabling Shutdown Via <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span></a></span></dt><dt><span class="section"><a href="#s1-access-console-program">16.2. Disabling Console Program Access</a></span></dt><dt><span class="section"><a href="#s1-access-console-define">16.3. Defining the Console</a></span></dt><dt><span class="section"><a href="#s1-access-console-files">16.4. Making Files Accessible From the Console</a></span></dt><dt><span class="section"><a href="#s1-access-console-enable">16.5. Enabling Console Access for Other Applications</a></span></dt><dt><span class="section"><
a href="#s1-access-floppy">16.6. The <code class="filename">floppy</code> Group</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-proc">17. The <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-proc-virtual">17.1. A Virtual File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-viewing">17.1.1. Viewing Virtual Files</a></span></dt><dt><span class="section"><a href="#s2-proc-change">17.1.2. Changing Virtual Files</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-topfiles">17.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-buddyinfo">17.2.1. <code class="filename">/proc/buddyinfo</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-cmdline">17.2.2. <code class="filename">/proc/cmdline</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-cp
uinfo">17.2.3. <code class="filename">/proc/cpuinfo</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-crypto">17.2.4. <code class="filename">/proc/crypto</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-devices">17.2.5. <code class="filename">/proc/devices</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dma">17.2.6. <code class="filename">/proc/dma</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-execdomains">17.2.7. <code class="filename">/proc/execdomains</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-fb">17.2.8. <code class="filename">/proc/fb</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-filesystems">17.2.9. <code class="filename">/proc/filesystems</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-interrupts">17.2.10. <code class="filename">/proc/interrupts</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-iomem">17.2.
11. <code class="filename">/proc/iomem</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-ioports">17.2.12. <code class="filename">/proc/ioports</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-kcore">17.2.13. <code class="filename">/proc/kcore</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-kmsg">17.2.14. <code class="filename">/proc/kmsg</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-loadavg">17.2.15. <code class="filename">/proc/loadavg</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-locks">17.2.16. <code class="filename">/proc/locks</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-mdstat">17.2.17. <code class="filename">/proc/mdstat</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-meminfo">17.2.18. <code class="filename">/proc/meminfo</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-misc">17.2.19. <code class="filename
">/proc/misc</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-modules">17.2.20. <code class="filename">/proc/modules</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-mounts">17.2.21. <code class="filename">/proc/mounts</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-mtrr">17.2.22. <code class="filename">/proc/mtrr</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-partitions">17.2.23. <code class="filename">/proc/partitions</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-pci">17.2.24. <code class="filename">/proc/pci</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-slabinfo">17.2.25. <code class="filename">/proc/slabinfo</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-stat">17.2.26. <code class="filename">/proc/stat</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-swaps">17.2.27. <code class="filename">/proc/swaps</code> </a
></span></dt><dt><span class="section"><a href="#s2-proc-sysrq-trigger">17.2.28. <code class="filename">/proc/sysrq-trigger</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-uptime">17.2.29. <code class="filename">/proc/uptime</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-version">17.2.30. <code class="filename">/proc/version</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-directories">17.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-processdirs">17.3.1. Process Directories</a></span></dt><dt><span class="section"><a href="#s2-proc-dir-bus">17.3.2. <code class="filename">/proc/bus/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-driver">17.3.3. <code class="filename">/proc/driver/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-fs">17.3.4. <code class="filename">/proc/fs</code>
</a></span></dt><dt><span class="section"><a href="#s2-proc-dir-irq">17.3.5. <code class="filename">/proc/irq/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-net">17.3.6. <code class="filename">/proc/net/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-scsi">17.3.7. <code class="filename">/proc/scsi/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-sys">17.3.8. <code class="filename">/proc/sys/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-sysvipc">17.3.9. <code class="filename">/proc/sysvipc/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-tty">17.3.10. <code class="filename">/proc/tty/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-pid">17.3.11. <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-sysctl">17.4. Using the <code class="com
mand">sysctl</code> Command</a></span></dt><dt><span class="section"><a href="#s1-proc-additional-resources">17.5. References</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><dd><dl><dt><span class="section"><a href="#s2-sysconfig-arpwatch">18.1.1. <code class="filename">/etc/sysconfig/arpwatch</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-authconfig">18.1.2. <code class="filename">/etc/sysconfig/authconfig</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-autofs">18.1.3. <code class="filename">/etc/sysconfig/autofs</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-clock">18.1.4. <code class="filename">/etc/sysconfig/clock</code> </a></span></dt><dt><span class="sectio
n"><a href="#s2-sysconfig-desktop">18.1.5. <code class="filename">/etc/sysconfig/desktop</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-dhcpd">18.1.6. <code class="filename">/etc/sysconfig/dhcpd</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-firewall">18.1.7. <code class="filename">/etc/sysconfig/firstboot</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-i18n">18.1.8. <code class="filename">/etc/sysconfig/i18n</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-init">18.1.9. <code class="filename">/etc/sysconfig/init</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-ip6tables">18.1.10. <code class="filename">/etc/sysconfig/ip6tables-config</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-kybd">18.1.11. <code class="filename">/etc/sysconfig/keyboard</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-named">18.1.1
2. <code class="filename">/etc/sysconfig/named</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-network">18.1.13. <code class="filename">/etc/sysconfig/network</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-ntpd">18.1.14. <code class="filename">/etc/sysconfig/ntpd</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-radvd">18.1.15. <code class="filename">/etc/sysconfig/radvd</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-samba">18.1.16. <code class="filename">/etc/sysconfig/samba</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-selinux">18.1.17. <code class="filename">/etc/sysconfig/selinux</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-sendmail">18.1.18. <code class="filename">/etc/sysconfig/sendmail</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-spamd">18.1.19. <code class="filename">/etc/sysconfig/spam
assassin</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-squid">18.1.20. <code class="filename">/etc/sysconfig/squid</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-rcu">18.1.21. <code class="filename">/etc/sysconfig/system-config-users</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-vncservers">18.1.22. <code class="filename">/etc/sysconfig/vncservers</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-xinetd">18.1.23. <code class="filename">/etc/sysconfig/xinetd</code> </a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#s2-sysconfig-installed-documentation">18.3.1. Installed Documentation</a>
</span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Date_and_Time_Configuration">19. 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">19.1. Date/Time Properties Tool</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Date_and_Time">19.1.1. Date and Time Properties</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Network_Time_Protocol">19.1.2. Network Time Protocol Properties</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Time_Zone">19.1.3. Time Zone Properties</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration">19.2. Command Line Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time"
>19.2.1. Date and Time Setup</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">19.2.2. Network Time Protocol Setup</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Keyboard_Configuration">20. Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-keyboard-layout">20.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="#s1-keyboard-indicator">20.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="#s1-keyboard-break">20.3. Setting Up a Typing Break</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-The_X_Window_System">21. The X Window System</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-x-server">21.1. The X11R7.1 Release</a></span></dt><dt><span class="section"><a href="#s1-x-clients">21.2. Desktop Environments and Window Managers</a></span></d
t><dd><dl><dt><span class="section"><a href="#s2-x-clients-desktop">21.2.1. Desktop Environments</a></span></dt><dt><span class="section"><a href="#s2-x-clients-winmanagers">21.2.2. Window Managers</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-server-configuration">21.3. X Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-server-config-xorg.conf">21.3.1. <code class="filename">xorg.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-fonts">21.4. Fonts</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-fonts-fontconfig">21.4.1. Fontconfig</a></span></dt><dt><span class="section"><a href="#s2-x-fonts-core">21.4.2. Core X Font System</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-runlevels">21.5. Runlevels and X</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-runlevels-3">21.5.1. Runlevel 3</a></span></dt><dt><span class="section"><a href="#s2
-x-runlevels-5">21.5.2. Runlevel 5</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-additional-resources">21.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-installed-documentation">21.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-x-useful-websites">21.6.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ers_and_Groups">22. Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-users-configui">22.1. User and Group Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-users-user-new">22.1.1. Adding a New User</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-new">22.1.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-properties">22.1.3. Modifying Group Properties</a></span></dt></dl></dd><dt><span class="s
ection"><a href="#s1-users-tools">22.2. User and Group Management Tools</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-cmd-line">22.2.1. Command Line Configuration</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-process">22.2.2. Explaining the Process</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-standard-users">22.3. Standard Users</a></span></dt><dt><span class="section"><a href="#s1-users-groups-standard-groups">22.4. Standard Groups</a></span></dt><dt><span class="section"><a href="#s1-users-groups-private-groups">22.5. User Private Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-rationale">22.5.1. Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-shadow-utilities">22.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="#s1-users-groups-additional-resources">22.7. Additional Resources</a></span></dt>
<dd><dl><dt><span class="section"><a href="#s2-users-groups-documentation">22.7.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Printer_Configuration">23. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-printing-local-printer">23.1. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">23.2. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">23.3. Adding a Samba (SMB) Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-jetdirect-printer">23.4. Adding a JetDirect Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">23.5. Selecting the Printer Model and Finishing</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-printing-confirm">23.5.1. Confirming Printer Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-prin
ting-test-page">23.6. Printing a Test Page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">23.7. Modifying Existing Printers</a></span></dt><dd><dl><dt><span class="section"><a href="#id1520769">23.7.1. The <span class="guilabel"><strong>Settings</strong></span> Tab</a></span></dt><dt><span class="section"><a href="#id995216">23.7.2. The <span class="guilabel"><strong>Policies</strong></span> Tab</a></span></dt><dt><span class="section"><a href="#id881428">23.7.3. The <span class="guilabel"><strong>Access Control</strong></span> Tab</a></span></dt><dt><span class="section"><a href="#id1712276">23.7.4. The <span class="guilabel"><strong>Printer</strong></span> and <span class="guilabel"><strong>Job Options</strong></span>Tab</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-printing-managing">23.8. Managing Print Jobs</a></span></dt><dt><span class="section"><a href="#s1-printing-additional-resources">23.9. Additional Resources</a></span></d
t><dd><dl><dt><span class="section"><a href="#s2-printing-installed-docs">23.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-printing-useful-websites">23.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Automated_Tasks">24. Automated Tasks</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-autotasks-cron">24.1. Cron</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-cron-configuring">24.1.1. Configuring Cron Tasks</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">24.1.2. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-service">24.1.3. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-at-batch">24.2. At and Batch</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-at-configuring">24.2.1. Configuring At Jobs</a></sp
an></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuring">24.2.2. Configuring Batch Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">24.2.3. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">24.2.4. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">24.2.5. Controlling Access to At and Batch</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-service">24.2.6. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">24.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-installed-docs">24.3.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Log_Files">25. Log Files</a></span></dt><dd><dl><dt><span class="sect
ion"><a href="#s1-logfiles-locating">25.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-viewing">25.2. Viewing Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-adding">25.3. Adding a Log File</a></span></dt><dt><span class="section"><a href="#s1-logfiles-examining">25.4. Monitoring Log Files</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">26. Gathering System Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-sysinfo-system-processes">26.1. System Processes</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-memory-usage">26.2. Memory Usage</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-filesystems">26.3. File Systems</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-hardware">26.4. Hardware</a></span><
/dt><dt><span class="section"><a href="#s1-sysinfo-additional-resources">26.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-installed-docs">26.5.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-OProfile">27. OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-overview-tools">27.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="#s1-oprofile-configuring">27.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">27.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">27.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">27.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">27.3. Starting and Stopping OPr
ofile</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">27.4. Saving Data</a></span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">27.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">27.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opreport-single">27.5.2. Using <code class="command">opreport</code> on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">27.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opannotate">27.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">27.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="#s1-oprof
ile-example-usage">27.7. Example Usage</a></span></dt><dt><span class="section"><a href="#s1-oprofile-gui">27.8. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1-oprofile-additional-resources">27.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-installed-docs">27.9.1. Installed Docs</a></span></dt><dt><span class="section"><a href="#s2-oprofile-useful-websites">27.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-abrt">28. ABRT</a></span></dt><dd><dl><dt><span class="section"><a href="#id2002784">28.1. Overview</a></span></dt><dt><span class="section"><a href="#id677272">28.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="#configuring">28.3. Configuring ABRT</a></span></dt><dt><span class="section"><a href="#id1986935">28.4. Plugins and Sending Crash Reports</a></span></dt><dt><span class="section"><a href="#id1189335">28.5. Usin
g the Command Line Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#id1189349">28.5.1. Viewing Crashes</a></span></dt><dt><span class="section"><a href="#id737384">28.5.2. Reporting Crashes</a></span></dt><dt><span class="section"><a href="#id570721">28.5.3. Deleting Crashes</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#pt-kernel-configuration">V. Kernel and Driver Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Manually_Upgrading_the_Kernel">29. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kernel-packages">29.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">29.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">29.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">29.4. Performing the Upgrade<
/a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image">29.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">29.6. Verifying the Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-kernel-boot-loader-grub">29.6.1. Configuring the GRUB Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-iseries">29.6.2. Configuring the <span class="trademark">OS/400</span>® Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-pseries">29.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-General_Parameters_and_Modules">30. General Parameters and Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kernel-module-utils">30.1. Kernel Module Utilities</a></span></dt><dt><span class="section"><a href="#s1-kernel-modules-persistant">3
0.2. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#s1-modules-parameters-specifying">30.3. Specifying Module Parameters</a></span></dt><dt><span class="section"><a href="#s1-modules-scsi">30.4. Storage parameters</a></span></dt><dt><span class="section"><a href="#s1-modules-ethernet">30.5. Ethernet Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-modules-multiple-eth">30.5.1. Using Multiple Ethernet Cards</a></span></dt><dt><span class="section"><a href="#s2-modules-bonding">30.5.2. The Channel Bonding Module</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">30.6. 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="#id735310">Index</a></span></dt></dl></div><div xml:lang="en-US" class="preface" title="Preface" id="id828957" lang="en-US"><div
class="titlepage"><div><div><h1 id="id828957" 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="id721124">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="id966299">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>F1</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>F7</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="id726864">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="id1780581">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"><h2>Note</h2><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 class="important"><h2>Important</h2><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' won't cause data loss but may cause irritation and frustration.
+ </div></div><div class="warning"><h2>Warning</h2><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </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="id1125172" 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">13</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="id788952">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><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><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><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><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><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://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Deployment_Guide/index.html">http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Deployment_Guide/index.html</a>.
+ </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="id988441" class="indexterm"></a><div class="para">
+ Welcome to the <em class="citetitle">Fedora Deployment Guide</em>.
+ </div><div class="para">
+ The Fedora Deployment Guide contains information on how to customize your Fedora 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">
+ Setting up a network interface card (NIC)
+ </div></li><li class="listitem"><div class="para">
+ Configuring a Virtual Private Network (VPN)
+ </div></li><li class="listitem"><div class="para">
+ Configuring Samba shares
+ </div></li><li class="listitem"><div class="para">
+ Managing your software with RPM
+ </div></li><li class="listitem"><div class="para">
+ Determining information about your system
+ </div></li><li class="listitem"><div class="para">
+ Upgrading your 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">
+ File systems
+ </div></li><li class="listitem"><div class="para">
+ Package management
+ </div></li><li class="listitem"><div class="para">
+ Network-related configuration
+ </div></li><li class="listitem"><div class="para">
+ System configuration
+ </div></li><li class="listitem"><div class="para">
+ System monitoring
+ </div></li><li class="listitem"><div class="para">
+ Kernel and Driver Configuration
+ </div></li><li class="listitem"><div class="para">
+ Security and Authentication
+ </div></li><li class="listitem"><div class="para">
+ Red Hat Training and Certification
+ </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 Installation Guide</em>.
+ </div></div><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES" class="part" title="Part I. Package Management" id="pt-pkg-management" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES"><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="id2444732"><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><dd><dl><dt><span class="section"><a href="#sec-Checking_For_Updates">1.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="#sec-Updating_Packages">1.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="#sec-Updating_Security-Related_Packages">1.1.3. Updating Security-Related Packages</a></span></dt><dt><span class="section"><a href="#sec-Preserving_Configuration_File_Changes">1.1.4. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">1.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Searching_Listing_and_Displaying_Package_Information">1.2.1. Sea
rching, Listing and Displaying Package Information</a></span></dt><dt><span class="section"><a href="#sec-Installing">1.2.2. Installing</a></span></dt><dt><span class="section"><a href="#sec-Removing">1.2.3. Removing</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">1.3. Configuring Yum and Yum Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_main_Options">1.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="#sec-Setting_repository_Options">1.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="#sec-Using_Yum_Variables">1.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Yum_Repository">1.3.4. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Yum_Plugins">1.4. Yum Plugins</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Enabling_Configur
ing_and_Disabling_Yum_Plugins">1.4.1. Enabling, Configuring and Disabling Yum Plugins</a></span></dt><dt><span class="section"><a href="#sec-Installing_More_Yum_Plugins">1.4.2. Installing More Yum Plugins</a></span></dt><dt><span class="section"><a href="#sec-Plugin_Descriptions">1.4.3. Plugin Descriptions</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#sec-Refreshing_Software_Sources_Yum_Repositories">2.2.1. Refreshing Software Sources (Yum Repositories)</a></span></dt><dt><span class="section"><a href="#sec-
Finding_Packages_with_Filters">2.2.2. Finding Packages with Filters</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Packages_and_Dependencies">2.2.3. Installing and Removing Packages (and Dependencies)</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Package_Groups">2.2.4. Installing and Removing Package Groups</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Transaction_Log">2.2.5. Viewing the Transaction Log</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#s2-rpm-finding">3.2.1. Finding RPM Packages</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Upgrading">3.2.2. Installing and Upgrading</a></span></dt><dt><span class="section"><a href="#sec-Configuration_File_Changes">3.2.3. Configuration File Changes</a></span></dt><dt><span class="section"><a href="#s2-rpm-uninstalling">3.2.4. Uninstalling</a></span></dt><dt><span class="section"><a href="#s2-rpm-freshening">3.2.5. Freshening</a></span></dt><dt><span class="section"><a href="#s2-rpm-querying">3.2.6. Querying</a></span></dt><dt><span class="section"><a href="#s2-rpm-verifying">3.2.7. Verifying</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-check-rpm-sig">3.3. Checking a Package's Signature</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-keys-importing">3.3.1. Importing Keys</a></span></dt><dt><span class="section"><a href="#s2-keys-checking">3.3.2. Verif
ying Signature of Packages</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#s2-rpm-installed-docs">3.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-rpm-useful-websites">3.5.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-rpm-related-books">3.5.3. Related Books</a></span></dt></dl></dd></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><dd><dl><dt><span class="section"><a href
="#sec-Checking_For_Updates">1.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="#sec-Updating_Packages">1.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="#sec-Updating_Security-Related_Packages">1.1.3. Updating Security-Related Packages</a></span></dt><dt><span class="section"><a href="#sec-Preserving_Configuration_File_Changes">1.1.4. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">1.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Searching_Listing_and_Displaying_Package_Information">1.2.1. Searching, Listing and Displaying Package Information</a></span></dt><dt><span class="section"><a href="#sec-Installing">1.2.2. Installing</a></span></dt><dt><span class="section"><a href="#sec-Removing">1.2.3. Removing</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_R
epositories">1.3. Configuring Yum and Yum Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_main_Options">1.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="#sec-Setting_repository_Options">1.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="#sec-Using_Yum_Variables">1.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Yum_Repository">1.3.4. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Yum_Plugins">1.4. Yum Plugins</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">1.4.1. Enabling, Configuring and Disabling Yum Plugins</a></span></dt><dt><span class="section"><a href="#sec-Installing_More_Yum_Plugins">1.4.2. Installing More Yum Plugins</a></span></dt><dt><span class="section"><a href="#sec-Plugin_Descriptions">1.4.3. Plugin Descriptions
</a></span></dt></dl></dd><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"><h2>Secure Package Management with GPG-Signed Packages</h2><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 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="id868324" 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"><h2>Note: <span class="application"><strong>Yum</strong></span> and Superuser Privileges</h2><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><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="id2401353" 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="id725142" 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"><h2>Important: Updating and Installing Kernels with Yum</h2><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></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="id1476665" 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"><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum update</code>
+</pre></div><h6>Example 1.1. Updating all packages at once</h6></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="id1004352" class="indexterm"></a><a id="id1004364" 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="id908940" 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="id642898" 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="id741517" class="indexterm"></a><a id="id741529" 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="id1003472" class="indexterm"></a><a id="id1003483" class="indexterm"></a><a id="id1003495" class="indexterm"></a><a id="id650529" class="indexterm"></a><a id="id650540" class="indexterm"></a><a id="id650552" 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="id727144" class="indexterm"></a>
+ <a id="id727159" 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="id749247" class="indexterm"></a>
+ <a id="id749263" class="indexterm"></a>
+ <code class="command">yum list</code> and related commands provide information about packages, package groups, and repositories.
+ </div><div class="note"><h2>Tip: Filtering Results with Glob Expressions</h2><a id="id939484" class="indexterm"></a><a id="id688778" 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 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><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"><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><h6>Example 1.2. Filtering results using a single glob expression with two escaped wildcard characters</h6></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"><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><h6>Example 1.3. Filtering results using a double-quoted glob expression</h6></div><br class="example-break" /></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"><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><h6>Example 1.4. Listing all ABRT addons and plugins using glob expressions</h6></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="id896508" class="indexterm"></a>
+ <a id="id649184" 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="id1018359" class="indexterm"></a>
+ <a id="id1018374" 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="id753799" class="indexterm"></a>
+ <a id="id753815" 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="id926778" class="indexterm"></a>
+ <a id="id926794" class="indexterm"></a>
+ List all package groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum repolist</code> —
+ <a id="id636538" class="indexterm"></a>
+ <a id="id636554" 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="id994647" class="indexterm"></a>
+ <a id="id994663" 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="id638294" class="indexterm"></a>
+ <a id="id638310" 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 13, 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="id606363" class="indexterm"></a><a id="id606375" 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">more_names</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"><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><h6>Example 1.5. Finding which package owns a file and installing it</h6></div><br class="example-break" /><div class="note"><h2>Note</h2><div class="para">
+ <code class="command">yum provides</code> is the same as <code class="command">yum whatprovides</code>.
+ </div></div><div class="note"><h2>Tip: yum provides/whatprovides and Glob Expressions</h2><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><h4>Installing a Package Group</h4><a id="id750590" class="indexterm"></a><a id="id750602" 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"><h2>Not all packages used in examples may be available on RHN</h2><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><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="id891507" class="indexterm"></a><a id="id1018004" class="indexterm"></a><div class="para">
+ <code class="command">yum remove <package_name></code> <a id="id1018022" class="indexterm"></a>
+ <a id="id1980828" 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"><h2>Warning: Removing a Package when Other Packages Depend On It</h2><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><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"><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><h6>Example 1.6. Alternative but equivalent ways of removing a package group</h6></div><br class="example-break" /><div class="important"><h2>Smart package group removal</h2><a id="id677516" class="indexterm"></a><a id="id677528" 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 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="id572917" class="indexterm"></a><a id="id572929" 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="id1004900" 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><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><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><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><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><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><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><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><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>.
+ </div></dd><dt><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 is therefore <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><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><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><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><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="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><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><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="id1010324" 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><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><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><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">
+ Here is another useful-but-optional [<em class="replaceable"><code>repository</code></em>] options:
+ </div><div class="variablelist"><dl><dt><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="id948474" 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><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><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><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><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="id1001474" 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"><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></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="id829001" 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="id998152" class="indexterm"></a><a id="id998164" class="indexterm"></a><a id="id998176" 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="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"><div class="example-contents"><pre class="screen">
+[main]
+enabled=1
+</pre></div><h6>Example 1.7. A minimal <span class="application">Yum</span> plugin configuration file</h6></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"><div class="example-contents"><pre class="screen">~]# <code class="command">yum update --disableplugin=presto</code>
+</pre></div><h6>Example 1.8. Disabling the presto plugin while running yum update</h6></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="id626875" 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 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 c
lass="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="id884769" 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>refresh-packagekit (PackageKit-yum-plugin)</h4><a id="id611433" 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="id576735" 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="id995268" class="indexterm"></a><div class="variablelist"><dl><dt><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><span class="term"> Managing Software with <span class="application"><strong>Yum</strong></span> — <a href="http://docs.fedoraproject.org/yum/en/index.html">http://docs.fedoraproject.org/yum/en/index.html</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><dd><dl><dt><span class="section"><a href="#sec-Refreshing_Software_Sources_Yum_Repositories">2.2.1. Refreshing Software Sources (Yum Repositories)</a></span></dt><dt><span class="section"><a href="#sec-Finding_Packages_with_Filters">2.2.2. Finding Packages with Filters</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Removing_Packages_and_Dependencies">2.2.3. Installing and Removing Packages (and Dependencies)</a></span></dt><dt><span class="section"><a href="#sec-
Installing_and_Removing_Package_Groups">2.2.4. Installing and Removing Package Groups</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Transaction_Log">2.2.5. Viewing the Transaction Log</a></span></dt></dl></dd><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="id649220" 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="id577711" class="indexterm"></a>
+ <a id="id692974" class="indexterm"></a>
+ <a id="id651690" class="indexterm"></a>
+ <a id="id1997937" class="indexterm"></a>
+ <a id="id601760" class="indexterm"></a>
+ <a id="id795620" class="indexterm"></a>
+ <a id="id597295" class="indexterm"></a>
+ <a id="id884294" class="indexterm"></a>
+ <a id="id902672" class="indexterm"></a>
+ <a id="id916784" 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="id838823" class="indexterm"></a>
+ <a id="id838839" 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="id618167" class="indexterm"></a>
+ <a id="id618182" 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="id563119" class="indexterm"></a>
+ <a id="id563134" class="indexterm"></a>
+ <a id="id563146" class="indexterm"></a>
+ utilizes the fine-grained user authentication
+ <a id="id890763" 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="id985564" 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="id701368" class="indexterm"></a><a id="id701379" 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="id915593" class="indexterm"></a>
+ <a id="id915604" 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"><h2>Showing Source RPM, Test and Debuginfo Repositories</h2><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 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="id1936600" 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="id935579" class="indexterm"></a>
+ <a id="id935595" class="indexterm"></a>
+ <a id="id567490" class="indexterm"></a>
+ <a id="id567505" class="indexterm"></a>
+ <a id="id567521" 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="id752559" class="indexterm"></a>
+ <a id="id752575" class="indexterm"></a>
+ <a id="id1010904" 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><span class="term"> <span class="guisubmenu"><strong>Graphical</strong></span> <a id="id761483" 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><span class="term"> <span class="guisubmenu"><strong>Free</strong></span> <a id="id806697" 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><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="id931102" 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><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="id1936521" 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"><h2>Important: Using the Only newest items filter</h2><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></dd><dt><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="id1860414" 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 <em class="replaceable"><code>x</code></em>86 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="id820628" class="indexterm"></a><a id="id820640" 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="id574790" 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 installed</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"><h2>Warning: Removing a Package when Other Packages Depend On It</h2><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 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="id870854" class="indexterm"></a><a id="id812098" class="indexterm"></a><a id="id812110" class="indexterm"></a><a id="id812121" 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 <span class="guibutton"><strong>Apply</strong></span>ing.
+ </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="id651075" class="indexterm"></a>
+ <a id="id651087" 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="id863326" 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"><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>Session and Startup</strong></span>, <span class="guilabel"><strong>Application Autostart</strong></span> tab
+ </div>
+
+ </td><td align="left">
+ gpk-update-icon
+ </td></tr></tbody></table></div><h6>Table 2.1. PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands</h6></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><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><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><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 6. Controlling Access to Services">Chapter 6, <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><dd><dl><dt><span class="section"><a href="#s2-rpm-finding">3.2.1. Finding RPM Packages</a></span></dt><dt><span class="section"><a href="#sec-Installing_and_Upgrading">3.2.2. Installing and Upgrading</a></span></dt><dt><span class="section"><a href="#sec-Configuration_File_Changes">3.2.3. Configuration File Changes</a></span></dt><dt><span class="section"><a href="#s2-rpm-uninstalling">3.2.4. Uninstalling</a></span></dt><dt><span class="section"><a href="#s2-rpm-freshening">3.2.5. Freshening</a></span></dt><dt><span class="section"><a href="#s2-rpm-querying">3.2.6. Querying</a></span></dt>
<dt><span class="section"><a href="#s2-rpm-verifying">3.2.7. Verifying</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-check-rpm-sig">3.3. Checking a Package's Signature</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-keys-importing">3.3.1. Importing Keys</a></span></dt><dt><span class="section"><a href="#s2-keys-checking">3.3.2. Verifying Signature of Packages</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#s2-rpm-installed-docs">3.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-rpm-useful-websites">3.5.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-rpm-related-books">3.5.3. Related Books</a></span></dt></dl></dd></dl></div><a id="id689078" cla
ss="indexterm"></a><a id="id689072" class="indexterm"></a><div class="para">
+ The <em class="firstterm">RPM Package Manager</em> (RPM) is an open packaging system
+ <a id="id689058" 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 13. 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"><h2>Use Yum Instead of RPM Whenever Possible</h2><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="id797436" 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 class="important"><h2>Important</h2><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 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="id859441" 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"><h2>Note</h2><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 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="id859395" 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><span class="term">Upgradability
+ <a id="id834367" 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><span class="term">Powerful Querying
+ <a id="id703514" 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><span class="term"> System Verification
+ <a id="id988938" 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><span class="term">Pristine Sources
+ <a id="id1226108" 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="id917657" 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="id1191918" class="indexterm"></a><a id="id1015986" 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="id569700" class="indexterm"></a>
+ <a id="id1871690" 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="id726871" class="indexterm"></a>
+ <a id="id698204" 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"><h2>Important</h2><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></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="id945094" class="indexterm"></a><a id="id891700" class="indexterm"></a><a id="id869346" class="indexterm"></a><a id="id771296" class="indexterm"></a><div class="para">
+ RPM packages typically have file names
+ <a id="id582582" class="indexterm"></a>
+ like <code class="filename">tree-1.5.3-2.fc13.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">fc13</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.fc13.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.fc13.x86_64.rpm</code>
+</pre><div class="note"><h2>Use -Uvh for nicely-formatted RPM installs</h2><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 marks.
+ </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"><h2>Always use the -i (install) option to install new kernel packages!</h2><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 29. Manually Upgrading the Kernel">Chapter 29, <i>Manually Upgrading the Kernel</i></a>.
+ </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.fc13.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.fc13.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.fc13.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="id1006184" class="indexterm"></a>
+ <a id="id1484003" class="indexterm"></a>
+ , the following output is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ package tree-1.5.3-2.fc13.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.fc13.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="id2394478" 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="id569126" class="indexterm"></a>
+ <a id="id710914" class="indexterm"></a>
+ , the following is displayed:
+ </div><pre class="screen">Preparing... ##################################################
+ file /usr/bin/foobar from install of foo-1.0-1.fc13.x86_64 conflicts
+with file from package bar-3.1.1.fc13.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.fc13.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="id1985123" class="indexterm"></a><a id="id1194982" class="indexterm"></a><div class="para">
+ RPM packages may sometimes depend on other packages
+ <a id="id1010167" class="indexterm"></a>
+ <a id="id845204" 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.fc13.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.fc13.x86_64.rpm bar-3.1.1.fc13.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.fc13.i586.rpm</pre><div class="warning"><h2>Warning: Forcing Package Installation</h2><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 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="id586677" class="indexterm"></a><a id="id1987061" class="indexterm"></a><div class="para">
+ Because RPM performs intelligent upgrading of packages with configuration files
+ <a id="id1898088" 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.fc13.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.fc13.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="id902284" class="indexterm"></a><a id="id610914" class="indexterm"></a><a id="id688640" class="indexterm"></a><a id="id1484016" 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"><h2>Note</h2><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.fc13.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 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.fc13.x86_64
+ libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc13.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc13.x86_64
+ ghostscript is needed by (installed) printer-filters-1.1-4.fc13.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.fc13.x86_64</pre><div class="warning"><h2>Warning: Forcing Package Installation</h2><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 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="id1025724" class="indexterm"></a><a id="id1025736" 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.fc13.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="id2401066" class="indexterm"></a><a id="id2401078" 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.fc13.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="id654662" class="indexterm"></a><a id="id660029" 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.fc13.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="id910817" 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="id626178" class="indexterm"></a><a id="id626192" class="indexterm"></a><a id="id995362" 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="id1010134" class="indexterm"></a><a id="id1010146" 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="id1117841" class="indexterm"></a><a id="id746412" 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="id925919" class="indexterm"></a><a id="id925931" 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.fc13.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="id1024365" class="indexterm"></a><a id="id834670" class="indexterm"></a><a id="id834681" 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="id910769" class="indexterm"></a><a id="id910781" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qip crontabs-1.10-31.fc13.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="id891710" class="indexterm"></a><a id="id891722" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qlp crontabs-1.10-31.fc13.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="id1987056" 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="id1681176" 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="id869331" class="indexterm"></a><a id="id902570" class="indexterm"></a><div class="variablelist"><dl><dt><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><span class="term"> <em class="citetitle">Red Hat RPM Guide</em> — <a href="http://docs.fedoraproject.org/drafts/rpm-guide-en/">http://docs.fedoraproject.org/drafts/rpm-guide-en/</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 xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,de-DE,ru-RU,fr-FR,zh-CN,it-IT,es-ES,ja-JP" class="part" title="Part II. Network-Related Configuration" id="pt-network-related-config" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,de-DE,ru-RU,fr-FR,zh-CN,it-IT,es-ES,ja-JP"><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="id989361"><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><dd><dl><dt><span class="section"><a href="#s2-networkscripts-interfaces-eth0">4.2.1. Ethernet Interfaces</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-chan">4.2.2. Channel Bonding Interfaces</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-alias">4.2.3. Alias and Clone Files</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-ppp0">4.2.4. Dialup Interfaces</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-other">4.2.5. Other Interfaces</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#s2-networkscripts-docs-inst">4.6.1. Installed Documentation</a></span></dt></dl></dd></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><dd><dl><dt><span class="section"><a href="#sec-Connecting_to_a_Network">5
.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="#sec-Configuring_New_and_Editing_Existing_Connections">5.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Automatically">5.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="#sec-User_and_System_Connections">5.2.4. User and System Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Establishing_Connections">5.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Wired_Ethernet_Connection">5.3.1. Establishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Wireless_Connection">5.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Mobile_Broadband_Connection">5.3.3. Establishing a Mobile Bro
adband Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_VPN_Connection">5.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_DSL_Connection">5.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_Routes">5.3.6. Establishing Routes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">5.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_802.1x_Security">5.4.1. Configuring 802.1x Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Wireless_Security">5.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_PPP_Point-to-Point_Settings">5.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv4_Settings">5.4.4. Con
figuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv6_Settings">5.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-NetworkManager_Architecture">5.5. NetworkManager Architecture</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Controlling_Access_to_Services">6. Controlling Access to Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-services-runlevels">6.1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="#s1-services-configuring">6.2. Configuring the Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-serviceconf">6.2.1. Using the <span class="application"><strong>Service Configuration</strong></span> Utility</a></span></dt><dt><span class="section"><a href="#s2-services-ntsysv">6.2.2. Using the <span class="application"><strong>ntsysv</strong></span> Utility</a></span></dt><dt><span class="se
ction"><a href="#s2-services-chkconfig">6.2.3. Using the <code class="command">chkconfig</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">6.3. Running the Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-service">6.3.1. Using the <span class="application"><strong>service</strong></span> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-additional-resources-installed">6.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">6.4.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-The_BIND_DNS_Server">7. The BIND DNS Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-bind-introduction">7.1. Introduction to DNS</a></span></dt><dd><dl>
<dt><span class="section"><a href="#s2-bind-introduction-zones">7.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="#s2-bind-introduction-nameservers">7.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="#s2-bind-introduction-bind">7.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-namedconf">7.2. <code class="filename">/etc/named.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-namedconf-state">7.2.1. Common Statement Types</a></span></dt><dt><span class="section"><a href="#s2-bind-namedconf-state-other">7.2.2. Other Statement Types</a></span></dt><dt><span class="section"><a href="#s2-bind-namedconf-comm">7.2.3. Comment Tags</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-zone">7.3. Zone Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-zone-directives">7.3.1. Zone File Directives</a></span></dt><dt><span class
="section"><a href="#s3-bind-zone-rr">7.3.2. Zone File Resource Records</a></span></dt><dt><span class="section"><a href="#s2-bind-zone-examples">7.3.3. Example Zone File</a></span></dt><dt><span class="section"><a href="#s2-bind-configuration-zone-reverse">7.3.4. Reverse Name Resolution Zone Files</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-rndc">7.4. Using <code class="command">rndc</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-rndc-configuration-namedconf">7.4.1. Configuring <code class="filename">/etc/named.conf</code> </a></span></dt><dt><span class="section"><a href="#s2-bind-rndc-configuration-rndcconf">7.4.2. Configuring <code class="filename">/etc/rndc.conf</code> </a></span></dt><dt><span class="section"><a href="#s2-bind-rndc-options">7.4.3. Command Line Options</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-features">7.5. Advanced Features of BIND</a></span></dt><dd><dl><dt><span class="s
ection"><a href="#s2-bind-features-protocol">7.5.1. DNS Protocol Enhancements</a></span></dt><dt><span class="section"><a href="#s2-bind-features-views">7.5.2. Multiple Views</a></span></dt><dt><span class="section"><a href="#s2-bind-features-security">7.5.3. Security</a></span></dt><dt><span class="section"><a href="#s2-bind-features-ipv6">7.5.4. IP version 6</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-mistakes">7.6. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="#s1-bind-additional-resources">7.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-installed-docs">7.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-bind-useful-websites">7.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-bind-related-books">7.7.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-OpenSSH">8. OpenSSH</a></spa
n></dt><dd><dl><dt><span class="section"><a href="#s1-ssh-protocol">8.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">8.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">8.1.2. Main Features</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">8.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">8.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-configuration">8.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">8.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-sshd">8.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">8.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="#
s2-ssh-configuration-keypairs">8.2.4. Using a Key-Based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">8.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-ssh">8.3.1. Using the <code class="command">ssh</code> Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">8.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-sftp">8.3.3. Using the <code class="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">8.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">8.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">8.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">8.5. Addition
al Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-openssh-installed-docs">8.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-openssh-useful-websites">8.5.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Samba">9. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#samba-rgs-overview">9.1. Introduction to Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-abilities">9.1.1. Samba Features</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-daemons">9.2. Samba Daemons and Related Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-services">9.2.1. Samba Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-connect-share">9.3. Connecting to a Samba Share</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-connect-share-cmdline">9.3.1. Command Line</a></span></d
t><dt><span class="section"><a href="#s1-samba-mounting">9.3.2. Mounting the Share</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-configuring">9.4. Configuring a Samba Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-configuring-gui">9.4.1. Graphical Configuration</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring-cmdline">9.4.2. Command Line Configuration</a></span></dt><dt><span class="section"><a href="#s2-samba-encrypted-passwords">9.4.3. Encrypted Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-startstop">9.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="#s1-samba-servers">9.6. Samba Server Types and the <code class="command">smb.conf</code> File</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-standalone">9.6.1. Stand-alone Server</a></span></dt><dt><span class="section"><a href="#s2-samba-domain-member">9.6.2. Domain
Member Server</a></span></dt><dt><span class="section"><a href="#s2-samba-domain-controller">9.6.3. Domain Controller</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-security-modes">9.7. Samba Security Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-user-level">9.7.1. User-Level Security</a></span></dt><dt><span class="section"><a href="#s2-samba-share-level">9.7.2. Share-Level Security</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-account-info-dbs">9.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="#s1-samba-network-browsing">9.9. Samba Network Browsing</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-domain-browsing">9.9.1. Domain Browsing</a></span></dt><dt><span class="section"><a href="#s2-samba-wins">9.9.2. WINS (Windows Internetworking Name Server)</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-cups">9.10. Samba wit
h CUPS Printing Support</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-cups-smb.conf">9.10.1. Simple <code class="filename">smb.conf</code> Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-programs">9.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="#s1-samba-resources">9.12. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-resources-installed">9.12.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-samba-resources-published">9.12.2. Related Books</a></span></dt><dt><span class="section"><a href="#s2-samba-resources-community">9.12.3. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Dynamic_Host_Configuration_Protocol_DHCP">10. Dynamic Host Configuration Protocol (DHCP)</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-dhcp-why">10.1. Why Use DHCP?</a></span></dt><dt><spa
n class="section"><a href="#s1-dhcp-configuring-server">10.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#config-file">10.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="#lease-database">10.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="#id729711">10.2.3. Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#dhcp-relay-agent">10.2.4. DHCP Relay Agent</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp-configuring-client">10.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="#sect-Configuring_a_Multihomed_DHCP_Server">10.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-dns_Host_Configuration">10.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">10.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span cla
ss="section"><a href="#s1-dhcp-additional-resources">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-dhcp-installed-docs">10.6.1. Installed Documentation</a></span></dt></dl></dd></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-httpd-v2">11.1. Apache HTTP Server 2.2</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-httpd-v2-features">11.1.1. Features of Apache HTTP Server 2.2</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-httpd-mig">11.2. Migrating Apache HTTP Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-httpd-v22-mig">11.2.1. Migrating Apache HTTP Server 2.0 Configuration Files</a></span></dt><dt><span class="section"><a href="#s3-httpd-v2-mig">11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></span></dt></dl></dd><dt><span class
="section"><a href="#s1-apache-startstop">11.3. Starting and Stopping <code class="command">httpd</code> </a></span></dt><dt><span class="section"><a href="#s1-apache-config-ui">11.4. Apache HTTP Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-httpd-basic-settings">11.4.1. Basic Settings</a></span></dt><dt><span class="section"><a href="#s2-httpd-default-settings">11.4.2. Default Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-apache-config">11.5. Configuration Directives in <code class="filename">httpd.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-tips">11.5.1. General Configuration Tips</a></span></dt><dt><span class="section"><a href="#s2-apache-sslcommands">11.5.2. Configuration Directives for SSL</a></span></dt><dt><span class="section"><a href="#s2-apache-mpm-containers">11.5.3. MPM Specific Server-Pool Directives</a></span></dt></dl></dd><dt><span class="section"><a href="#
s1-apache-addmods">11.6. Adding Modules</a></span></dt><dt><span class="section"><a href="#s1-apache-virtualhosts">11.7. Virtual Hosts</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-settingupvhosts">11.7.1. Setting Up Virtual Hosts</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-httpd-secure-server">11.8. Apache HTTP Secure Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-secureserver-optionalpackages">11.8.1. An Overview of Security-Related Packages</a></span></dt><dt><span class="section"><a href="#s2-secureserver-overview-certs">11.8.2. An Overview of Certificates and Security</a></span></dt><dt><span class="section"><a href="#s1-secureserver-oldcert">11.8.3. Using Pre-Existing Keys and Certificates</a></span></dt><dt><span class="section"><a href="#s2-secureserver-certs">11.8.4. Types of Certificates</a></span></dt><dt><span class="section"><a href="#s2-secureserver-generatingkey">11.8.5. Generating
a Key</a></span></dt><dt><span class="section"><a href="#s1-use-new-key">11.8.6. How to configure the server to use the new key</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-apache-additional-resources">11.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-additional-resources-web">11.9.1. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-FTP">12. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ftp-protocol">12.1. The File Transfer Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol-multiport">12.1.1. Multiple Ports, Multiple Modes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ftp-servers">12.2. FTP Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-servers-vsftpd">12.2.1. <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s2-ftp-vsftpd-con
f">12.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s1-ftp-vsftpd-start">12.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-vsftpd-start-multi">12.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ftp-vsftpd-conf">12.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-daemon">12.5.1. Daemon Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-login">12.5.2. Log In Options and Access Controls</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-anon">12.5.3. Anonymous User Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-usr">12.5.4. Local User Options</a></span></dt><dt><span c
lass="section"><a href="#s2-ftp-vsftpd-conf-opt-dir">12.5.5. Directory Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-file">12.5.6. File Transfer Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-log">12.5.7. Logging Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-net">12.5.8. Network Options</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ftp-resources">12.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-installed-documentation">12.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-ftp-useful-websites">12.6.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-email">13. Email</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-email-protocols">13.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-protoc
ols-send">13.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">13.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">13.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-types-mta">13.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mda">13.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">13.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mta">13.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-sendmail">13.3.1. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-postfix">13.3.2. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">13.3.3. Fetchmail</a></span></dt></dl></dd><dt><span clas
s="section"><a href="#s1-email-switchmail">13.4. Mail Transport Agent (MTA) Configuration</a></span></dt><dt><span class="section"><a href="#s1-email-mda">13.5. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">13.5.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="#s2-email-procmail-recipes">13.5.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">13.6. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">13.6.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">13.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">13.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">13.7.2. Useful Websites</a></span></dt><dt><span class="sectio
n"><a href="#s2-email-related-books">13.7.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Lightweight_Directory_Access_Protocol_LDAP">14. Lightweight Directory Access Protocol (LDAP)</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ldap-adv">14.1. Why Use LDAP?</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ldap-v3">14.1.1. OpenLDAP Features</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ldap-terminology">14.2. LDAP Terminology</a></span></dt><dt><span class="section"><a href="#s1-ldap-daemonsutils">14.3. OpenLDAP Daemons and Utilities</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-pam-nss">14.3.1. NSS, PAM, and LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-other-apps">14.3.2. PHP4, LDAP, and the Apache HTTP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-applications">14.3.3. LDAP Client Applications</a></span></dt></dl></dd><dt><sp
an class="section"><a href="#s1-ldap-files">14.4. OpenLDAP Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-ldap-files-schemas">14.5. The <code class="filename">/etc/openldap/schema/</code> Directory</a></span></dt><dt><span class="section"><a href="#s1-ldap-quickstart">14.6. OpenLDAP Setup Overview</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-files-slapd-conf">14.6.1. Editing <code class="filename">/etc/openldap/slapd.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ldap-pam">14.7. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-pamd">14.7.1. PAM and LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-migrate">14.7.2. Migrating Old Authentication Information to LDAP Format</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ldap-migrate">14.8. Migrating Directories from Earlier Releases</a></span></dt><dt><
span class="section"><a href="#s1-ldap-additional-resources">14.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-installed-docs">14.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-ldap-additional-resources-web">14.9.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-ldap-related-books">14.9.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Authentication_Configuration">15. Authentication Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool">15.1. The Authentication Configuration Tool</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">15.1.1. Identity & Authentication</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">15.1.2. Advanced
Options</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Command_Line_Version">15.1.3. Command Line Version</a></span></dt></dl></dd><dt><span class="section"><a href="#chap-SSSD_User_Guide-Introduction">15.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introduction-What_is_SSSD">15.2.1. What is SSSD?</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introduction-SSSD_Features">15.2.2. SSSD Features</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Setting_Up_SSSD">15.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Services">15.2.4. Configuring Services</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Domains">15.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Configurin
g_Domains-Setting_up_Kerberos_Authentication">15.2.6. Setting up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Troubleshooting">15.2.7. Troubleshooting</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">15.2.8. SSSD Configuration File Format</a></span></dt></dl></dd></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><dd><dl><dt><span class="section"><a href="#s2-networkscripts-interfaces-eth0">4.2.1. Ethe
rnet Interfaces</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-chan">4.2.2. Channel Bonding Interfaces</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-alias">4.2.3. Alias and Clone Files</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-ppp0">4.2.4. Dialup Interfaces</a></span></dt><dt><span class="section"><a href="#s2-networkscripts-interfaces-other">4.2.5. Other Interfaces</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#s2-netwo
rkscripts-docs-inst">4.6.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id739996" class="indexterm"></a><a id="id2399733" 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="id2394018" 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><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><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><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><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"><h2>Warning</h2><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 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="id808984" class="indexterm"></a><a id="id808998" 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="id892775" class="indexterm"></a><a id="id590659" 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><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><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><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><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><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><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><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"><h2>Note</h2><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></dd><dt><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><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><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><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><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><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><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><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><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><span class="term"> <code class="command">SLAVE=<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 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><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><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="id844544" class="indexterm"></a><a id="id844562" 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"><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><h6>Example 4.1. Sample ifcfg-bond0 interface configuration file</h6></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"><h2>Important: put all bonding module parameters in ifcfg-bondN files</h2><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="#s2-modules-bonding" title="30.5.2. The Channel Bonding Module">Section 30.5.2, “The Channel Bonding Module”</a>.
+ </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="id924566" class="indexterm"></a><a id="id924584" 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"><h2>Caution</h2><div class="para">
+ Alias interfaces do not support DHCP.
+ </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="id649558" 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><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><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><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><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><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><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><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><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><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><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><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><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><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><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"><h2>Warning</h2><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></dd><dt><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><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="id576888" class="indexterm"></a><a id="id576909" class="indexterm"></a><a id="id584910" class="indexterm"></a><a id="id584932" class="indexterm"></a><a id="id618278" 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"><h2>Caution</h2><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 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><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><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><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><span class="term"> <code class="filename">ifup-plip</code> </span></dt><dd><div class="para">
+ Brings up a PLIP interface.
+ </div></dd><dt><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><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><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><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><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><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"><h2>Warning</h2><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 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="id1010778">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"><h2>Duplicate Default Gateways</h2><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 class="formalpara"><h5 class="formalpara" id="id665429">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="id930402" 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="id575614" 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><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><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><dd><dl><dt><span class="section"><a href="#sec-Connecting_to_a_Network">5.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="#sec-Configuring_New_and_Editing_Existing_Connections">5.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="#sec-Connecting_to_a_Network_Automatically">5.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href
="#sec-User_and_System_Connections">5.2.4. User and System Connections</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Establishing_Connections">5.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Establishing_a_Wired_Ethernet_Connection">5.3.1. Establishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Wireless_Connection">5.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_Mobile_Broadband_Connection">5.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_VPN_Connection">5.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_a_DSL_Connection">5.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="#sec-Establishing_Routes">5.3.6. Establishing Routes</a></span><
/dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">5.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_802.1x_Security">5.4.1. Configuring 802.1x Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Wireless_Security">5.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="#sec-Configuring_PPP_Point-to-Point_Settings">5.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv4_Settings">5.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="#sec-Configuring_IPv6_Settings">5.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-NetworkManager_Architecture">5.5. NetworkManager Architecture</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 13, <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 13 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 6. Controlling Access to Services">Chapter 6, <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"><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"><h2>Tip: Increase security by making VPN connections user-specific</h2><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 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"><h6>Procedure 5.2. Changing a Connection to be User-Specific instead of System-Wide, or Vice-Versa</h6><div class="note"><h2>Depending on the system's policy, root privileges may be required</h2><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><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. Establishing Connections" id="sec-Establishing_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Establishing_Connections">5.3. Establishing Connections</h2></div></div></div><div class="section" title="5.3.1. Establishing a Wired (Ethernet) Connection" id="sec-Establishing_a_Wired_Ethernet_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_a_Wired_Ethernet_Connection">5.3.1. Establishing a Wired (Ethernet) Connection</h3></div></div></div><div class="para">
+ To establish an Ethernet connection, you need a network interface card (an NIC), a network cable (usually a Cat-5 cable), and a network to connect to (usually the Internet, through a router).
+ </div><div class="para">
+ You can configure a wired connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window and selecting the <span class="guilabel"><strong>Wired</strong></span> tab. For more information on opening the <span class="guilabel"><strong>Network Connections</strong></span> window via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet, or by running a shell command, refer to <a class="xref" href="#sec-Configuring_New_and_Editing_Existing_Connections" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Editing_Wired_Connection_1.png" align="middle" /><div class="caption"><div class="para">
+ Editing the newly-created Wired connection 1
+ </div></div></div><div class="para">
+ The system startup scripts create and configure a single wired connection called <span class="guilabel"><strong>System eth0</strong></span> by default on all systems. Although you can edit <span class="guilabel"><strong>System eth0</strong></span>, creating a new wired connection for your custom settings is recommended. You can create a new wired connection by selecting the <span class="guilabel"><strong>Wired</strong></span> tab and clicking the <span class="guibutton"><strong>Add</strong></span> button.
+ </div><div class="note"><h2>The dialog for adding and editing connections is the same</h2><div class="para">
+ When you add a new connection by clicking the <span class="guibutton"><strong>Add</strong></span> button, <span class="application"><strong>NetworkManager</strong></span> creates a new configuration file for that connection and then opens the same dialog that is used for editing an existing connection. There is no difference between these dialogs. In effect, you are always editing a connection; the difference only lies in whether that connection previously existed or was just created by <span class="application"><strong>NetworkManager</strong></span> when you clicked <span class="guibutton"><strong>Add</strong></span>.
+ </div></div><h4>Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — You can customize the name under which this connection is listed in the <span class="guilabel"><strong>Wired</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window by entering a descriptive name in the text-entry box. For example, you could create a wired connection with custom settings for the office called <em class="replaceable"><code>Wired Office</code></em>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the this connection when it is—or becomes—available. Refer to <a class="xref" href="#sec-Connecting_to_a_Network_Automatically" title="5.2.3. Connecting to a Network Automatically">Section 5.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="#sec-User_and_System_Connections" title="5.2.4. User and System Connections">Section 5.2.4, “User and System Connections”</a> for details.
+ </div></li></ul></div><h4>Configuring the Wired Tab</h4><div class="para">
+ The final two configurable settings are located within the <span class="guilabel"><strong>Wired</strong></span> tab itself: the first is a text-entry field where you can specify a MAC (Media Access Control) address, and the second allows you to specify the MTU (Maximum Transmission Unit) value. Normally, you can leave the <span class="guilabel"><strong>MAC address</strong></span> field blank and the <span class="guilabel"><strong>MTU</strong></span> set to <strong class="userinput"><code>automatic</code></strong>. These defaults will suffice unless you are associating a wired connection with a second or specific NIC, or performing advanced networking. In such cases, refer to the following descriptions:
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>MAC Address</strong></span> </span></dt><dd><div class="para">
+ Network hardware such as a Network Interface Card (NIC) has a unique MAC address (Media Access Control; also known as a <em class="firstterm">hardware address</em>) that identifies it to the system. Running the <code class="command">ip addr</code> command will show the MAC address associated with each interface. For example, in the following <code class="command">ip addr</code> output, the MAC address for the eth0 interface (which is <code class="computeroutput"> 52:54:00:26:9e:f1</code>) immediately follows the <code class="computeroutput">link/ether</code> keyword:
+ </div><pre class="screen">~]# <code class="command">ip addr</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
+ link/ether <span class="emphasis"><em>52:54:00:26:9e:f1</em></span> brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.251/24 brd 192.168.122.255 scope global eth0
+ inet6 fe80::5054:ff:fe26:9ef1/64 scope link
+ valid_lft forever preferred_lft forever</pre><div class="para">
+ A single system can have one or more NICs installed on it. The <span class="guilabel"><strong>MAC address</strong></span> field therefore allows you to associate a specific NIC with a specific connection (or connections). As mentioned, you can determine the MAC address using the <code class="command">ip addr</code> command, and then copy and paste that value into the <span class="guilabel"><strong>MAC address</strong></span> text-entry field.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>MTU</strong></span> </span></dt><dd><div class="para">
+ The MTU (Maximum Transmission Unit) value represents the size in bytes of the largest packet that the connection will use to transmit. This value defaults to <code class="constant">1500</code> when using IPv4, or a variable number <code class="constant">1280</code> or higher for IPv6, and does not generally need to be specified or changed.
+ </div></dd></dl></div><h4>Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your new wired connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="#sec-Connecting_to_a_Network" title="5.2.1. Connecting to a Network">Section 5.2.1, “Connecting to a Network”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ At this point, you have created a new wired connection. You can further configure your connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port-based Network Access Control (PNAC), click the <span class="guilabel"><strong>802.1x Security</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_802.1x_Security" title="5.4.1. Configuring 802.1x Security">Section 5.4.1, “Configuring 802.1x Security”</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings" title="5.4.4. Configuring IPv4 Settings">Section 5.4.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings" title="5.4.5. Configuring IPv6 Settings">Section 5.4.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></div><div class="section" title="5.3.2. Establishing a Wireless Connection" id="sec-Establishing_a_Wireless_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_a_Wireless_Connection">5.3.2. Establishing a Wireless Connection</h3></div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> makes configuring a wireless (also known as wi-fi or 802.1<em class="replaceable"><code>a/b/g/n</code></em>) connection quick and simple. To establish a wireless connection, you need:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ a computer capable of wi-fi connectivity (such as a laptop with an integrated 802.1<em class="replaceable"><code>x</code></em> card or chip);
+ </div></li><li class="listitem"><div class="para">
+ a wireless access point to connect to (such as a wireless router); and,
+ </div></li><li class="listitem"><div class="para">
+ if the access point is secured, an authentication secret such as a key, passphrase, or digital certificate.
+ </div></li></ul></div><div class="para">
+ To configure a mobile broadband (such as 3G) connection instead of a wireless one, refer to <a class="xref" href="#sec-Establishing_a_Mobile_Broadband_Connection" title="5.3.3. Establishing a Mobile Broadband Connection">Section 5.3.3, “Establishing a Mobile Broadband Connection”</a>.
+ </div><h4>Quickly Connecting to an Available Access Point</h4><div class="para">
+ The easiest way to connect to an available access point is to left-click on the <span class="application"><strong>NetworkManager</strong></span> applet, locate the SSID of the access point in the list of <span class="guilabel"><strong>Available</strong></span> networks, and click on it. If the access point is secured, a dialog prompts you for authentication.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Wireless_authentication_required.png" align="middle" /><div class="caption"><div class="para">
+ Authenticating with a wireless access point
+ </div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> tries to auto-detect the type of security used by the access point. If there are multiple possibilities, <span class="application"><strong>NetworkManager</strong></span> guesses the security type and presents it in the <span class="guilabel"><strong>Wireless security</strong></span> dropdown. To see if there are multiple choices, click the <span class="guilabel"><strong>Wireless security</strong></span> dropdown menu and select the type of security the access point is using. If you are unsure, try connecting to each type in turn. Finally, enter the key or passphrase in the <span class="guilabel"><strong>Password</strong></span> field. Certain password types, such as a 40-bit WEP or 128-bit WPA key, are invalid unless they are of a requisite length. The <span class="guilabel"><strong>Connect</strong></span> button will remain inactive until you enter a key of the length required for the selected security typ
e. To learn more about wireless security, refer to <a class="xref" href="#sec-Configuring_Wireless_Security" title="5.4.2. Configuring Wireless Security">Section 5.4.2, “Configuring Wireless Security”</a>.
+ </div><div class="para">
+ If <span class="application"><strong>NetworkManager</strong></span> connects to the access point succesfully, its applet icon will change into a graphical indicator of the wireless connection's signal strength.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM_applet-signal_strength_75.png" align="middle" /><div class="caption"><div class="para">
+ Applet icon indicating a wireless connection signal strength of 75%
+ </div></div></div><div class="para">
+ You can also edit the settings for one of these auto-created access point connections just as if you had <span class="guilabel"><strong>Add</strong></span>ded it yourself. The <span class="guilabel"><strong>Wireless</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window lists all of the connections you have ever tried to connect to: <span class="application"><strong>NetworkManager</strong></span> names each of them <code class="computeroutput">Auto <em class="replaceable"><code><SSID></code></em> </code>, where SSID is the <em class="firstterm">Service Set identifier</em> of the access point.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Wireless_Auto_Connections_List.png" align="middle" /><div class="caption"><div class="para">
+ Previous access points that have been connected to
+ </div></div></div><h4>Connecting to a Hidden Wireless Network</h4><div class="para">
+ All access points have a <em class="firstterm">Service Set identifier</em> (SSID) to identify them. However, an access point may be configured not to broadcast its SSID, in which case it is <span class="emphasis"><em>hidden</em></span>, and will not show up in <span class="application"><strong>NetworkManager</strong></span>'s list of <span class="guilabel"><strong>Available</strong></span> networks. You can still connect to a wireless access point that is hiding its SSID as long as you know its SSID, authentication method, and secrets.
+ </div><div class="para">
+ To connect to a hidden wireless network, left-click <span class="application"><strong>NetworkManager</strong></span>'s applet icon and select <span class="guilabel"><strong>Connect to Hidden Wireless Network...</strong></span> to cause a dialog to appear. If you have connected to the hidden network before, use the <span class="guilabel"><strong>Connection</strong></span> dropdown to select it, and click <span class="guibutton"><strong>Connect</strong></span>. If you have not, leave the <span class="guilabel"><strong>Connection</strong></span> dropdown as <span class="guimenuitem"><strong>New...</strong></span>, enter the SSID of the hidden network, select its <span class="guilabel"><strong>Wireless security</strong></span> method, enter the correct authentication secrets, and click <span class="guibutton"><strong>Connect</strong></span>.
+ </div><div class="para">
+ For more information on wireless security settings, refer to <a class="xref" href="#sec-Configuring_Wireless_Security" title="5.4.2. Configuring Wireless Security">Section 5.4.2, “Configuring Wireless Security”</a>.
+ </div><h4>Editing a Connection, or Creating a Completely New One</h4><div class="para">
+ You can edit an existing connection that you have tried or succeeded in connecting to in the past by opening the <span class="guilabel"><strong>Wireless</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span>, selecting the connection by name (words which follow <code class="computeroutput">Auto</code> refer to the SSID of an access point), and clicking <span class="guilabel"><strong>Edit</strong></span>.
+ </div><div class="para">
+ You can create a new connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window, selecting the <span class="guilabel"><strong>Wireless</strong></span> tab, and clicking the <span class="guilabel"><strong>Add</strong></span> button.
+ </div><div class="para">
+ For more information on opening the <span class="guilabel"><strong>Network Connections</strong></span> window via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet, or by running a shell command, refer to <a class="xref" href="#sec-Configuring_New_and_Editing_Existing_Connections" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Editing_Wireless_Connection_1.png" align="middle" /><div class="caption"><div class="para">
+ Editing the newly-created Wireless connection 1
+ </div></div></div><h4>Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — You can customize the name under which this connection is listed in the <span class="guilabel"><strong>Wireless</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window by entering a descriptive name in the text-entry box. By default, wireless connections are named the same as the <em class="firstterm">SSID</em> of the wireless access point. You can rename the wireless connection without affecting its ability to connect, but it is recommended to retain the SSID name.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the this connection when it is—or becomes—available. Refer to <a class="xref" href="#sec-Connecting_to_a_Network_Automatically" title="5.2.3. Connecting to a Network Automatically">Section 5.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="#sec-User_and_System_Connections" title="5.2.4. User and System Connections">Section 5.2.4, “User and System Connections”</a> for details.
+ </div></li></ul></div><h4>Configuring the Wireless Tab</h4><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>SSID</strong></span> </span></dt><dd><div class="para">
+ All access points have a <em class="firstterm">Service Set identifier</em> to identify them. However, an access point may be configured not to broadcast its SSID, in which case it is <span class="emphasis"><em>hidden</em></span>, and will not show up in <span class="application"><strong>NetworkManager</strong></span>'s list of <span class="guilabel"><strong>Available</strong></span> networks. You can still connect to a wireless access point that is hiding its SSID as long as you know its SSID (and authentication secrets).
+ </div><div class="para">
+ For information on connecting to a hidden wireless network, refer to <a class="xref" href="#bh-Connecting_to_a_Hidden_Wireless_Network" title="5.3.2. Connecting to a Hidden Wireless Network">Section 5.3.2, “Connecting to a Hidden Wireless Network”</a>.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Mode</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Infrastructure</strong></span> — Set <span class="guilabel"><strong>Mode</strong></span> to <span class="guimenuitem"><strong>Infrastructure</strong></span> if you are connecting to a wireless access point such as a router or a switch.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Ad-hoc</strong></span> — Set <span class="guilabel"><strong>Mode</strong></span> to <span class="guimenuitem"><strong>Ad-hoc</strong></span> if you are creating a peer-to-peer network for two or more mobile devices to communicate directly with each other. If you use <span class="guimenuitem"><strong>Ad-hoc</strong></span> mode, you must ensure that the same <span class="guilabel"><strong>SSID</strong></span> is set for all participating wireless devices, and that they are all communicating over the same channel.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>BSSID</strong></span> </span></dt><dd><div class="para">
+ The Basic Service Set Identifier (BSSID) is the MAC address of the wireless access point you are connecting to when in <span class="guilabel"><strong>Infrastructure</strong></span> mode. This field is blank by default, and you are able to connect to a wireless access point by <span class="guilabel"><strong>SSID</strong></span> without having to specify its <span class="guilabel"><strong>BSSID</strong></span>.
+ </div><div class="para">
+ For ad-hoc networks, the BSSID is generated randomly. However, <span class="application"><strong>NetworkManager</strong></span> does not have the capability to generate the BSSID for an ad-hoc network.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>MAC address</strong></span> </span></dt><dd><div class="para">
+ Like an ethernet Network Interface Card (NIC), a wireless adapter has a unique MAC address (Media Access Control; also known as a <em class="firstterm">hardware address</em>) that identifies it to the system. Running the <code class="command">ip addr</code> command will show the MAC address associated with each interface. For example, in the following <code class="command">ip addr</code> output, the MAC address for the <code class="computeroutput">wlan0</code> interface (which is <code class="computeroutput">00:1c:bf:02:f8:70</code>) immediately follows the <code class="computeroutput">link/ether</code> keyword:
+ </div><pre class="screen">~]# <code class="command">ip addr</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
+ link/ether 52:54:00:26:9e:f1 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.251/24 brd 192.168.122.255 scope global eth0
+ inet6 fe80::5054:ff:fe26:9ef1/64 scope link
+ valid_lft forever preferred_lft forever
+3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
+ link/ether <span class="emphasis"><em>00:1c:bf:02:f8:70</em></span> brd ff:ff:ff:ff:ff:ff
+ inet 10.200.130.67/24 brd 10.200.130.255 scope global wlan0
+ inet6 fe80::21c:bfff:fe02:f870/64 scope link
+ valid_lft forever preferred_lft forever</pre><div class="para">
+ A single system could have one or more wireless network adapters connected to it. The <span class="guilabel"><strong>MAC address</strong></span> field therefore allows you to associate a specific wireless adapter with a specific connection (or connections). As mentioned, you can determine the MAC address using the <code class="command">ip addr</code> command, and then copy and paste that value into the <span class="guilabel"><strong>MAC address</strong></span> text-entry field.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>MTU</strong></span> </span></dt><dd><div class="para">
+ The MTU (Maximum Transmission Unit) value represents the size in bytes of the largest packet that the connection will use to transmit. If set to a non-zero number, only packets of the specified size or smaller will be transmitted. Larger packets are broken up into multiple Ethernet frames. It is recommended to leave this setting on <span class="guimenuitem"><strong>automatic</strong></span>.
+ </div></dd></dl></div><h4>Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing the wireless connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can successfully connect to your the modified connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="#sec-Connecting_to_a_Network" title="5.2.1. Connecting to a Network">Section 5.2.1, “Connecting to a Network”</a> for details on selecting and connecting to a network.
+ </div><div class="para">
+ You can further configure your connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ security authentication for the wireless connection, click the <span class="guilabel"><strong>Wireless Security</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_Wireless_Security" title="5.4.2. Configuring Wireless Security">Section 5.4.2, “Configuring Wireless Security”</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings" title="5.4.4. Configuring IPv4 Settings">Section 5.4.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings" title="5.4.5. Configuring IPv6 Settings">Section 5.4.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></div><div class="section" title="5.3.3. Establishing a Mobile Broadband Connection" id="sec-Establishing_a_Mobile_Broadband_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_a_Mobile_Broadband_Connection">5.3.3. Establishing a Mobile Broadband Connection</h3></div></div></div><div class="para">
+ You can use <span class="application"><strong>NetworkManager</strong></span>'s mobile broadband connection abilities to connect to the following <em class="firstterm">2G</em> and <em class="firstterm">3G</em> services:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 2G — <em class="firstterm">GPRS</em> (<em class="firstterm">General Packet Radio Service</em>) or <em class="firstterm">EDGE</em> (<em class="firstterm">Enhanced Data Rates for GSM Evolution</em>)
+ </div></li><li class="listitem"><div class="para">
+ 3G — <em class="firstterm">UMTS</em> (<em class="firstterm">Universal Mobile Telecommunications System</em>) or <em class="firstterm">HSPA</em> (<em class="firstterm">High Speed Packet Access</em>)
+ </div></li></ul></div><div class="para">
+ Your computer must have a device capable of mobile broadband capability which the system has recognized in order to create the connection. Such a device may be built into your computer (as is the case on many notebooks and netbooks), or may be provided as external hardware (such as a PC card, USB or phone modem).
+ </div><div class="procedure"><h6>Procedure 5.3. Adding a New Mobile Broadband Connection</h6><div class="para">
+ You can configure a mobile broadband connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window and selecting the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab. For more information on opening the <span class="guilabel"><strong>Network Connections</strong></span> window via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet, or by running a shell command, refer to <a class="xref" href="#sec-Configuring_New_and_Editing_Existing_Connections" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>.
+ </div><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button to open the <span class="guilabel"><strong>Set up a Mobile Broadband Connection</strong></span> assistant.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Under <span class="guilabel"><strong>Create a connection for this mobile broadband device</strong></span>, choose the 2G- or 3G-capable device you want to use with the connection. If the dropdown menu is inactive, this indicates that the system was unable to detect a device capable of mobile broadband. In this case, click <span class="guilabel"><strong>Cancel</strong></span>, ensure that you do have a mobile broadband-capable device attached to, and recognized by, the computer, and then retry this procedure.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ TBD
+ </div></li></ol></div><div class="procedure"><h6>Procedure 5.4. Editing an Existing Mobile Broadband Connection</h6><div class="para">
+ Follow these steps to edit an existing mobile broadband connection.
+ </div><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Open the <span class="guilabel"><strong>Network Connections</strong></span> window and select the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab. For more information on opening the <span class="guilabel"><strong>Network Connections</strong></span> window via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet, or by running a shell command, refer to <a class="xref" href="#sec-Configuring_New_and_Editing_Existing_Connections" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Select the connection you wish to edit and click the <span class="guilabel"><strong>Edit</strong></span> button.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — You can customize the name under which this connection is listed in the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window by entering a descriptive name in the text-entry box.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the this connection when it is—or becomes—available. Refer to <a class="xref" href="#sec-Connecting_to_a_Network_Automatically" title="5.2.3. Connecting to a Network Automatically">Section 5.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="#sec-User_and_System_Connections" title="5.2.4. User and System Connections">Section 5.2.4, “User and System Connections”</a> for details.
+ </div></li></ul></div></li><li class="step" title="Step 4"><div class="para">
+ Edit the mobile broadband-specific settings by referring to <a class="xref" href="#bh-Configuring_the_Mobile_Broadband_Tab" title="5.3.3. Configuring the Mobile Broadband Tab">Section 5.3.3, “Configuring the Mobile Broadband Tab”</a>.
+ </div></li><li class="step" title="Step 5"><div class="para">
+ Once you have finished editing your new mobile broadband connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="#sec-Connecting_to_a_Network" title="5.2.1. Connecting to a Network">Section 5.2.1, “Connecting to a Network”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ At this point, you have created a new mobile broadband connection. You can further configure your connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Point-to-point settings for the connection, click the <span class="guilabel"><strong>PPP Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_PPP_Point-to-Point_Settings" title="5.4.3. Configuring PPP (Point-to-Point) Settings">Section 5.4.3, “Configuring PPP (Point-to-Point) Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings" title="5.4.4. Configuring IPv4 Settings">Section 5.4.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv6_Settings" title="5.4.5. Configuring IPv6 Settings">Section 5.4.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></li></ol></div><h4>Configuring the Mobile Broadband Tab</h4><div class="para">
+ If you have already added a new mobile broadband connection using the assistant (refer to <a class="xref" href="#procedure-Adding_a_New_Mobile_Broadband_Connection" title="Procedure 5.3. Adding a New Mobile Broadband Connection">Procedure 5.3, “Adding a New Mobile Broadband Connection”</a> for instructions), you can edit the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab to disable roaming if home network is not available, assign a network ID, or instruct <span class="application"><strong>NetworkManager</strong></span> to prefer a certain technology (such as 3G or 2G) when using the connection.
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Number</strong></span> </span></dt><dd><div class="para">
+ The number that is dialed to establish a PPP connection with the GSM-based mobile broadband network. You can usually leave this field blank and simply enter the <span class="guilabel"><strong>APN</strong></span> instead.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the username used to authenticate with the network. Some providers do not provide a username, or accept any username when connecting to the network.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password used to authenticate with the network. Some providers do not provide a password, or accept any password.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>APN</strong></span> </span></dt><dd><div class="para">
+ Enter the <em class="firstterm">APN</em> (<em class="firstterm">Access Point Name</em>) used to establish a connection with the GSM-based network. Entering the correct APN for a connection is important because it often determines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ how the user is billed for their network usage; and/or
+ </div></li><li class="listitem"><div class="para">
+ whether the user has access to the Internet or to an intranet or subnetwork.
+ </div></li></ul></div></dd><dt><span class="term"> <span class="guilabel"><strong>Network ID</strong></span> </span></dt><dd><div class="para">
+ Entering a <span class="guilabel"><strong>Network ID</strong></span> causes <span class="application"><strong>NetworkManager</strong></span> to force the device to register only on a specific network. This can be used to ensure the connection does not roam when it is not possible to control roaming directly.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Type</strong></span> </span></dt><dd><div class="para">
+ <span class="guilabel"><strong>Any</strong></span> — The default value of <span class="guilabel"><strong>Any</strong></span> allows <span class="application"><strong>NetworkManager</strong></span>
+ .
+ </div><div class="para">
+ <span class="guilabel"><strong>3G (UMTS/HSPA)</strong></span> — Force the connection to use only 3G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>2G (GPRS/EDGE)</strong></span> — Force the connection to use only 2G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 3G (UMTS/HSPA)</strong></span> — First attempt to connect using a 3G technology such as HSPA or UMTS, and fall back to GPRS or EDGE only upon failure.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 2G (GPRS/EDGE)</strong></span> — First attempt to connect using a 2G technology such as GPRS or EDGE, and fall back to HSPA or UMTS only upon failure.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Allow roaming if home network is not available</strong></span> </span></dt><dd><div class="para">
+ Uncheck this box if you want <span class="application"><strong>NetworkManager</strong></span> to terminate the connection if you transition from the home network to a roaming one, thereby avoiding possible roaming charges. If the box is checked, <span class="application"><strong>NetworkManager</strong></span> will maintain the connection when it transitions from the home network to a roaming one, and vice versa.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>PIN</strong></span> </span></dt><dd><div class="para">
+ If your device's <em class="firstterm">SIM</em> (<em class="firstterm">Subscriber Identity Module</em>) is locked with a <em class="firstterm">PIN</em> (<em class="firstterm">Personal Identification Number</em>), enter the PIN so that <span class="application"><strong>NetworkManager</strong></span> can unlock the device. <span class="application"><strong>NetworkManager</strong></span> must unlock the SIM if it requires a PIN in order to use the device for any purpose.
+ </div></dd></dl></div></div><div class="section" title="5.3.4. Establishing a VPN Connection" id="sec-Establishing_a_VPN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_a_VPN_Connection">5.3.4. Establishing a VPN Connection</h3></div></div></div><div class="para">
+ Connecting to a Virtual Private Network (VPN) enables you to communicate securely between your Local Area Network (LAN), and another, remote LAN. After successfully establishing a VPN connection, a VPN router or gateway performs the following actions upon the packets that you transmit:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ it adds an <em class="firstterm">Authentication Header</em> for routing and authentication purposes;
+ </div></li><li class="listitem"><div class="para">
+ it encrypts the packet data; and
+ </div></li><li class="listitem"><div class="para">
+ it encloses the data with an Encapsulating Security Payload (ESP), which constitutes the decryption and handling instructions.
+ </div></li></ol></div><div class="para">
+ The receiving VPN router strips the header information, decrypts the data, and routes it to its intended destination (either a workstation or other node on a network). Using a network-to-network connection, the receiving node on the local network receives the packets already decrypted and ready for processing. The encryption/decryption process in a network-to-network VPN connection is therefore transparent to clients.
+ </div><div class="para">
+ Because they employ several layers of authentication and encryption, VPNs are a secure and effective means of connecting multiple remote nodes to act as a unified intranet.
+ </div><div class="para">
+ You can configure a VPN connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window and selecting the <span class="guilabel"><strong>tab</strong></span> tab. For more information on opening the <span class="guilabel"><strong>Network Connections</strong></span> window via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet, or by running a shell command, refer to <a class="xref" href="#sec-Configuring_New_and_Editing_Existing_Connections" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>.
+ </div><h4>Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — You can customize the name under which this connection is listed in the <span class="guilabel"><strong>tab</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window by entering a descriptive name in the text-entry box.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the this connection when it is—or becomes—available. Refer to <a class="xref" href="#sec-Connecting_to_a_Network_Automatically" title="5.2.3. Connecting to a Network Automatically">Section 5.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="#sec-User_and_System_Connections" title="5.2.4. User and System Connections">Section 5.2.4, “User and System Connections”</a> for details.
+ </div></li></ul></div><h4>Configuring the <em class="replaceable"><code><tab></code></em> Tab</h4><h4>Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your new VPN connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="#sec-Connecting_to_a_Network" title="5.2.1. Connecting to a Network">Section 5.2.1, “Connecting to a Network”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ At this point, you have created a new VPN connection. You can further configure your connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="#sec-Configuring_IPv4_Settings" title="5.4.4. Configuring IPv4 Settings">Section 5.4.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li></ul></div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Gateway</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Group name</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>User password</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Group password</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>User name</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Domain</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Encryption Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Secure (default)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Weak (use with caution)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>None (completely insecure)</strong></span> —
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>NAT traversal</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Cisco UDP (default)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>NAT-T</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Disabled</strong></span> —
+ </div><div class="para">
+ <span class="guilabel"><strong>Disable Dead Peer Detection</strong></span> —
+ </div></dd></dl></div></div><div class="section" title="5.3.5. Establishing a DSL Connection" id="sec-Establishing_a_DSL_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_a_DSL_Connection">5.3.5. Establishing a DSL Connection</h3></div></div></div><div class="para">
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Service</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div><div class="section" title="5.3.6. Establishing Routes" id="sec-Establishing_Routes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_Routes">5.3.6. Establishing Routes</h3></div></div></div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-System_eth0-Routes.png" align="middle" width="444" /><div class="caption"><div class="para">
+ Configuring static network routes
+ </div></div></div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Addresses</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Address</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Prefix</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Gateway</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Metric</strong></span> —
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Ignore automatically obtained routes</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Use this connection only for resources on its network</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div></div><div class="section" title="5.4. 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.4. Configuring Connection Settings</h2></div></div></div><div class="section" title="5.4.1. Configuring 802.1x Security" id="sec-Configuring_802.1x_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_802.1x_Security">5.4.1. Configuring 802.1x Security</h3></div></div></div><div class="para">
+ 802.1x security is the name of the IEEE standard for port-based Network Access Control (PNAC). Simply put, 802.1x security is a way of defining a <em class="firstterm">logical network</em> out of a physical one. All clients who want to join the logical network must authenticate with the server (a router, for example) using the correct 802.1x authentication method.
+ </div><div class="para">
+ 802.1x security is most often associated with securing wireless networks (WLANs), but can also be used to prevent intruders with physical access to the network (LAN) from gaining entry. In the past, DHCP servers were configured not to lease IP addresses to unauthorized users, but but for various reasons this practice is both impractical and insecure, and thus is no longer recommended. Instead, 802.1x security is used to ensure a logically-secure network through port-based authentication.
+ </div><div class="para">
+ 802.1x provides a framework for WLAN and LAN access control and serves as an envelope for carrying one of the Extensible Authentication Protocol (EAP) types. An EAP type is a protocol that defines how WLAN security is achieved on the network.
+ </div><div class="para">
+ You can configure 802.1x security for a wired or wireless connection type by opening the <span class="guilabel"><strong>Network Connections</strong></span> window (refer to <a class="xref" href="#sec-Configuring_New_and_Editing_Existing_Connections" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>) and following the applicable procedure:
+ </div><div class="procedure"><h6>Procedure 5.5. For a wired connection...</h6><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Select the <span class="guilabel"><strong>Wired</strong></span> tab.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Either click on <span class="guibutton"><strong>Add</strong></span> to add a new network connection for which you want to configure 802.1x security, or select an existing connection and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Then select the <span class="guilabel"><strong>802.1x Security</strong></span> tab and check the <span class="guilabel"><strong>Use 802.1x security for this connection</strong></span> checkbox to enable settings configuration.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ Proceed to
+ </div></li></ol></div><div class="procedure"><h6>Procedure 5.6. For a wireless connection...</h6><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Select the <span class="guilabel"><strong>Wireless</strong></span> tab.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Either click on <span class="guibutton"><strong>Add</strong></span> to add a new network connection for which you want to configure 802.1x security, or select an existing connection and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Then click the <span class="guilabel"><strong>Security</strong></span> dropdown and choose one of the following security methods: <span class="guimenuitem"><strong>LEAP</strong></span>, <span class="guimenuitem"><strong>Dynamic WEP (802.1x)</strong></span>, or <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span>.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ Refer to for descriptions of which EAP types correspond to your selection in the <span class="guilabel"><strong>Security</strong></span> dropdown.
+ </div></li></ol></div><div class="section" title="5.4.1.1. Configuring TLS (Transport Level Security) Settings" id="sec-Configuring_TLS_Transport_Level_Security_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sec-Configuring_TLS_Transport_Level_Security_Settings">5.4.1.1. Configuring TLS (Transport Level Security) Settings</h4></div></div></div><div class="para">
+ With Transport Level Security, the client and server mutually authenticate using the TLS protocol. The server demonstrates that it holds a digital certificate, the client proves its own identity using its client-side certificate, and key information is exchanged. Once authentication is complete, the TLS tunnel is no longer used. Instead, the client and server use the exchanged keys to encrypt data using AES, TKIP or WEP.
+ </div><div class="para">
+ The fact that certificates must be distributed to all clients who want to authenticate means that the the EAP-TLS authentication method is very strong, but also more complicated to set up. Using TLS security requires the overhead of a public key infrastructure (PKI) to manage certificates. The benefit to TLS security is that a compromised password does not allow access to the (W)LAN: an intruder must also have access to the authenticating client's private key.
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Identity</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>User certificate</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Private key</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Private key password</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div><div class="section" title="5.4.1.2. Configuring Tunneled TLS Settings" id="sec-Configuring_Tunneled_TLS_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sec-Configuring_Tunneled_TLS_Settings">5.4.1.2. Configuring Tunneled TLS Settings</h4></div></div></div><div class="para">
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Anonymous identity</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>PAP</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAP</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>CHAP</strong></span> —
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div><div class="section" title="5.4.1.3. Configuring Protected EAP (PEAP) Settings" id="sec-Configuring_Protected_EAP_PEAP_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sec-Configuring_Protected_EAP_PEAP_Settings">5.4.1.3. Configuring Protected EAP (PEAP) Settings</h4></div></div></div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Anonymous Identity</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>PEAP version</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MD5</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>GTC</strong></span> —
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div></div><div class="section" title="5.4.2. Configuring Wireless Security" id="sec-Configuring_Wireless_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_Wireless_Security">5.4.2. Configuring Wireless Security</h3></div></div></div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Security</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>None</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 40/128-bit Key</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 128-bit Passphrase</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>LEAP</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Dynamic WEP (802.1x)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Personal</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span> —
+ </div></dd><dt><span class="term">Password</span></dt><dd><div class="para">
+ </div></dd></dl></div></div><div class="section" title="5.4.3. Configuring PPP (Point-to-Point) Settings" id="sec-Configuring_PPP_Point-to-Point_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_PPP_Point-to-Point_Settings">5.4.3. Configuring PPP (Point-to-Point) Settings</h3></div></div></div><div class="para">
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Configure Methods</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Use point-to-point encryption (MPPE)</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Allow BSD data compression</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Allow Deflate data compression</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Use TCP header compression</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Send PPP echo packets</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div><div class="section" title="5.4.4. 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.4.4. 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. If you need to configure IPv6 addresses, refer to ???. If you need to configure static routes, which can be done by clicking on the <span class="guibutton"><strong>Routes</strong></span> button, refer to ???.
+ </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><h4>Setting the Method</h4><div class="variablelist" title="Available IPv4 Methods by Connection Type" id="varlist-Available_IPv4_Methods_by_Connection_Type"><h6>Available IPv4 Methods by Connection Type</h6><div class="para">
+ When you click the <span class="guilabel"><strong>Method</strong></span> dropdown menu, depending on the type of connection you are configuring, you are able to select one of the following IPv4 connection methods. All of the methods are listed here according to which connection type or types they are associated with.
+ </div><dl><dt><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses. You do not need to fill in the <span class="guilabel"><strong>DHCP client ID</strong></span> field.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP) addresses only</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Shared to other computers</strong></span> —
+ </div></dd><dt><span class="term">Wired, Wireless and DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> —
+ </div></dd><dt><span class="term">Mobile Broadband Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP) addresses only</strong></span> —
+ </div></dd><dt><span class="term">VPN Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN) addresses only</strong></span> —
+ </div></dd><dt><span class="term">DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE) addresses only</strong></span> —
+ </div></dd></dl></div></div><div class="section" title="5.4.5. Configuring IPv6 Settings" id="sec-Configuring_IPv6_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_IPv6_Settings">5.4.5. Configuring IPv6 Settings</h3></div></div></div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Ignore</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic, addresses only</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Shared to other computers</strong></span> —
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Addresses</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>DNS servers</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Search domains</strong></span> —
+ </div></dd></dl></div></div></div><div class="section" title="5.5. NetworkManager Architecture" id="sec-NetworkManager_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-NetworkManager_Architecture">5.5. NetworkManager Architecture</h2></div></div></div><div class="para">
+ See <a href="http://live.gnome.org/NetworkManagerConfiguration">http://live.gnome.org/NetworkManagerConfiguration</a>
+ </div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 6. Controlling Access to Services" id="ch-Controlling_Access_to_Services" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Controlling Access to Services</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-services-runlevels">6.1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="#s1-services-configuring">6.2. Configuring the Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-serviceconf">6.2.1. Using the <span class="application"><strong>Service Configuration</strong></span> Utility</a></span></dt><dt><span class="section"><a href="#s2-services-ntsysv">6.2.2. Using the <span class="application"><strong>ntsysv</strong></span> Utility</a></span></dt><dt><span class="section"><a href="#s2-services-chkconfig">6.2.3. Using the <code class="command">chkconfig</code> Utility</a></span></dt
></dl></dd><dt><span class="section"><a href="#s1-services-running">6.3. Running the Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-service">6.3.1. Using the <span class="application"><strong>service</strong></span> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-additional-resources-installed">6.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">6.4.2. Related Books</a></span></dt></dl></dd></dl></div><a id="id1125782" 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"><h2>Important</h2><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="6.4. Additional Resources">Section 6.4, “Additional Resources”</a>) for more information.
+ </div></div><div class="section" title="6.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">6.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 6.1. Runlevels in Fedora" id="table-services-runlevels"><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><h6>Table 6.1. Runlevels in Fedora</h6></div><br class="table-break" /><div class="para">
+ To check in which runlevel you are operating, type the following:
+ </div><a id="id1006198" class="indexterm"></a><a id="id1006215" 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="6.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">6.2. Configuring the Services</h2></div></div></div><div class="section" title="6.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">6.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="id980914" class="indexterm"></a><a id="id929996" 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 6.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 6.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 6.2. Possible Service States">Table 6.2, “Possible Service States”</a> for a complete list of used icons and an explanation of their meaning.
+ </div><div class="table" title="Table 6.2. Possible Service States" id="tab-services-serviceconf-states"><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><h6>Table 6.2. Possible Service States</h6></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 6.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 6.2. Authentication Query</h6></div><br class="figure-break" /><div class="section" title="6.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">6.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="6.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">6.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="6.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">6.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="6.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">6.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="6.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">6.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="6.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">6.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="6.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">6.2.2. Using the <span class="application"><strong>ntsysv</strong></span> Utility</h3></div></div></div><a id="id1011250" class="indexterm"></a><a id="id1011267" 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 6.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 6.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 6.3. Possible Service States">Table 6.3, “Possible Service States”</a> for a list of used symbols and an explanation of their meaning.
+ </div><div class="table" title="Table 6.3. Possible Service States" id="tab-services-ntsysv-states"><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><h6>Table 6.3. Possible Service States</h6></div><br class="table-break" /><div class="section" title="6.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">6.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="6.3.1.1. Running the Service">Section 6.3.1.1, “Running the Service”</a>.
+ </div></div><div class="section" title="6.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">6.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="6.3.1.2. Stopping the Service">Section 6.3.1.2, “Stopping the Service”</a>.
+ </div></div><div class="section" title="6.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">6.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="6.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">6.2.3. Using the <code class="command">chkconfig</code> Utility</h3></div></div></div><a id="id611514" class="indexterm"></a><a id="id611532" 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="6.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">6.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 6.1. Listing the services" id="ex-services-chkconfig-listing-all"><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><h6>Example 6.1. Listing the services</h6></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 6.2. Listing a single service" id="ex-services-chkconfig-listing-single"><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><h6>Example 6.2. Listing a single service</h6></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 6.3. Listing a service that is managed by xinetd" id="ex-services-chkconfig-listing-xinetd"><div class="example-contents"><pre class="screen">~]# <code class="command">chkconfig --list rsync</code>
+rsync off</pre></div><h6>Example 6.3. Listing a service that is managed by <span class="application">xinetd</span></h6></div><br class="example-break" /></div><div class="section" title="6.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">6.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="6.3.1.1. Running the Service">Section 6.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="6.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">6.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 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="6.3.1.2. Stopping the Service">Section 6.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="6.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">6.3. Running the Services</h2></div></div></div><div class="section" title="6.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">6.3.1. Using the <span class="application"><strong>service</strong></span> Utility</h3></div></div></div><a id="id1779259" class="indexterm"></a><a id="id698217" 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"><h2>Tip</h2><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="6.2.1. Using the Service Configuration Utility">Section 6.2.1, “Using the <span class="application"><strong>Service Configuration</strong></span> Utility”</a> for more information.
+ </div></div><div class="section" title="6.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">6.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="6.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">6.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="6.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">6.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="6.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">6.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 6.4. Checking the status of httpd" id="ex-services-running-checking-single"><div class="example-contents"><pre class="screen">~]# <code class="command">service httpd status</code>
+httpd (pid 7474) is running...</pre></div><h6>Example 6.4. Checking the status of <span class="application">httpd</span></h6></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 6.5. Checking the status of all services" id="ex-services-running-checking-all"><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><h6>Example 6.5. Checking the status of all services</h6></div><br class="example-break" /></div></div></div><div class="section" title="6.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">6.4. Additional Resources</h2></div></div></div><div class="section" title="6.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">6.4.1. Installed Documentation</h3></div></div></div><div class="variablelist"><dl><dt><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><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><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><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="6.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">6.4.2. Related Books</h3></div></div></div><div class="variablelist"><dl><dt><span class="term"> <em class="citetitle">Security Guide</em> </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 7. The BIND DNS Server" id="ch-The_BIND_DNS_Server" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. The BIND DNS Server</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-bind-introduction">7.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-introduction-zones">7.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="#s2-bind-introduction-nameservers">7.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="#s2-bind-introduction-bind">7.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-namedconf">7.2. <code class="filename">/etc/named.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-namedconf-state">7.2.1. Common Statement Types</a></span></dt><dt><span class="section"
><a href="#s2-bind-namedconf-state-other">7.2.2. Other Statement Types</a></span></dt><dt><span class="section"><a href="#s2-bind-namedconf-comm">7.2.3. Comment Tags</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-zone">7.3. Zone Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-zone-directives">7.3.1. Zone File Directives</a></span></dt><dt><span class="section"><a href="#s3-bind-zone-rr">7.3.2. Zone File Resource Records</a></span></dt><dt><span class="section"><a href="#s2-bind-zone-examples">7.3.3. Example Zone File</a></span></dt><dt><span class="section"><a href="#s2-bind-configuration-zone-reverse">7.3.4. Reverse Name Resolution Zone Files</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-rndc">7.4. Using <code class="command">rndc</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-rndc-configuration-namedconf">7.4.1. Configuring <code class="filename">/etc/named.conf</code> </a></s
pan></dt><dt><span class="section"><a href="#s2-bind-rndc-configuration-rndcconf">7.4.2. Configuring <code class="filename">/etc/rndc.conf</code> </a></span></dt><dt><span class="section"><a href="#s2-bind-rndc-options">7.4.3. Command Line Options</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-features">7.5. Advanced Features of BIND</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-bind-features-protocol">7.5.1. DNS Protocol Enhancements</a></span></dt><dt><span class="section"><a href="#s2-bind-features-views">7.5.2. Multiple Views</a></span></dt><dt><span class="section"><a href="#s2-bind-features-security">7.5.3. Security</a></span></dt><dt><span class="section"><a href="#s2-bind-features-ipv6">7.5.4. IP version 6</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-bind-mistakes">7.6. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="#s1-bind-additional-resources">7.7. Additional Resources</a></span><
/dt><dd><dl><dt><span class="section"><a href="#s2-bind-installed-docs">7.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-bind-useful-websites">7.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-bind-related-books">7.7.3. Related Books</a></span></dt></dl></dd></dl></div><a id="id966235" class="indexterm"></a><a id="id1780496" class="indexterm"></a><div class="para">
+ On most modern networks, including the Internet, users locate other computers by name. This frees users from the daunting task of remembering the numerical network address of network resources. The most effective way to configure a network to allow such name-based connections is to set up a <em class="firstterm">Domain Name Service</em> (<em class="firstterm">DNS</em>) or a <em class="firstterm">nameserver</em>, which resolves hostnames on the network to numerical addresses and vice versa.
+ </div><div class="para">
+ This chapter reviews the nameserver included in Fedora and the <em class="firstterm">Berkeley Internet Name Domain</em> (<em class="firstterm">BIND</em>) DNS server, with an emphasis on the structure of its configuration files and how it may be administered both locally and remotely.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ BIND is also known as the service <code class="command">named</code> in Fedora. You can manage it via the Services Configuration Tool (<code class="command">system-config-service</code>).
+ </div></div><div class="section" title="7.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">7.1. Introduction to DNS</h2></div></div></div><a id="id882264" class="indexterm"></a><a id="id880426" class="indexterm"></a><a id="id861982" class="indexterm"></a><a id="id936242" class="indexterm"></a><a id="id821945" class="indexterm"></a><a id="id987903" class="indexterm"></a><a id="id987921" class="indexterm"></a><div class="para">
+ DNS associates hostnames with their respective IP addresses, so that when users want to connect to other machines on the network, they can refer to them by name, without having to remember IP addresses.
+ </div><div class="para">
+ Use of DNS also has advantages for system administrators, allowing the flexibility to change the IP address for a host without affecting name-based queries to the machine. Conversely, administrators can shuffle which machines handle a name-based query.
+ </div><div class="para">
+ DNS is normally implemented using centralized servers that are authoritative for some domains and refer to other DNS servers for other domains.
+ </div><div class="para">
+ 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 the nameserver does not have an authoritative answer about the name the which host requested, 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. Then, with that information, it queries the authoritative nameservers to get the requested name.
+ </div><div class="section" title="7.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">7.1.1. Nameserver Zones</h3></div></div></div><a id="id899436" 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>. A resource record is usually the <em class="firstterm">fully qualified domain name</em> (FQDN) of a host. Resource records are broken down into multiple sections. These sections are organized into a tree-like hierarchy consisting of a main trunk, primary branches, secondary branches, and so forth. Consider the following resource record:
+ </div><pre class="screen">bob.sales.example.com</pre><div class="para">
+ When looking at how a resource record is resolved to find, for example, the IP address that relates to a particular system, read the name from right to left. Each level of the hierarchy is divided by a period (often called a "dot": <span class="quote">“<span class="quote"><code class="computeroutput">.</code> </span>”</span>). In this example, therefore, <code class="computeroutput">com</code> defines the <em class="firstterm">top-level domain</em> for this resource record. The name <code class="computeroutput">example</code> is a sub-domain under <code class="computeroutput">com</code>, while <code class="computeroutput">sales</code> is a sub-domain under <code class="computeroutput">example</code>. The name furthest to the left, <code class="computeroutput">bob</code>, identifies a resource record which is part of the <code class="computeroutput">sales.example.com</code> domain.
+ </div><div class="para">
+ Except for the first (leftmost) part of the resource record (<code class="computeroutput">bob</code>), each section is called a <em class="firstterm">zone</em>. Zone defines a specific <em class="firstterm">namespace</em>. A zone contains definitions of resource records, which usually contain host-to-IP address mappings and IP address-to-host mappings, which are called <em class="firstterm">reverse records</em>).
+ </div><div class="para">
+ Zones are defined on authoritative nameservers through the use of <em class="firstterm">zone files</em>, which define the resource records in that 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. Any nameserver can be a primary or secondary nameserver for multiple zones at the same time. It all depends on how the nameserver is configured.
+ </div></div><div class="section" title="7.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">7.1.2. Nameserver Types</h3></div></div></div><a id="id1998801" class="indexterm"></a><a id="id1998818" class="indexterm"></a><a id="id813836" class="indexterm"></a><a id="id813854" class="indexterm"></a><a id="id813871" class="indexterm"></a><a id="id881505" class="indexterm"></a><a id="id881519" class="indexterm"></a><a id="id881532" class="indexterm"></a><div class="para">
+ There are two nameserver configuration types:
+ </div><div class="variablelist"><dl><dt><span class="term">authoritative</span></dt><dd><div class="para">
+ This category includes both primary (master) and secondary (slave) servers. Those servers answer only for resource records which are part of their zones.
+ </div></dd><dt><span class="term">recursive</span></dt><dd><div class="para">
+ Offers resolution services, but is not authoritative for any zones. Answers for all resolutions are cached in memory for a fixed period of time, which is specified by the retrieved RR.
+ </div></dd></dl></div><div class="para">
+ A nameserver may be one or both of these types. For example, a nameserver can be a master for some zones, a slave for others, and offer recursive services for others. However the best practice is not to combine authoritative and recursive servers due their absolutely different requirements. Authoritative servers are available for all clients and they should be available all the time otherwise it is not possible to resolve particular subtree of the DNS database. Recursive lookups take far more time than authoritative responses thus recursive servers should be available for a restricted number of clients. Otherwise recursive server could be easy target for <em class="firstterm">distributed denial of service (DDoS)</em> attack.
+ </div></div><div class="section" title="7.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">7.1.3. BIND as a Nameserver</h3></div></div></div><a id="id870484" class="indexterm"></a><a id="id870502" class="indexterm"></a><a id="id910382" class="indexterm"></a><a id="id910404" class="indexterm"></a><a id="id1117218" class="indexterm"></a><div class="para">
+ BIND is set of DNS related programs. It contains a monolithic nameserver called <code class="command">/usr/sbin/named</code>, an administration utility called <code class="command">/usr/sbin/rndc</code> and DNS debugging utility called <code class="command">/usr/bin/dig</code>. More information about <code class="command">rndc</code> can be found in <a class="xref" href="#s1-bind-rndc" title="7.4. Using rndc">Section 7.4, “Using <code class="command">rndc</code> ”</a>.
+ </div><div class="para">
+ BIND stores its configuration files in the following locations:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="filename">/etc/named.conf</code> </span></dt><dd><div class="para">
+ The configuration file for the <code class="command">named</code> daemon
+ </div></dd><dt><span class="term"> <code class="filename">/var/named/</code> directory</span></dt><dd><div class="para">
+ The <code class="command">named</code> working directory which stores zone and statistic files
+ </div></dd></dl></div><div class="note"><h2>Note</h2><div class="para">
+ If you have installed the <code class="filename">bind-chroot</code> package, the BIND service will run in the <code class="command">/var/named/chroot</code> environment. All configuration files will be moved there. As such, <code class="filename">named.conf</code> will be located in <code class="filename">/var/named/chroot/etc/named.conf</code>, and so on.
+ </div></div><div class="para">
+ The next few sections review the BIND configuration in more detail.
+ </div></div></div><div class="section" title="7.2. /etc/named.conf" id="s1-bind-namedconf"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-namedconf">7.2. <code class="filename">/etc/named.conf</code> </h2></div></div></div><a id="id638889" class="indexterm"></a><a id="id921665" class="indexterm"></a><a id="id921683" class="indexterm"></a><div class="para">
+ The <code class="filename">named.conf</code> file is a collection of statements using nested options surrounded by opening and closing ellipse characters, <code class="command">{ }</code>. Administrators must be careful when editing <code class="filename">named.conf</code> to avoid syntax errors as many seemingly minor errors prevent the <code class="command">named</code> service from starting.
+ </div><div class="para">
+ A typical <code class="filename">named.conf</code> file is organized similar to the following example:
+ </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="section" title="7.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">7.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="section" title="7.2.1.1. acl Statement" id="s3-bind-namedconf-state-acl"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-namedconf-state-acl">7.2.1.1. <code class="command">acl</code> Statement</h4></div></div></div><div class="para">
+ The <code class="command">acl</code> (Access Control List) statement defines groups of hosts which can then be permitted or denied access to the nameserver.
+ </div><div class="para">
+ An <code class="command">acl</code> statement 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>;
+[<em class="replaceable"><code><match-element></code></em>; ...]
+};</pre><div class="para">
+ In this statement, replace <em class="replaceable"><code><acl-name></code></em> with the name of the access control list and replace <em class="replaceable"><code><match-element></code></em> with a semi-colon separated list of IP addresses. Most of the time, an individual IP address or CIDR network notation (such as <code class="command">10.0.1.0/24</code>) is used to identify the IP addresses within the <code class="command">acl</code> statement.
+ </div><div class="para">
+ The following access control lists are already defined as keywords to simplify configuration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">any</code> — Matches every IP address
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">localhost</code> — Matches any IP address in use by the local system
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">localnets</code> — Matches any IP address on any network to which the local system is connected
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">none</code> — Matches no IP addresses
+ </div></li></ul></div><div class="para">
+ When used in conjunction with other statements (such as the <code class="command">options</code> statement), <code class="command">acl</code> statements can be very useful in preventing the misuse of a BIND nameserver.
+ </div><div class="para">
+ The following example defines two access control lists and uses an <code class="command">options</code> statement to define how they are treated by the nameserver:
+ </div><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 class="para">
+ This example contains two access control lists, <code class="command">black-hats</code> and <code class="command">red-hats</code>. Hosts in the <code class="command">black-hats</code> list are denied access to the nameserver, while hosts in the <code class="command">red-hats</code> list are given normal access.
+ </div></div><div class="section" title="7.2.1.2. include Statement" id="s3-bind-namedconf-state-inc"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-namedconf-state-inc">7.2.1.2. <code class="command">include</code> Statement</h4></div></div></div><div class="para">
+ The <code class="command">include</code> statement allows files to be included in a <code class="filename">named.conf</code> file. In this way, sensitive configuration data (such as <code class="command">keys</code>) can be placed in a separate file with restrictive permissions.
+ </div><div class="para">
+ An <code class="command">include</code> statement takes the following form:
+ </div><pre class="screen">include "<em class="replaceable"><code><file-name></code></em>"</pre><div class="para">
+ In this statement, <em class="replaceable"><code><file-name></code></em> is replaced with an absolute path to a file.
+ </div></div><div class="section" title="7.2.1.3. options Statement" id="s3-bind-namedconf-state-opt"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-namedconf-state-opt">7.2.1.3. <code class="command">options</code> Statement</h4></div></div></div><div class="para">
+ The <code class="command">options</code> statement defines global server configuration options and sets defaults for other statements. It can be used to specify the location of the <code class="command">named</code> working directory, the types of queries allowed, and much more.
+ </div><div class="para">
+ The <code class="command">options</code> statement takes the following form:
+ </div><pre class="screen">options {
+<em class="replaceable"><code><option></code></em>;
+[<em class="replaceable"><code><option></code></em>; ...]
+};</pre><div class="para">
+ In this statement, the <em class="replaceable"><code><option></code></em> directives are replaced with a valid option.
+ </div><div class="para">
+ The following are commonly used options:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">allow-query</code> </span></dt><dd><div class="para">
+ Specifies which hosts are allowed to query this nameserver for authoritative RRs. By default, all hosts are allowed to query. An access control lists, or collection of IP addresses or networks, may be used here to allow only particular hosts to query the nameserver.
+ </div></dd><dt><span class="term"> <code class="command">allow-query-cache</code> </span></dt><dd><div class="para">
+ Similar to <code class="command">allow-query</code>, this option applies to non-authoritative data, like recursive queries. By default, only <code class="command">localhost;</code> and <code class="command">localnets;</code> are allowed to obtain non-authoritative data.
+ </div></dd><dt><span class="term"> <code class="command">blackhole</code> </span></dt><dd><div class="para">
+ Specifies which hosts are banned from the server. This option should be used when particular host or network floods the server with requests. Default is <code class="command">none;</code>
+ </div></dd><dt><span class="term"> <code class="command">directory</code> </span></dt><dd><div class="para">
+ Specifies the <code class="command">named</code> working directory if different from the default value, <code class="filename">/var/named/</code>.
+ </div></dd><dt><span class="term"> <code class="command">forwarders</code> </span></dt><dd><div class="para">
+ Specifies a list of valid IP addresses for nameservers where requests should be forwarded for resolution.
+ </div></dd><dt><span class="term"> <code class="command">forward</code> </span></dt><dd><div class="para">
+ Specifies the forwarding behavior of a <code class="command">forwarders</code> directive.
+ </div><div class="para">
+ The following options are accepted:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">first</code> — Specifies that the nameservers listed in the <code class="command">forwarders</code> directive be queried before <code class="command">named</code> attempts to resolve the name itself.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">only</code> — Specifies that <code class="command">named</code> does not attempt name resolution itself in the event that queries to nameservers specified in the <code class="command">forwarders</code> directive fail.
+ </div></li></ul></div></dd><dt><span class="term"> <code class="command">listen-on</code> </span></dt><dd><div class="para">
+ Specifies the IPv4 network interface on which <code class="command">named</code> listens for queries. By default, all IPv4 interfaces are used.
+ </div><div class="para">
+ Using this directive on a DNS server which also acts a gateway, BIND can be configured to only answer queries that originate from one of the networks.
+ </div><div class="para">
+ The following is an example of a <code class="command">listen-on</code> directive:
+ </div><pre class="screen">options { listen-on { 10.0.1.1; }; };</pre><div class="para">
+ In this example, server listens only on (<code class="command">10.0.1.1</code>) address.
+ </div></dd><dt><span class="term"> <code class="command">listen-on-v6</code> </span></dt><dd><div class="para">
+ Same as <code class="command">listen-on</code> except for IPv6 interfaces.
+ </div><div class="para">
+ The following is an example of a <code class="command">listen-on-v6</code> directive:
+ </div><pre class="screen">options { listen-on-v6 { 1234:5678::9abc; }; };</pre><div class="para">
+ In this example, server listens only on (<code class="command">1234:5678::9abc</code>) address.
+ </div></dd><dt><span class="term"> <code class="command">max-cache-size</code> </span></dt><dd><div class="para">
+ Specifies the maximum amount of memory to use for server caches. When the amount of data in the cache reaches this limit, the server will cause 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. Default is 32M.
+ </div><pre class="screen">options { max-cache-size 256M; };</pre></dd><dt><span class="term"> <code class="command">notify</code> </span></dt><dd><div class="para">
+ Controls whether <code class="command">named</code> notifies the slave servers when a zone is updated. It accepts the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Notifies slave servers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Does not notify slave servers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">master-only</code> - Send notify only when server is a master server for the zone.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">explicit</code> — Only notifies slave servers specified in an <code class="command">also-notify</code> list within a zone statement.
+ </div></li></ul></div></dd><dt><span class="term"> <code class="command">pid-file</code> </span></dt><dd><div class="para">
+ Specifies the location of the process ID file created by <code class="command">named</code>.
+ </div></dd><dt><span class="term"> <code class="command">recursion</code> </span></dt><dd><div class="para">
+ Specifies if <code class="command">named</code> acts as a recursive server. The default is <code class="command">yes</code>.
+ </div><pre class="screen">options { recursion no; };</pre></dd><dt><span class="term"> <code class="command">statistics-file</code> </span></dt><dd><div class="para">
+ Specifies an alternate location for statistics files. By default, <code class="command">named</code> statistics are saved to the <code class="filename">/var/named/named.stats</code> file.
+ </div></dd></dl></div><div class="para">
+ There are many other options also available, many of which rely upon one another to work properly. Refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#s2-bind-installed-docs" title="7.7.1. Installed Documentation">Section 7.7.1, “Installed Documentation”</a> and the <code class="filename">named.conf</code> man page for more details.
+ </div></div><div class="section" title="7.2.1.4. zone Statement" id="s3-bind-namedconf-state-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-namedconf-state-zone">7.2.1.4. <code class="command">zone</code> Statement</h4></div></div></div><div class="para">
+ A <code class="command">zone</code> statement defines the characteristics of a zone, such as the location of its configuration file and zone-specific options. This statement can be used to override the global <code class="command">options</code> statements.
+ </div><div class="para">
+ A <code class="command">zone</code> statement 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><zone-options></code></em>;
+[<em class="replaceable"><code><zone-options></code></em>; ...]
+};</pre><div class="para">
+ In this statement, <em class="replaceable"><code><zone-name></code></em> 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><zone-options></code></em> is a list of options characterizing the zone.
+ </div><div class="para">
+ The <em class="replaceable"><code><zone-name></code></em> attribute for the zone statement is particularly important. It is the default value assigned for the <code class="command">$ORIGIN</code> directive used within the corresponding zone file located in the <code class="filename">/var/named/</code> directory. The <code class="command">named</code> daemon appends the name of the zone to any non-fully qualified domain name listed in the zone file.
+ </div><div class="para">
+ For example, if a <code class="command">zone</code> statement defines the namespace for <code class="command">example.com</code>, use <code class="command">example.com</code> as the <em class="replaceable"><code><zone-name></code></em> so it is placed at the end of hostnames within the <code class="command">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="7.3. Zone Files">Section 7.3, “Zone Files”</a>.
+ </div><div class="para">
+ The most common <code class="command">zone</code> statement options include the following:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">allow-query</code> </span></dt><dd><div class="para">
+ Specifies the clients that are allowed to request information about this zone. Setting of this option overrides global <code class="command">allow-query</code> option. The default is to allow all query requests.
+ </div></dd><dt><span class="term"> <code class="command">allow-transfer</code> </span></dt><dd><div class="para">
+ Specifies the slave servers that are allowed to request a transfer of the zone's information. The default is to allow all transfer requests.
+ </div></dd><dt><span class="term"> <code class="command">allow-update</code> </span></dt><dd><div class="para">
+ Specifies the hosts that are allowed to dynamically update information in their zone. The default is to deny all dynamic update requests.
+ </div><div class="para">
+ 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. Use TSIG key instead .
+ </div></dd><dt><span class="term"> <code class="command">file</code> </span></dt><dd><div class="para">
+ Specifies the name of the file in the <code class="command">named</code> working directory that contains the zone's configuration data.
+ </div></dd><dt><span class="term"> <code class="command">masters</code> </span></dt><dd><div class="para">
+ Specifies the IP addresses from which to request authoritative zone information and is used only if the zone is defined as <code class="command">type</code> <code class="command">slave</code>.
+ </div></dd><dt><span class="term"> <code class="command">notify</code> </span></dt><dd><div class="para">
+ Specifies whether or not <code class="command">named</code> notifies the slave servers when a zone is updated. This option has same parameters as a global <code class="command">notify</code> parameter.
+ </div></dd><dt><span class="term"> <code class="command">type</code> </span></dt><dd><div class="para">
+ Defines the type of zone.
+ </div><div class="para">
+ Below is a list of valid options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">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="command">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="command">forward</code> — Forwards all requests for information about this zone to other nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">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="command">hint</code> zone.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">master</code> — Designates the nameserver as authoritative for this zone. A zone should be set as the <code class="command">master</code> if the zone's configuration files reside on the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">slave</code> — Designates the nameserver as a slave server for this zone. Master server is specified in <code class="command">masters</code> directive.
+ </div></li></ul></div></dd></dl></div></div><div class="section" title="7.2.1.5. Sample zone Statements" id="s3-bind-configuration-named-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-configuration-named-zone">7.2.1.5. Sample <code class="command">zone</code> Statements</h4></div></div></div><a id="id899903" class="indexterm"></a><div class="para">
+ Most changes to the <code class="filename">/etc/named.conf</code> file of a master or slave nameserver involves adding, modifying, or deleting <code class="command">zone</code> statements. While these <code class="command">zone</code> statements can contain many options, most nameservers require only a small subset to function efficiently. The following <code class="command">zone</code> statements are very basic examples illustrating a master-slave nameserver relationship.
+ </div><div class="para">
+ The following is an example of a <code class="command">zone</code> statement for the primary nameserver hosting <code class="command">example.com</code> (<code class="command">192.168.0.1</code>):
+ </div><pre class="screen">zone "example.com" IN {
+type master;
+file "example.com.zone";
+allow-transfer { 192.168.0.2; };
+};</pre><div class="para">
+ In the statement, the zone is identified as <code class="command">example.com</code>, the type is set to <code class="command">master</code>, and the <code class="command">named</code> service is instructed to read the <code class="filename">/var/named/example.com.zone</code> file. It also allows only slave nameserver (<code class="command">192.168.0.2</code>) to transfer the zone.
+ </div><div class="para">
+ A slave server's <code class="command">zone</code> statement for <code class="command">example.com</code> is slightly different from the previous example. For a slave server, the type is set to <code class="command">slave</code> and the <code class="command">masters</code> directive is telling <code class="command">named</code> the IP address of the master server.
+ </div><div class="para">
+ The following is an example slave server <code class="command">zone</code> statement for <code class="command">example.com</code> zone:
+ </div><pre class="screen">zone "example.com"{
+type slave;
+file "slaves/example.com.zone";
+masters { 192.168.0.1; };
+};</pre><div class="para">
+ This <code class="command">zone</code> statement configures <code class="command">named</code> on the slave server to query the master server at the <code class="command">192.168.0.1</code> IP address for information about the <code class="command">example.com</code> zone. The information that the slave server receives from the master server is saved to the <code class="filename">/var/named/slaves/example.com.zone</code> file. Make sure you put all slave zones to <code class="filename">/var/named/slaves</code> directory otherwise <code class="command">named</code> will fail to transfer the zone.
+ </div></div></div><div class="section" title="7.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">7.2.2. Other Statement Types</h3></div></div></div><div class="para">
+ The following is a list of lesser used statement types available within <code class="filename">named.conf</code>:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">controls</code> </span></dt><dd><div class="para">
+ Configures various security requirements necessary to use the <code class="command">rndc</code> command to administer the <code class="command">named</code> service.
+ </div><div class="para">
+ Refer to <a class="xref" href="#s2-bind-rndc-configuration-namedconf" title="7.4.1. Configuring /etc/named.conf">Section 7.4.1, “Configuring <code class="filename">/etc/named.conf</code> ”</a> to learn more about how the <code class="command">controls</code> statement is structured and what options are available.
+ </div></dd><dt><span class="term"> <code class="command">key "<em class="replaceable"><code><key-name></code></em>"</code> </span></dt><dd><div class="para">
+ Defines 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="command">key</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">algorithm <em class="replaceable"><code><algorithm-name></code></em> </code> — The type of algorithm used, such as <code class="command">hmac-md5</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">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="#s2-bind-rndc-configuration-rndcconf" title="7.4.2. Configuring /etc/rndc.conf">Section 7.4.2, “Configuring <code class="filename">/etc/rndc.conf</code> ”</a> for instructions on how to write a <code class="command">key</code> statement.
+ </div></dd><dt><span class="term"> <code class="command">logging</code> </span></dt><dd><div class="para">
+ Allows for the use of multiple types of logs, called <em class="firstterm">channels</em>. By using the <code class="command">channel</code> option within the <code class="command">logging</code> statement, a customized type of log can be constructed — with its own file name (<code class="command">file</code>), size limit (<code class="command">size</code>), versioning (<code class="command">version</code>), and level of importance (<code class="command">severity</code>). Once a customized channel is defined, a <code class="command">category</code> option is used to categorize the channel and begin logging when <code class="command">named</code> is restarted.
+ </div><div class="para">
+ By default, <code class="command">named</code> logs standard messages to the <code class="command">rsyslog</code> daemon, which places them in <code class="filename">/var/log/messages</code>. This occurs because several standard channels are built into BIND with various severity levels, such as <code class="command">default_syslog</code> (which handles informational logging messages) and <code class="command">default_debug</code> (which specifically handles debugging messages). A default category, called <code class="command">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="7.7.1. Installed Documentation">Section 7.7.1, “Installed Documentation”</a>.
+ </div></dd><dt><span class="term"> <code class="command">server</code> </span></dt><dd><div class="para">
+ Specifies options that affect how <code class="command">named</code> should respond to remote nameservers, especially with regard to notifications and zone transfers.
+ </div><div class="para">
+ The <code class="command">transfer-format</code> option controls whether one resource record is sent with each message (<code class="command">one-answer</code>) or multiple resource records are sent with each message (<code class="command">many-answers</code>). While <code class="command">many-answers</code> is more efficient, only newer BIND nameservers understand it.
+ </div></dd><dt><span class="term"> <code class="command">trusted-keys</code> </span></dt><dd><div class="para">
+ Contains assorted public keys used for secure DNS (DNSSEC). Refer to <a class="xref" href="#s2-bind-features-security" title="7.5.3. Security">Section 7.5.3, “Security”</a> for more information concerning BIND security.
+ </div></dd><dt><span class="term"> <code class="command">view "<em class="replaceable"><code><view-name></code></em>"</code> </span></dt><dd><div class="para">
+ Creates 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 may be used, but their names must be unique. The <code class="command">match-clients</code> option specifies the IP addresses that apply to a particular view. Any <code class="command">options</code> statement may also be used within a view, overriding the global options already configured for <code class="command">named</code>. Most <code class="command">view</code> statements contain multiple <code class="command">zone</code> statements that apply to the <code class="command">match-clients</code> list. The order in which <code class="command">view</code> statements are listed is important, as the first <code class="command">view</code> statement that matches a particular client's IP address is used.
+ </div><div class="para">
+ Refer to <a class="xref" href="#s2-bind-features-views" title="7.5.2. Multiple Views">Section 7.5.2, “Multiple Views”</a> for more information about the <code class="command">view</code> statement.
+ </div></dd></dl></div></div><div class="section" title="7.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">7.2.3. Comment Tags</h3></div></div></div><div class="para">
+ The following is a list of valid comment tags used within <code class="filename">named.conf</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">//</code> — When placed at the beginning of a line, that line is ignored by <code class="command">named</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">#</code> — When placed at the beginning of a line, that line is ignored by <code class="command">named</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">/*</code> and <code class="command">*/</code> — When text is enclosed in these tags, the block of text is ignored by <code class="command">named</code>.
+ </div></li></ul></div></div></div><div class="section" title="7.3. Zone Files" id="s1-bind-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-zone">7.3. Zone Files</h2></div></div></div><a id="id1943792" class="indexterm"></a><div class="para">
+ <em class="firstterm">Zone files</em> contain information about a namespace and are stored in the <code class="command">named</code> working directory (<code class="filename">/var/named/</code>) by default. Each zone file is named according to the <code class="command">file</code> option data in the <code class="command">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="note"><h2>Note</h2><div class="para">
+ If you have installed the <code class="filename">bind-chroot</code> package, the BIND service will run in the <code class="command">/var/named/chroot</code> environment. All configuration files will be moved there. As such, you can find the zone files in <code class="filename">/var/named/chroot/var/named</code>.
+ </div></div><div class="para">
+ Each zone file may contain <em class="firstterm">directives</em> and <em class="firstterm">resource records</em>. 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. Directives are optional, but resource records are required 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="para">
+ Comments can be placed after semicolon characters (<code class="command">;</code>) in zone files.
+ </div><div class="section" title="7.3.1. Zone File Directives" id="s2-bind-zone-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-zone-directives">7.3.1. Zone File Directives</h3></div></div></div><a id="id747531" class="indexterm"></a><div class="para">
+ Directives begin with the dollar sign character (<code class="command">$</code>) followed by the name of the directive. They usually appear at the top of the zone file.
+ </div><div class="para">
+ The following are commonly used directives:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">$INCLUDE</code> </span></dt><dd><div class="para">
+ Configures <code class="command">named</code> to include another zone file in this zone file at the place where the directive appears. This allows additional zone settings to be stored apart from the main zone file.
+ </div></dd><dt><span class="term"> <code class="command">$ORIGIN</code> </span></dt><dd><div class="para">
+ Appends the domain name to unqualified records, such as those with the hostname and nothing more.
+ </div><div class="para">
+ For example, a zone file may contain the following line:
+ </div><pre class="screen">$ORIGIN example.com.</pre><div class="para">
+ Any names used in resource records that do not end in a trailing period (<code class="command">.</code>) are appended with <code class="command">example.com</code>.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ The use of the <code class="command">$ORIGIN</code> directive is unnecessary if the zone is specified in <code class="filename">/etc/named.conf</code> because the zone name is used as the value for the <code class="command">$ORIGIN</code> directive by default.
+ </div></div></dd><dt><span class="term"> <code class="command">$TTL</code> </span></dt><dd><div class="para">
+ Sets the default <em class="firstterm">Time to Live (TTL)</em> value for the zone. This is the length of time, in seconds, that a zone resource record is 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></dd></dl></div></div><div class="section" title="7.3.2. Zone File 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">7.3.2. Zone File Resource Records</h3></div></div></div><a id="id1124120" class="indexterm"></a><div class="para">
+ The primary component of a zone file is its resource records.
+ </div><div class="para">
+ There are many types of zone file resource records. The following are used most frequently:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">A</code> </span></dt><dd><div class="para">
+ This refers to the Address record, which specifies an IP address to assign to a name, as in this example:
+ </div><pre class="screen">
+ <em class="replaceable"><code><host></code></em> IN A <em class="replaceable"><code><IP-address></code></em>
+</pre><div class="para">
+ If the <em class="replaceable"><code><host></code></em> value is omitted, then an <code class="command">A</code> record points to a default IP address for the top of the namespace. This system is the target for all non-FQDN requests.
+ </div><div class="para">
+ Consider the following <code class="command">A</code> record examples for the <code class="command">example.com</code> zone file:
+ </div><pre class="screen">
+server1 IN A 10.0.1.3
+ IN A 10.0.1.5
+</pre><div class="para">
+ Requests for <code class="command">example.com</code> are pointed to 10.0.1.3 or 10.0.1.5.
+ </div></dd><dt><span class="term"> <code class="command">CNAME</code> </span></dt><dd><div class="para">
+ This refers to the Canonical Name record, which maps one name to another. This type of record can also be referred to as an <em class="firstterm">alias record</em>.
+ </div><div class="para">
+ The next example tells <code class="command">named</code> that any requests sent to the <em class="replaceable"><code><alias-name></code></em> should point to the host, <em class="replaceable"><code><real-name></code></em>. <code class="command">CNAME</code> records are most commonly used to point to services that use a common naming scheme, such as <code class="command">www</code> for Web servers.
+ </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">
+ In the following example, an <code class="command">A</code> record binds a hostname to an IP address, while a <code class="command">CNAME</code> record points the commonly used <code class="command">www</code> hostname to it.
+ </div><pre class="screen">server1 IN A 10.0.1.5
+www IN CNAME server1</pre></dd><dt><span class="term"> <code class="command">MX</code> </span></dt><dd><div class="para">
+ This refers to the Mhail eXchange record, which tells where mail sent to a particular namespace controlled by this zone should go.
+ </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">
+ Here, 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">
+ The <em class="replaceable"><code><email-server-name></code></em> may be a hostname or FQDN.
+ </div><pre class="screen">IN MX 10 mail.example.com.
+IN MX 20 mail2.example.com.</pre><div class="para">
+ In this example, the first <code class="command">mail.example.com</code> email server is preferred to the <code class="command">mail2.example.com</code> email server when receiving email destined for the <code class="command">example.com</code> domain.
+ </div></dd><dt><span class="term"> <code class="command">NS</code> </span></dt><dd><div class="para">
+ This refers to the NameServer record, which announces the authoritative nameservers for a particular zone.
+ </div><div class="para">
+ The following illustrates the layout of an <code class="command">NS</code> record:
+ </div><pre class="screen"> IN NS <em class="replaceable"><code><nameserver-name></code></em>
+</pre><div class="para">
+ Here, <em class="replaceable"><code><nameserver-name></code></em> should be an FQDN.
+ </div><div class="para">
+ Next, two nameservers are listed as authoritative for the domain. It is not important whether these nameservers are slaves or if one is a master; they are both still considered authoritative.
+ </div><pre class="screen">IN NS dns1.example.com.
+IN NS dns2.example.com.</pre></dd><dt><span class="term"> <code class="command">PTR</code> </span></dt><dd><div class="para">
+ This refers to the PoinTeR record, which is designed to point to another part of the namespace.
+ </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="7.3.4. Reverse Name Resolution Zone Files">Section 7.3.4, “Reverse Name Resolution Zone Files”</a> for more examples of <code class="command">PTR</code> records in use.
+ </div></dd><dt><span class="term"> <code class="command">SOA</code> </span></dt><dd><div class="para">
+ This refers to the Start Of Authority resource record, which proclaims important authoritative information about a namespace to the nameserver.
+ </div><div class="para">
+ Located after the directives, an <code class="command">SOA</code> resource record is the first resource record in a zone file.
+ </div><div class="para">
+ The following shows the basic structure of an <code class="command">SOA</code> resource record:
+ </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 <code class="command">@</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. The hostname of the primary nameserver that is authoritative for this domain is the <em class="replaceable"><code><primary-name-server></code></em> directive, and the email of the person to contact about this namespace is the <em class="replaceable"><code><hostmaster-email></code></em> directive.
+ </div><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 <code class="command">named</code> to reload the zone. The <em class="replaceable"><code><time-to-refresh></code></em> directive is the numerical value slave servers use to determine how long to wait before asking the master nameserver if any changes have been made to the zone. The <em class="replaceable"><code><serial-number></code></em> directive is a numerical value used by the slave servers to determine if it is using outdated zone data and should therefore refresh it.
+ </div><div class="para">
+ The <em class="replaceable"><code><time-to-retry></code></em> directive is a numerical value used by slave servers to determine the length of time to wait before issuing a refresh request in the event that the master nameserver is not answering. If the master 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 slave servers stop responding as an authority for requests concerning that namespace.
+ </div><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. However, in BIND 9, the <em class="replaceable"><code><minimum-TTL></code></em> directive defines how long negative answers are cached for. Caching of negative answers can be set to a maximum of 3 hours (<code class="option">3H</code>).
+ </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="command">M</code>), hours (<code class="command">H</code>), days (<code class="command">D</code>), and weeks (<code class="command">W</code>). The table in <a class="xref" href="#tb-bind-seconds" title="Table 7.1. Seconds compared to other time units">Table 7.1, “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 7.1. Seconds compared to other time units" id="tb-bind-seconds"><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>
+ <code class="command">60</code>
+ </td><td>
+ <code class="command">1M</code>
+ </td></tr><tr><td>
+ <code class="command">1800</code>
+ </td><td>
+ <code class="command">30M</code>
+ </td></tr><tr><td>
+ <code class="command">3600</code>
+ </td><td>
+ <code class="command">1H</code>
+ </td></tr><tr><td>
+ <code class="command">10800</code>
+ </td><td>
+ <code class="command">3H</code>
+ </td></tr><tr><td>
+ <code class="command">21600</code>
+ </td><td>
+ <code class="command">6H</code>
+ </td></tr><tr><td>
+ <code class="command">43200</code>
+ </td><td>
+ <code class="command">12H</code>
+ </td></tr><tr><td>
+ <code class="command">86400</code>
+ </td><td>
+ <code class="command">1D</code>
+ </td></tr><tr><td>
+ <code class="command">259200</code>
+ </td><td>
+ <code class="command">3D</code>
+ </td></tr><tr><td>
+ <code class="command">604800</code>
+ </td><td>
+ <code class="command">1W</code>
+ </td></tr><tr><td>
+ <code class="command">31536000</code>
+ </td><td>
+ <code class="command">365D</code>
+ </td></tr></tbody></table></div><h6>Table 7.1. Seconds compared to other time units</h6></div><br class="table-break" /><div class="para">
+ The following example illustrates the form an <code class="command">SOA</code> resource record might take when it is populated with real values.
+ </div><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></dd></dl></div></div><div class="section" title="7.3.3. Example Zone File" id="s2-bind-zone-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-zone-examples">7.3.3. Example Zone File</h3></div></div></div><a id="id1225239" class="indexterm"></a><div class="para">
+ Seen individually, directives and resource records can be difficult to grasp. However, when placed together in a single file, they become easier to understand.
+ </div><div class="para">
+ The following example shows a very basic zone file.
+ </div><pre class="screen">$ORIGIN example.com.
+$TTL 86400
+@ 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
+;
+;
+ NS dns1.example.com.
+ NS dns2.example.com.
+dns1 A 10.0.1.1
+ AAAA aaaa:bbbb::1
+dns2 A 10.0.1.2
+ AAAA aaaa:bbbb::2
+;
+;
+@ MX 10 mail.example.com.
+ MX 20 mail2.example.com.
+mail A 10.0.1.5
+ AAAA aaaa:bbbb::5
+mail2 A 10.0.1.6
+ AAAA aaaa:bbbb::6
+;
+;
+; This sample zone file illustrates sharing the same IP addresses for multiple services:
+;
+services A 10.0.1.10
+ AAAA aaaa:bbbb::10
+ A 10.0.1.11
+ AAAA aaaa:bbbb::11
+
+ftp CNAME services.example.com.
+www CNAME services.example.com.
+;
+;
+</pre><div class="para">
+ In this example, standard directives and <code class="command">SOA</code> values are used. The authoritative nameservers are set as <code class="command">dns1.example.com</code> and <code class="command">dns2.example.com</code>, which have <code class="command">A</code> records that tie them to <code class="command">10.0.1.1</code> and <code class="command">10.0.1.2</code>, respectively.
+ </div><div class="para">
+ The email servers configured with the <code class="command">MX</code> records point to <code class="command">mail</code> and <code class="command">mail2</code> via <code class="command">A</code> records. Since the <code class="command">mail</code> and <code class="command">mail2</code> names do not end in a trailing period (<code class="command">.</code>), the <code class="command">$ORIGIN</code> domain is placed after them, expanding them to <code class="command">mail.example.com</code> and <code class="command">mail2.example.com</code>. Through the related <code class="command">A</code> resource records, their IP addresses can be determined.
+ </div><div class="para">
+ Services available at the standard names, such as <code class="command">www.example.com</code> (<acronym class="acronym">WWW</acronym>), are pointed at the appropriate servers using a <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">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="7.3.4. Reverse Name Resolution Zone Files" id="s2-bind-configuration-zone-reverse"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-configuration-zone-reverse">7.3.4. Reverse Name Resolution Zone Files</h3></div></div></div><a id="id896894" 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 FQDN. It looks very similar to a standard zone file, except that <code class="command">PTR</code> resource records are used to link the IP addresses to a fully qualified domain name.
+ </div><div class="para">
+ The following illustrates the layout of a <code class="command">PTR</code> record:
+ </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> is the last number in an IP address which points to a particular system's FQDN.
+ </div><div class="para">
+ In the following example, IP addresses <code class="command">10.0.1.1</code> through <code class="command">10.0.1.6</code> are pointed to corresponding FQDNs. It can be located in <code class="filename">/var/named/example.com.rr.zone</code>.
+ </div><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 class="para">
+ This zone file would be called into service with a <code class="command">zone</code> statement in the <code class="filename">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 class="section" title="7.4. Using rndc" id="s1-bind-rndc"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-rndc">7.4. Using <code class="command">rndc</code> </h2></div></div></div><a id="id817343" class="indexterm"></a><div class="para">
+ BIND includes a utility called <code class="command">rndc</code> which allows command line administration of the <code class="command">named</code> daemon from the localhost or a remote host.
+ </div><div class="para">
+ In order to prevent unauthorized access to the <code class="command">named</code> daemon, BIND uses a shared secret key authentication method to grant privileges to hosts. This means an identical key must be present in both <code class="filename">/etc/named.conf</code> and the <code class="command">rndc</code> configuration file, <code class="filename">/etc/rndc.conf</code>.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ If you have installed the <code class="filename">bind-chroot</code> package, the BIND service will run in the <code class="command">/var/named/chroot</code> environment. All configuration files will be moved there. As such, the <code class="filename">rndc.conf</code> file is located in <code class="filename">/var/named/chroot/etc/rndc.conf</code>.
+ </div><div class="para">
+ Note that since the <code class="command">rndc</code> utility does not run in a <code class="command">chroot</code> environment, <code class="filename">/etc/rndc.conf</code> is a symlink to <code class="filename">/var/named/chroot/etc/rndc.conf</code>.
+ </div></div><div class="section" title="7.4.1. Configuring /etc/named.conf" id="s2-bind-rndc-configuration-namedconf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-configuration-namedconf">7.4.1. Configuring <code class="filename">/etc/named.conf</code> </h3></div></div></div><a id="id752944" class="indexterm"></a><div class="para">
+ In order for <code class="command">rndc</code> to connect to a <code class="command">named</code> service, there must be a <code class="command">controls</code> statement in the BIND server's <code class="filename">/etc/named.conf</code> file.
+ </div><div class="para">
+ The <code class="command">controls</code> statement, shown in the following example, allows <code class="command">rndc</code> to connect from the localhost.
+ </div><pre class="screen">
+controls {
+ inet 127.0.0.1
+ allow { localhost; } keys { <em class="replaceable"><code><key-name></code></em>; };
+};
+</pre><div class="para">
+ This statement tells <code class="command">named</code> to listen on the default TCP port 953 of the loopback address and allow <code class="command">rndc</code> commands coming from the localhost, if the proper key is given. The <em class="replaceable"><code><key-name></code></em> specifies a name in the <code class="command">key</code> statement within the <code class="filename">/etc/named.conf</code> file. The next example illustrates a sample <code class="command">key</code> statement.
+ </div><pre class="screen">
+key "<em class="replaceable"><code><key-name></code></em>" {
+ algorithm hmac-md5;
+ secret "<em class="replaceable"><code><key-value></code></em>";
+};
+</pre><div class="para">
+ In this case, the <em class="replaceable"><code><key-value></code></em> uses the HMAC-MD5 algorithm. Use the following command to generate keys using the HMAC-MD5 algorithm:
+ </div><pre class="screen">
+<code class="command">dnssec-keygen -a hmac-md5 -b <em class="replaceable"><code><bit-length></code></em> -n HOST <em class="replaceable"><code><key-file-name></code></em> </code>
+</pre><div class="para">
+ A key with at least a 256-bit length is a good idea. The actual key that should be placed in the <em class="replaceable"><code><key-value></code></em> area can be found in the <code class="filename"><em class="replaceable"><code><key-file-name></code></em> </code> file generated by this command.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ Because <code class="filename">/etc/named.conf</code> is world-readable, it is advisable to place the <code class="command">key</code> statement in a separate file, readable only by root, and then use an <code class="command">include</code> statement to reference it. For example:
+ </div><pre class="screen">include "/etc/rndc.key";</pre></div></div><div class="section" title="7.4.2. Configuring /etc/rndc.conf" id="s2-bind-rndc-configuration-rndcconf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-configuration-rndcconf">7.4.2. Configuring <code class="filename">/etc/rndc.conf</code> </h3></div></div></div><a id="id749332" class="indexterm"></a><a id="id852523" class="indexterm"></a><div class="para">
+ The <code class="command">key</code> is the most important statement in <code class="filename">/etc/rndc.conf</code>.
+ </div><pre class="screen">
+key "<em class="replaceable"><code><key-name></code></em>" {
+ algorithm hmac-md5;
+ secret "<em class="replaceable"><code><key-value></code></em>";
+};
+</pre><div class="para">
+ The <em class="replaceable"><code><key-name></code></em> and <em class="replaceable"><code><key-value></code></em> should be exactly the same as their settings in <code class="filename">/etc/named.conf</code>.
+ </div><div class="para">
+ To match the keys specified in the target server's <code class="filename">/etc/named.conf</code>, add the following lines to <code class="filename">/etc/rndc.conf</code>.
+ </div><pre class="screen">
+options {
+ default-server localhost;
+ default-key "<em class="replaceable"><code><key-name></code></em>";
+};
+</pre><div class="para">
+ This directive sets a global default key. However, the <code class="filename">rndc</code> configuration file can also specify different keys for different servers, as in the following example:
+ </div><pre class="screen">
+server localhost {
+ key "<em class="replaceable"><code><key-name></code></em>";
+};
+</pre><div class="important"><h2>Important</h2><div class="para">
+ Make sure that only the root user can read or write to the <code class="filename">/etc/rndc.conf</code> file.
+ </div></div><div class="para">
+ For more information about the <code class="filename">/etc/rndc.conf</code> file, refer to the <code class="filename">rndc.conf</code> man page.
+ </div></div><div class="section" title="7.4.3. Command Line Options" id="s2-bind-rndc-options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-options">7.4.3. Command Line Options</h3></div></div></div><a id="id884922" class="indexterm"></a><div class="para">
+ An <code class="command">rndc</code> command takes the following form:
+ </div><pre class="screen">rndc <em class="replaceable"><code><options></code></em> <em class="replaceable"><code><command></code></em> <em class="replaceable"><code><command-options></code></em>
+</pre><div class="para">
+ When executing <code class="command">rndc</code> on a properly configured localhost, the following commands are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">halt</code> — Stops the <code class="filename">named</code> service immediately.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">querylog</code> — Logs all queries made to this nameserver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">refresh</code> — Refreshes the nameserver's database.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">reload</code> — Reloads the zone files but keeps all other previously cached responses. This command also allows changes to zone files without losing all stored name resolutions.
+ </div><div class="para">
+ If changes made only affect a specific zone, reload only that specific zone by adding the name of the zone after the <code class="command">reload</code> command.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">stats</code> — Dumps the current <code class="command">named</code> statistics to the <code class="filename">/var/named/named.stats</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">stop</code> — Stops the server gracefully, saving any dynamic update and <em class="firstterm">Incremental Zone Transfers</em> (<em class="firstterm">IXFR</em>) data before exiting.
+ </div></li></ul></div><div class="para">
+ Occasionally, it may be necessary to override the default settings in the <code class="filename">/etc/rndc.conf</code> file. The following options are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-c <em class="replaceable"><code><configuration-file></code></em> </code> — Specifies the alternate location of a configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-p <em class="replaceable"><code><port-number></code></em> </code> — Specifies a port number to use for the <code class="command">rndc</code> connection other than the default port 953.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-s <em class="replaceable"><code><server></code></em> </code> — Specifies a server other than the <code class="command">default-server</code> listed in <code class="filename">/etc/rndc.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-y <em class="replaceable"><code><key-name></code></em> </code> — Specifies a key other than the <code class="command">default-key</code> option in <code class="filename">/etc/rndc.conf</code>.
+ </div></li></ul></div><div class="para">
+ Additional information about these options can be found in the <code class="command">rndc</code> man page.
+ </div></div></div><div class="section" title="7.5. 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">7.5. Advanced Features of BIND</h2></div></div></div><a id="id665530" class="indexterm"></a><div class="para">
+ Most BIND implementations only use <code class="command">named</code> to provide name resolution services or to act as an authority for a particular domain or sub-domain. However, BIND version 9 has a number of advanced features that allow for a more secure and efficient DNS service.
+ </div><div class="warning"><h2>Caution</h2><div class="para">
+ Some of these advanced features, such as DNSSEC, TSIG, and IXFR (which are defined in the following section), should only be used in network environments with nameservers that support the features. If the network environment includes non-BIND or older BIND nameservers, verify that each advanced feature is supported before attempting to use it.
+ </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="7.7.1. Installed Documentation">Section 7.7.1, “Installed Documentation”</a>.
+ </div><div class="section" title="7.5.1. DNS Protocol Enhancements" id="s2-bind-features-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-protocol">7.5.1. DNS Protocol Enhancements</h3></div></div></div><a id="id1191681" class="indexterm"></a><div class="para">
+ BIND supports Incremental Zone Transfers (IXFR), where a slave nameserver only downloads the updated portions of a zone modified on a master nameserver. The standard transfer process requires that the entire zone be transferred to each slave nameserver for even the smallest change. For very popular domains with very lengthy zone files and many slave nameservers, IXFR makes the notification and update process much less resource-intensive.
+ </div><div class="para">
+ Note that IXFR is only available when using <em class="firstterm">dynamic updating</em> to make changes to master zone records. If manually editing zone files to make changes, Automatic Zone Transfer (AXFR) is used. More information on dynamic updating is available in the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#s2-bind-installed-docs" title="7.7.1. Installed Documentation">Section 7.7.1, “Installed Documentation”</a>.
+ </div></div><div class="section" title="7.5.2. 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">7.5.2. Multiple Views</h3></div></div></div><a id="id765243" class="indexterm"></a><div class="para">
+ Through the use of the <code class="command">view</code> statement in <code class="filename">named.conf</code>, BIND can present different information depending on which network a request originates from.
+ </div><div class="para">
+ 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">
+ The <code class="command">view</code> statement uses the <code class="command">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="7.5.3. Security" id="s2-bind-features-security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-security">7.5.3. Security</h3></div></div></div><a id="id725313" class="indexterm"></a><div class="para">
+ BIND supports a number of different methods to protect the updating and transfer of zones, on both master and slave nameservers:
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="emphasis"><em>DNSSEC</em></span> </span></dt><dd><div class="para">
+ Short for <em class="firstterm">DNS SECurity</em>, this feature allows for zones to be cryptographically signed with a <em class="firstterm">zone key</em>.
+ </div><div class="para">
+ In this way, the information about a specific zone can be verified as coming from a nameserver that has signed it with a particular private key, as long as the recipient has that nameserver's public key.
+ </div><div class="para">
+ BIND version 9 also supports the SIG(0) public/private key method of message authentication.
+ </div></dd><dt><span class="term"> <span class="emphasis"><em>TSIG</em></span> </span></dt><dd><div class="para">
+ Short for <em class="firstterm">Transaction SIGnatures</em>, this feature allows a transfer from master to slave only after verifying that a shared secret key exists on both nameservers.
+ </div><div class="para">
+ This feature strengthens the standard IP address-based method of transfer authorization. An attacker 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">
+ BIND version 9 also supports <em class="firstterm">TKEY</em>, which is another shared secret key method of authorizing zone transfers.
+ </div></dd></dl></div></div><div class="section" title="7.5.4. IP version 6" id="s2-bind-features-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-ipv6">7.5.4. IP version 6</h3></div></div></div><a id="id881246" class="indexterm"></a><div class="para">
+ BIND version 9 supports name service in IP version 6 (IPv6) environments through the use of <code class="command">A6</code> zone records.
+ </div><div class="para">
+ If the network environment includes both IPv4 and IPv6 hosts, use the <code class="command">lwresd</code> lightweight resolver daemon on all network clients. This daemon is a very efficient, caching-only nameserver which understands the new <code class="command">A6</code> and <code class="command">DNAME</code> records used under IPv6. Refer to the <code class="command">lwresd</code> man page for more information.
+ </div></div></div><div class="section" title="7.6. 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">7.6. Common Mistakes to Avoid</h2></div></div></div><a id="id1530275" class="indexterm"></a><div class="para">
+ It is very common for beginners to make mistakes when editing BIND configuration files. Be sure to avoid the following issues:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Take care to increment the serial number when editing a zone file.</em></span>
+ </div><div class="para">
+ If the serial number is not incremented, the master nameserver has the correct, new information, but the slave nameservers are never notified of the change and do not attempt to refresh their data of that zone.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Be careful to use ellipses and semi-colons correctly in the <code class="filename">/etc/named.conf</code> file.</em></span>
+ </div><div class="para">
+ An omitted semi-colon or unclosed ellipse section can cause <code class="command">named</code> to refuse to start.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Remember to place periods (<code class="command">.</code>) in zone files after all FQDNs and omit them on hostnames.</em></span>
+ </div><div class="para">
+ A period at the end of a domain name denotes a fully qualified domain name. If the period is omitted, then <code class="command">named</code> appends the name of the zone or the <code class="command">$ORIGIN</code> value to complete it.
+ </div></li><li class="listitem"><div class="para">
+ If a firewall is blocking connections from the <code class="command">named</code> daemon to other nameservers, the recommended best practice is to change the firewall settings whenever possible.
+ </div><div class="warning"><h2>Warning: Avoid Using Fixed UDP Source Ports</h2><div class="para">
+ Recent research in DNS security has shown that using a fixed UDP source port for DNS queries is a potential security vulnerability that could allow an attacker to more easily conduct cache-poisoning attacks. Due to this security threat, Red Hat issued a security update<sup>[<a id="id858805" href="#ftn.id858805" class="footnote">3</a>]</sup> for all versions of Red Hat Enterprise Linux which updated the default sample caching-nameserver configuration files so that they do not specify a fixed query-source port, thus causing the BIND nameserver to use a new, randomly-selected source port for each DNS query by default. This method had previously only been used during <span class="application"><strong>named</strong></span> service startup.
+ </div><div class="para">
+ DNS resolving is at risk whenever <span class="application"><strong>named</strong></span> is configured to use a static UDP source port. To avoid this risk, we recommend configuring your firewall to allow queries from a random UDP source port.
+ </div><div class="para">
+ BIND administrators with existing configurations who wish to take advantage of randomized UDP source ports should check their configuration files to ensure that they have not specified fixed query-source ports.
+ </div></div></li></ul></div></div><div class="section" title="7.7. 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">7.7. Additional Resources</h2></div></div></div><a id="id913408" class="indexterm"></a><div class="para">
+ The following sources of information provide additional resources regarding BIND.
+ </div><div class="section" title="7.7.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">7.7.1. Installed Documentation</h3></div></div></div><a id="id933360" 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-number></code></em> with the version of <code class="filename">bind</code> installed on the system:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code><version-number></code></em>/</code> </span></dt><dd><div class="para">
+ This directory lists the most recent features.
+ </div></dd><dt><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code><version-number></code></em>/arm/</code> </span></dt><dd><div class="para">
+ This directory contains 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><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code><version-number></code></em>/draft/</code> </span></dt><dd><div class="para">
+ This directory contains assorted technical documents that review issues related to DNS service and propose some methods to address them.
+ </div></dd><dt><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code><version-number></code></em>/misc/</code> </span></dt><dd><div class="para">
+ This directory contains documents 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><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code><version-number></code></em>/rfc/</code> </span></dt><dd><div class="para">
+ This directory provides every RFC document related to BIND.
+ </div></dd></dl></div><div class="para">
+ There are also a number of man pages for the various applications and configuration files involved with BIND. The following lists some of the more important man pages.
+ </div><div class="variablelist"><dl><dt><span class="term">Administrative Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man rndc</code> — Explains the different options available when using the <code class="command">rndc</code> command to control a BIND nameserver.
+ </div></li></ul></div></dd><dt><span class="term">Server Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man named</code> — Explores assorted arguments that can be used to control the BIND nameserver daemon.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man lwresd</code> — Describes the purpose of and options available for the lightweight resolver daemon.
+ </div></li></ul></div></dd><dt><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man named.conf</code> — A comprehensive list of options available within the <code class="command">named</code> configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man rndc.conf</code> — A comprehensive list of options available within the <code class="command">rndc</code> configuration file.
+ </div></li></ul></div></dd></dl></div></div><div class="section" title="7.7.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">7.7.2. Useful Websites</h3></div></div></div><a id="id669934" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.isc.org/index.pl?/sw/bind/">http://www.isc.org/index.pl?/sw/bind/</a> — 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></li><li class="listitem"><div class="para">
+ <a href="http://www.redhat.com/mirrors/LDP/HOWTO/DNS-HOWTO.html">http://www.redhat.com/mirrors/LDP/HOWTO/DNS-HOWTO.html</a> — Covers the use of BIND as a resolving, caching nameserver and the configuration of various zone files necessary to serve as the primary nameserver for a domain.
+ </div></li></ul></div></div><div class="section" title="7.7.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">7.7.3. Related Books</h3></div></div></div><a id="id774224" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">DNS and BIND</em> by Paul Albitz and Cricket Liu; O'Reilly & Associates — A popular reference that explains both common and esoteric BIND configuration options, as well as providing strategies for securing a DNS server.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">The Concise Guide to DNS and BIND</em> by Nicolai Langfeldt; Que — Looks at the connection between multiple network services and BIND, with an emphasis on task-oriented, technical topics.
+ </div></li></ul></div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id858805" href="#id858805" class="para">3</a>] </sup>
+ The security update was <a href="https://rhn.redhat.com/errata/RHSA-2008-0533.html">RHSA-2008:0533</a>.
+ </p></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 8. OpenSSH" id="ch-OpenSSH" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. OpenSSH</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-ssh-protocol">8.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">8.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">8.1.2. Main Features</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">8.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">8.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-configuration">8.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">8.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-ssh-configur
ation-sshd">8.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">8.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">8.2.4. Using a Key-Based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">8.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-ssh">8.3.1. Using the <code class="command">ssh</code> Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">8.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-sftp">8.3.3. Using the <code class="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">8.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">8.4.1
. X11 Forwarding</a></span></dt><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">8.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">8.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-openssh-installed-docs">8.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-openssh-useful-websites">8.5.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id1691150" 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="8.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">8.1. The SSH Protocol</h2></div></div></div><div class="section" title="8.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">8.1.1. Why Use SSH?</h3></div></div></div><a id="id931219" 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><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><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="8.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">8.1.2. Main Features</h3></div></div></div><a id="id869815" class="indexterm"></a><a id="id869827" class="indexterm"></a><div class="para">
+ The SSH protocol provides the following safeguards:
+ </div><div class="variablelist"><dl><dt><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><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><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><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><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><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><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="8.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">8.1.3. Protocol Versions</h3></div></div></div><a id="id754049" class="indexterm"></a><a id="id754061" 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"><h2>Important: Avoid Using SSH Version 1</h2><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 class="section" title="8.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">8.1.4. Event Sequence of an SSH Connection</h3></div></div></div><a id="id1984780" 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="8.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">8.1.4.1. Transport Layer</h4></div></div></div><a id="id909631" 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"><h2>Caution</h2><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 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="8.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">8.1.4.2. Authentication</h4></div></div></div><a id="id1127724" 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="8.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">8.1.4.3. Channels</h4></div></div></div><a id="id881186" 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="id780071" href="#ftn.id780071" class="footnote">4</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="8.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">8.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="8.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">8.2.1. Configuration Files</h3></div></div></div><a id="id999456" 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="id771269" 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 8.1. System-wide configuration files">Table 8.1, “System-wide configuration files”</a> for a description of its content.
+ </div><div class="table" title="Table 8.1. System-wide configuration files" id="table-ssh-configuration-configs-system"><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><h6>Table 8.1. System-wide configuration files</h6></div><br class="table-break" /><a id="id619159" 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 8.2. User-specific configuration files">Table 8.2, “User-specific configuration files”</a> for a description of its content.
+ </div><div class="table" title="Table 8.2. User-specific configuration files" id="table-ssh-configuration-configs-user"><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><h6>Table 8.2. User-specific configuration files</h6></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="8.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">8.2.2. Starting an OpenSSH Server</h3></div></div></div><a id="id1024508" class="indexterm"></a><div class="note"><h2>Note: Make Sure You Have Relevant Packages Installed</h2><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><a id="id806657" 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="id761388" 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 6. Controlling Access to Services">Chapter 6, <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 8.1. System-wide configuration files">Table 8.1, “System-wide configuration files”</a> for a complete list), and restore them whenever you reinstall the system.
+ </div></div><div class="section" title="8.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">8.2.3. Requiring SSH for Remote Connections</h3></div></div></div><a id="id565566" class="indexterm"></a><a id="id865235" 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 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a>.
+ </div></div><div class="section" title="8.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">8.2.4. Using a Key-Based Authentication</h3></div></div></div><a id="id561834" 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 13 uses SSH Protocol 2 and RSA keys by default (see <a class="xref" href="#s2-ssh-versions" title="8.1.3. Protocol Versions">Section 8.1.3, “Protocol Versions”</a> for more information).
+ </div><div class="important"><h2>Important: Do Not Generate Key Pairs as root</h2><div class="para">
+ If you complete the steps as root, only root will be able to use the keys.
+ </div></div><div class="note"><h2>Tip: Backup Your <code class="filename">~/.ssh/</code> Directory</h2><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 class="section" title="8.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">8.2.4.1. Generating Key Pairs</h4></div></div></div><a id="id748334" class="indexterm"></a><a id="id748346" 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="id712382" 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="id750930" class="indexterm"></a><a id="id856117" 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="id856137" 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="id980773" class="indexterm"></a><a id="id980785" 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="id748499" 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="8.2.4.2. Configuring ssh-agent">Section 8.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"><h2>Important: Never Share Your Private Key</h2><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 class="section" title="8.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">8.2.4.2. Configuring <code class="command">ssh-agent</code></h4></div></div></div><a id="id922077" class="indexterm"></a><a id="id923452" 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 8.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 8.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 left, 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="id754360" class="indexterm"></a><a id="id905229" class="indexterm"></a><div class="figure" title="Figure 8.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 8.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 8.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 8.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 8.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 8.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="8.3. OpenSSH Clients" id="s1-ssh-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ssh-clients">8.3. OpenSSH Clients</h2></div></div></div><a id="id868008" class="indexterm"></a><div class="note"><h2>Note: Make Sure You Have Relevant Packages Installed</h2><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 class="section" title="8.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">8.3.1. Using the <code class="command">ssh</code> Utility</h3></div></div></div><a id="id891431" class="indexterm"></a><a id="id891447" 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"><h2>Important</h2><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 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="8.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">8.3.2. Using the <code class="command">scp</code> Utility</h3></div></div></div><a id="id856972" class="indexterm"></a><a id="id694426" class="indexterm"></a><a id="id694446" 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="8.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">8.3.3. Using the <code class="command">sftp</code> Utility</h3></div></div></div><a id="id1127212" class="indexterm"></a><a id="id1523248" 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 8.3. A selection of available sftp commands">Table 8.3, “A selection of available <code class="command">sftp</code> commands”</a>).
+ </div><div class="table" title="Table 8.3. A selection of available sftp commands" id="table-ssh-clients-sftp"><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><h6>Table 8.3. A selection of available <code class="command">sftp</code> commands</h6></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="8.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">8.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="8.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">8.4.1. X11 Forwarding</h3></div></div></div><a id="id606940" 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="8.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">8.4.2. Port Forwarding</h3></div></div></div><a id="id767517" 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"><h2>Note: Using Reserved Port Numbers</h2><div class="para">
+ Setting up port forwarding to listen on ports below 1024 requires root level access.
+ </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"><h2>Important: A Connection Is Only as Secure as a Client System</h2><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 class="section" title="8.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">8.5. Additional Resources</h2></div></div></div><a id="id577095" class="indexterm"></a><a id="id577107" 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="8.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">8.5.1. Installed Documentation</h3></div></div></div><div class="variablelist"><dl><dt><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><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><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><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><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><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><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="8.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">8.5.2. Useful Websites</h3></div></div></div><div class="variablelist"><dl><dt><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><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><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.id780071" href="#id780071" class="para">4</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 9. Samba" id="ch-Samba" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. Samba</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#samba-rgs-overview">9.1. Introduction to Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-abilities">9.1.1. Samba Features</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-daemons">9.2. Samba Daemons and Related Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-services">9.2.1. Samba Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-connect-share">9.3. Connecting to a Samba Share</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-connect-share-cmdline">9.3.1. Command Line</a></span></dt><dt><span class="section"><a href="#s1-samba-mounting">9.3.2. Mounting the Share</a></span></dt></dl></dd><dt><
span class="section"><a href="#s1-samba-configuring">9.4. Configuring a Samba Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-configuring-gui">9.4.1. Graphical Configuration</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring-cmdline">9.4.2. Command Line Configuration</a></span></dt><dt><span class="section"><a href="#s2-samba-encrypted-passwords">9.4.3. Encrypted Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-startstop">9.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="#s1-samba-servers">9.6. Samba Server Types and the <code class="command">smb.conf</code> File</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-standalone">9.6.1. Stand-alone Server</a></span></dt><dt><span class="section"><a href="#s2-samba-domain-member">9.6.2. Domain Member Server</a></span></dt><dt><span class="section"><a href="#s2-samba-domain-controller">9.6.3. Domain Contr
oller</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-security-modes">9.7. Samba Security Modes</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-user-level">9.7.1. User-Level Security</a></span></dt><dt><span class="section"><a href="#s2-samba-share-level">9.7.2. Share-Level Security</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-account-info-dbs">9.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="#s1-samba-network-browsing">9.9. Samba Network Browsing</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-domain-browsing">9.9.1. Domain Browsing</a></span></dt><dt><span class="section"><a href="#s2-samba-wins">9.9.2. WINS (Windows Internetworking Name Server)</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-cups">9.10. Samba with CUPS Printing Support</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-cups-smb.conf">9.10.1
. Simple <code class="filename">smb.conf</code> Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-samba-programs">9.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="#s1-samba-resources">9.12. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-samba-resources-installed">9.12.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-samba-resources-published">9.12.2. Related Books</a></span></dt><dt><span class="section"><a href="#s2-samba-resources-community">9.12.3. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id901222" class="indexterm"></a><a id="id951791" class="indexterm"></a><div class="para">
+ <em class="firstterm">Samba</em> is an open source implementation of the Server Message Block (SMB) protocol. It allows the networking of Microsoft <span class="trademark">Windows</span>®, Linux, UNIX, and other operating systems together, enabling access to Windows-based file and printer shares. Samba's use of SMB allows it to appear as a Windows server to Windows clients.
+ </div><div class="section" title="9.1. Introduction to Samba" id="samba-rgs-overview"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="samba-rgs-overview">9.1. Introduction to Samba</h2></div></div></div><a id="id824518" class="indexterm"></a><div class="para">
+ The third major release of Samba, version 3.0.0, introduced numerous improvements from prior versions, including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The ability to join an Active Directory domain by means of LDAP and Kerberos
+ </div></li><li class="listitem"><div class="para">
+ Built in Unicode support for internationalization
+ </div></li><li class="listitem"><div class="para">
+ Support for Microsoft Windows XP Professional client connections to Samba servers without needing local registry hacking
+ </div></li><li class="listitem"><div class="para">
+ Two new documents developed by the Samba.org team, which include a 400+ page reference manual, and a 300+ page implementation and integration manual. For more information about these published titles, refer to <a class="xref" href="#s2-samba-resources-published" title="9.12.2. Related Books">Section 9.12.2, “Related Books”</a>.
+ </div></li></ul></div><div class="section" title="9.1.1. Samba Features" id="s2-samba-abilities"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-abilities">9.1.1. Samba Features</h3></div></div></div><a id="id642015" class="indexterm"></a><div class="para">
+ Samba is a powerful and versatile server application. Even seasoned system administrators must know its abilities and limitations before attempting installation and configuration.
+ </div><div class="para">
+ What Samba can do:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Serve directory trees and printers to Linux, UNIX, and Windows clients
+ </div></li><li class="listitem"><div class="para">
+ Assist in network browsing (with or without NetBIOS)
+ </div></li><li class="listitem"><div class="para">
+ Authenticate Windows domain logins
+ </div></li><li class="listitem"><div class="para">
+ Provide Windows Internet Name Service (WINS) name server resolution
+ </div></li><li class="listitem"><div class="para">
+ Act as a Windows <span class="trademark">NT</span>®-style Primary Domain Controller (PDC)
+ </div></li><li class="listitem"><div class="para">
+ Act as a Backup Domain Controller (BDC) for a Samba-based PDC
+ </div></li><li class="listitem"><div class="para">
+ Act as an Active Directory domain member server
+ </div></li><li class="listitem"><div class="para">
+ Join a Windows NT/2000/2003 PDC
+ </div></li></ul></div><div class="para">
+ What Samba cannot do:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Act as a BDC for a Windows PDC (and vice versa)
+ </div></li><li class="listitem"><div class="para">
+ Act as an Active Directory domain controller
+ </div></li></ul></div></div></div><div class="section" title="9.2. Samba Daemons and Related Services" id="s1-samba-daemons"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-daemons">9.2. Samba Daemons and Related Services</h2></div></div></div><a id="id1016453" class="indexterm"></a><div class="para">
+ The following is a brief introduction to the individual Samba daemons and services.
+ </div><div class="section" title="9.2.1. Samba Daemons" id="s2-samba-services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-services">9.2.1. Samba Daemons</h3></div></div></div><a id="id846937" class="indexterm"></a><div class="para">
+ Samba is comprised of three daemons (<code class="command">smbd</code>, <code class="command">nmbd</code>, and <code class="command">winbindd</code>). Two services (<code class="command">smb</code> and <code class="command">windbind</code>) control how the daemons are started, stopped, and other service-related features. Each daemon is listed in detail, as well as which specific service has control over it.
+ </div><div class="formalpara" id="s3-samba-daemon-smbd"><h5 class="formalpara"> <code class="command">smbd</code> </h5><a id="id894044" class="indexterm"></a>
+ The <code class="command">smbd</code> server daemon provides file sharing and printing services to Windows clients. In addition, it is responsible for user authentication, resource locking, and data sharing through the SMB protocol. The default ports on which the server listens for SMB traffic are TCP ports 139 and 445.
+ </div><div class="para">
+ The <code class="command">smbd</code> daemon is controlled by the <code class="command">smb</code> service.
+ </div><div class="formalpara" id="s3-samba-daemon-nmbd"><h5 class="formalpara"> <code class="command">nmbd</code> </h5><a id="id966067" class="indexterm"></a>
+ The <code class="command">nmbd</code> server daemon understands and replies to NetBIOS name service requests such as those produced by SMB/CIFS in Windows-based systems. These systems include Windows 95/98/ME, Windows NT, Windows 2000, Windows XP, and LanManager clients. It also participates in the browsing protocols that make up the Windows <span class="guilabel"><strong>Network Neighborhood</strong></span> view. The default port that the server listens to for NMB traffic is UDP port 137.
+ </div><div class="para">
+ The <code class="command">nmbd</code> daemon is controlled by the <code class="command">smb</code> service.
+ </div><div class="formalpara" id="s3-samba-daemon-winbindd"><h5 class="formalpara"> <code class="command">winbindd</code> </h5><a id="id588932" class="indexterm"></a>
+ The <code class="command">winbind</code> service resolves user and group information on a server running Windows NT 2000 or Windows Server 2003. This makes Windows user / group information understandable by UNIX platforms. This is achieved by using Microsoft RPC calls, Pluggable Authentication Modules (PAM), and the Name Service Switch (NSS). This allows Windows NT domain users to appear and operate as UNIX users on a UNIX machine. Though bundled with the Samba distribution, the <code class="command">winbind</code> service is controlled separately from the <code class="command">smb</code> service.
+ </div><div class="para">
+ The <code class="command">winbindd</code> daemon is controlled by the <code class="command">winbind</code> service and does not require the <code class="command">smb</code> service to be started in order to operate. Winbindd is also used when Samba is an Active Directory member, and may also be used on a Samba domain controller (to implement nested groups and/or interdomain trust). Because <code class="command">winbind</code> is a client-side service used to connect to Windows NT-based servers, further discussion of <code class="command">winbind</code> is beyond the scope of this manual.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ You may refer to <a class="xref" href="#s1-samba-programs" title="9.11. Samba Distribution Programs">Section 9.11, “Samba Distribution Programs”</a> for a list of utilities included in the Samba distribution.
+ </div></div></div></div><div class="section" title="9.3. Connecting to a Samba Share" id="s1-samba-connect-share"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-connect-share">9.3. Connecting to a Samba Share</h2></div></div></div><a id="id1996585" class="indexterm"></a><div class="para">
+ You can use <span class="application"><strong>Nautilus</strong></span> to view available Samba shares on your network. Select <span class="guimenu"><strong>Places</strong></span> (on the Panel) > <span class="guimenuitem"><strong>Network Servers</strong></span> to view a list of Samba workgroups on your network. You can also type <strong class="userinput"><code>smb:</code></strong> in the <span class="guilabel"><strong>File</strong></span> > <span class="guilabel"><strong>Open Location</strong></span> bar of Nautilus to view the workgroups.
+ </div><div class="para">
+ As shown in <a class="xref" href="#fig-samba-nautilus-workgroups" title="Figure 9.1. SMB Workgroups in Nautilus">Figure 9.1, “SMB Workgroups in Nautilus”</a>, an icon appears for each available SMB workgroup on the network.
+ </div><div class="figure" title="Figure 9.1. SMB Workgroups in Nautilus" id="fig-samba-nautilus-workgroups"><div class="figure-contents"><div class="mediaobject"><img src="images/samba-nautilus.png" width="444" alt="SMB Workgroups in Nautilus" /><div class="longdesc"><div class="para">
+ SMB Workgroups in Nautilus
+ </div></div></div></div><h6>Figure 9.1. SMB Workgroups in Nautilus</h6></div><br class="figure-break" /><div class="para">
+ Double-click one of the workgroup icons to view a list of computers within the workgroup.
+ </div><div class="figure" title="Figure 9.2. SMB Machines in Nautilus" id="fig-samba-nautilus-machines"><div class="figure-contents"><div class="mediaobject"><img src="images/samba-nautilus-machines.png" width="444" alt="SMB Machines in Nautilus" /><div class="longdesc"><div class="para">
+ SMB Machines in Nautilus
+ </div></div></div></div><h6>Figure 9.2. SMB Machines in Nautilus</h6></div><br class="figure-break" /><div class="para">
+ As you can see from <a class="xref" href="#fig-samba-nautilus-machines" title="Figure 9.2. SMB Machines in Nautilus">Figure 9.2, “SMB Machines in Nautilus”</a>, there is an icon for each machine within the workgroup. Double-click on an icon to view the Samba shares on the machine. If a username and password combination is required, you are prompted for them.
+ </div><div class="para">
+ Alternately, you can also specify the Samba server and sharename in the <span class="guilabel"><strong>Location:</strong></span> bar for <span class="application"><strong>Nautilus</strong></span> using the following syntax (replace <em class="replaceable"><code><servername></code></em> and <em class="replaceable"><code><sharename></code></em> with the appropriate values):
+ </div><pre class="screen">
+<code class="command">smb://<em class="replaceable"><code><servername></code></em>/<em class="replaceable"><code><sharename></code></em> </code>
+</pre><div class="section" title="9.3.1. Command Line" id="s2-samba-connect-share-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-connect-share-cmdline">9.3.1. Command Line</h3></div></div></div><a id="id921240" class="indexterm"></a><a id="id921257" class="indexterm"></a><a id="id921275" class="indexterm"></a><div class="para">
+ To query the network for Samba servers, use the <code class="command">findsmb</code> command. For each server found, it displays its IP address, NetBIOS name, workgroup name, operating system, and SMB server version.
+ </div><a id="id1937759" class="indexterm"></a><a id="id1937776" class="indexterm"></a><div class="para">
+ To connect to a Samba share from a shell prompt, type the following command:
+ </div><pre class="screen">
+<code class="command">smbclient //<em class="replaceable"><code><hostname></code></em>/<em class="replaceable"><code><sharename></code></em> -U <em class="replaceable"><code><username></code></em> </code>
+</pre><div class="para">
+ Replace <em class="replaceable"><code><hostname></code></em> with the hostname or IP address of the Samba server you want to connect to, <em class="replaceable"><code><sharename></code></em> with the name of the shared directory you want to browse, and <em class="replaceable"><code><username></code></em> with the Samba username for the system. Enter the correct password or press <span class="keycap"><strong>Enter</strong></span> if no password is required for the user.
+ </div><div class="para">
+ If you see the <code class="prompt">smb:\></code> prompt, you have successfully logged in. Once you are logged in, type <strong class="userinput"><code>help</code></strong> for a list of commands. If you wish to browse the contents of your home directory, replace <em class="replaceable"><code>sharename</code></em> with your username. If the <code class="command">-U</code> switch is not used, the username of the current user is passed to the Samba server.
+ </div><div class="para">
+ To exit <code class="command">smbclient</code>, type <strong class="userinput"><code>exit</code></strong> at the <code class="prompt">smb:\></code> prompt.
+ </div></div><div class="section" title="9.3.2. Mounting the Share" id="s1-samba-mounting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-samba-mounting">9.3.2. Mounting the Share</h3></div></div></div><a id="id956115" class="indexterm"></a><div class="para">
+ Sometimes it is useful to mount a Samba share to a directory so that the files in the directory can be treated as if they are part of the local file system.
+ </div><div class="para">
+ To mount a Samba share to a directory, create create a directory to mount it to (if it does not already exist), and execute the following command as root:
+ </div><pre class="screen">
+<code class="command">mount -t cifs -o <em class="replaceable"><code><username></code></em>,<em class="replaceable"><code><password></code></em> //<em class="replaceable"><code><servername></code></em>/<em class="replaceable"><code><sharename></code></em> <em class="replaceable"><code>/mnt/point/</code></em> </code>
+</pre><div class="para">
+ This command mounts <em class="replaceable"><code><sharename></code></em> from <em class="replaceable"><code><servername></code></em> in the local directory <em class="replaceable"><code>/mnt/point/</code></em>. For more information about mounting a samba share, refer to <code class="command">man mount.cifs</code>.
+ </div></div></div><div class="section" title="9.4. Configuring a Samba Server" id="s1-samba-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-configuring">9.4. Configuring a Samba Server</h2></div></div></div><a id="id756591" class="indexterm"></a><a id="id756604" class="indexterm"></a><div class="para">
+ The default configuration file (<code class="filename">/etc/samba/smb.conf</code>) allows users to view their home directories as a Samba share. It also shares all printers configured for the system as Samba shared printers. In other words, you can attach a printer to the system and print to it from the Windows machines on your network.
+ </div><div class="section" title="9.4.1. Graphical Configuration" id="s2-samba-configuring-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-configuring-gui">9.4.1. Graphical Configuration</h3></div></div></div><a id="id971761" class="indexterm"></a><div class="para">
+ To configure Samba using a graphical interface, use the <span class="application"><strong>Samba Server Configuration Tool</strong></span>. For command line configuration, skip to <a class="xref" href="#s2-samba-configuring-cmdline" title="9.4.2. Command Line Configuration">Section 9.4.2, “Command Line Configuration”</a>.
+ </div><div class="para">
+ The <span class="application"><strong>Samba Server Configuration Tool</strong></span> is a graphical interface for managing Samba shares, users, and basic server settings. It modifies the configuration files in the <code class="filename">/etc/samba/</code> directory. Any changes to these files not made using the application are preserved.
+ </div><div class="para">
+ To use this application, you must be running the X Window System, have root privileges, and have the <code class="filename">system-config-samba</code> RPM package installed. To start the <span class="application"><strong>Samba Server Configuration Tool</strong></span> from the desktop, go to the <span class="guimenu"><strong>System</strong></span> (on the Panel) > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>Server Settings</strong></span> > <span class="guimenuitem"><strong>Samba</strong></span> or type the command <code class="command">system-config-samba</code> at a shell prompt (for example, in an XTerm or a GNOME terminal).
+ </div><div class="figure" title="Figure 9.3. Samba Server Configuration Tool" id="fig-s-c-samba"><div class="figure-contents"><div class="mediaobject"><img src="images/s-c-samba.png" width="444" alt="Samba Server Configuration Tool" /><div class="longdesc"><div class="para">
+ <span class="application"><strong>Samba Server Configuration Tool</strong></span>
+ </div></div></div></div><h6>Figure 9.3. <span class="application">Samba Server Configuration Tool</span> </h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><div class="para">
+ The <span class="application"><strong>Samba Server Configuration Tool</strong></span> does not display shared printers or the default stanza that allows users to view their own home directories on the Samba server.
+ </div></div><div class="section" title="9.4.1.1. Configuring Server Settings" id="s3-samba-gui-server-settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-gui-server-settings">9.4.1.1. Configuring Server Settings</h4></div></div></div><a id="id656751" class="indexterm"></a><div class="para">
+ The first step in configuring a Samba server is to configure the basic settings for the server and a few security options. After starting the application, select <span class="guimenu"><strong>Preferences</strong></span> > <span class="guimenuitem"><strong>Server Settings</strong></span> from the pulldown menu. The <span class="guilabel"><strong>Basic</strong></span> tab is displayed as shown in <a class="xref" href="#fig-samba-basic" title="Figure 9.4. Configuring Basic Server Settings">Figure 9.4, “Configuring Basic Server Settings”</a>.
+ </div><div class="figure" title="Figure 9.4. Configuring Basic Server Settings" id="fig-samba-basic"><div class="figure-contents"><div class="mediaobject"><img src="images/s-c-samba-basic.png" alt="Configuring Basic Server Settings" /><div class="longdesc"><div class="para">
+ Configuring Basic Server Settings
+ </div></div></div></div><h6>Figure 9.4. Configuring Basic Server Settings</h6></div><br class="figure-break" /><div class="para">
+ On the <span class="guilabel"><strong>Basic</strong></span> tab, specify which workgroup the computer should be in as well as a brief description of the computer. They correspond to the <code class="command">workgroup</code> and <code class="command">server string</code> options in <code class="filename">smb.conf</code>.
+ </div><div class="figure" title="Figure 9.5. Configuring Security Server Settings" id="fig-samba-security"><div class="figure-contents"><div class="mediaobject"><img src="images/s-c-samba-security.png" alt="Configuring Security Server Settings" /><div class="longdesc"><div class="para">
+ Configuring Security Server Settings
+ </div></div></div></div><h6>Figure 9.5. Configuring Security Server Settings</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Security</strong></span> tab contains the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Authentication Mode</strong></span> — This corresponds to the <code class="command">security</code> option. Select one of the following types of authentication.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>ADS</strong></span> — The Samba server acts as a domain member in an Active Directory Domain (ADS) realm. For this option, Kerberos must be installed and configured on the server, and Samba must become a member of the ADS realm using the <code class="command">net</code> utility, which is part of the <code class="filename">samba-common</code> package. Refer to the <code class="command">net</code> man page for details. This option does not configure Samba to be an ADS Controller. Specify the realm of the Kerberos server in the <span class="guilabel"><strong>Kerberos Realm</strong></span> field.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ The <span class="guilabel"><strong>Kerberos Realm</strong></span> field must be supplied in all uppercase letters, such as <code class="command">EXAMPLE.COM</code>.
+ </div><div class="para">
+ Using a Samba server as a domain member in an ADS realm assumes proper configuration of Kerberos, including the <code class="filename">/etc/krb5.conf</code> file.
+ </div></div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Domain</strong></span> — The Samba server relies on a Windows NT Primary or Backup Domain Controller to verify the user. The server passes the username and password to the Controller and waits for it to return. Specify the NetBIOS name of the Primary or Backup Domain Controller in the <span class="guilabel"><strong>Authentication Server</strong></span> field.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Encrypted Passwords</strong></span> option must be set to <span class="guilabel"><strong>Yes</strong></span> if this is selected.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Server</strong></span> — The Samba server tries to verify the username and password combination by passing them to another Samba server. If it can not, the server tries to verify using the user authentication mode. Specify the NetBIOS name of the other Samba server in the <span class="guilabel"><strong>Authentication Server</strong></span> field.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Share</strong></span> — Samba users do not have to enter a username and password combination on a per Samba server basis. They are not prompted for a username and password until they try to connect to a specific shared directory from a Samba server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>User</strong></span> — (Default) Samba users must provide a valid username and password on a per Samba server basis. Select this option if you want the <span class="guilabel"><strong>Windows Username</strong></span> option to work. Refer to <a class="xref" href="#s3-samba-gui-users" title="9.4.1.2. Managing Samba Users">Section 9.4.1.2, “Managing Samba Users”</a> for details.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Encrypt Passwords</strong></span> — This option must be enabled if the clients are connecting from a system with Windows 98, Windows NT 4.0 with Service Pack 3, or other more recent versions of Microsoft Windows. The passwords are transfered between the server and the client in an encrypted format instead of as a plain-text word that can be intercepted. This corresponds to the <code class="command">encrypted passwords</code> option. Refer to <a class="xref" href="#s2-samba-encrypted-passwords" title="9.4.3. Encrypted Passwords">Section 9.4.3, “Encrypted Passwords”</a> for more information about encrypted Samba passwords.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Guest Account</strong></span> — When users or guest users log into a Samba server, they must be mapped to a valid user on the server. Select one of the existing usernames on the system to be the guest Samba account. When guests log in to the Samba server, they have the same privileges as this user. This corresponds to the <code class="command">guest account</code> option.
+ </div></li></ul></div><div class="para">
+ After clicking <span class="guibutton"><strong>OK</strong></span>, the changes are written to the configuration file and the daemon is restarted; thus, the changes take effect immediately.
+ </div></div><div class="section" title="9.4.1.2. Managing Samba Users" id="s3-samba-gui-users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-gui-users">9.4.1.2. Managing Samba Users</h4></div></div></div><a id="id745388" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Samba Server Configuration Tool</strong></span> requires that an existing user account be active on the system acting as the Samba server before a Samba user can be added. The Samba user is associated with the existing user account.
+ </div><div class="figure" title="Figure 9.6. Managing Samba Users" id="fig-samba-users"><div class="figure-contents"><div class="mediaobject"><img src="images/s-c-samba-users.png" alt="Managing Samba Users" /><div class="longdesc"><div class="para">
+ Managing Samba Users
+ </div></div></div></div><h6>Figure 9.6. Managing Samba Users</h6></div><br class="figure-break" /><div class="para">
+ To add a Samba user, select <span class="guimenu"><strong>Preferences</strong></span> > <span class="guimenuitem"><strong>Samba Users</strong></span> from the pulldown menu, and click the <span class="guibutton"><strong>Add User</strong></span> button. In the <span class="guilabel"><strong>Create New Samba User</strong></span> window select a <span class="guilabel"><strong>Unix Username</strong></span> from the list of existing users on the local system.
+ </div><div class="para">
+ If the user has a different username on a Windows machine and needs to log into the Samba server from the Windows machine, specify that Windows username in the <span class="guilabel"><strong>Windows Username</strong></span> field. The <span class="guilabel"><strong>Authentication Mode</strong></span> on the <span class="guilabel"><strong>Security</strong></span> tab of the <span class="guilabel"><strong>Server Settings</strong></span> preferences must be set to <span class="guilabel"><strong>User</strong></span> for this option to work.
+ </div><div class="para">
+ Also, configure a <span class="guilabel"><strong>Samba Password</strong></span> for the Samba User and confirm it by typing it again. Even if you opt to use encrypted passwords for Samba, it is recommended that the Samba passwords for all users are different from their system passwords.
+ </div><div class="para">
+ To edit an existing user, select the user from the list, and click <span class="guibutton"><strong>Edit User</strong></span>. To delete an existing Samba user, select the user, and click the <span class="guibutton"><strong>Delete User</strong></span> button. Deleting a Samba user does not delete the associated system user account.
+ </div><div class="para">
+ The users are modified immediately after clicking the <span class="guibutton"><strong>OK</strong></span> button.
+ </div></div><div class="section" title="9.4.1.3. Adding a Share" id="s3-samba-gui-add-share"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-gui-add-share">9.4.1.3. Adding a Share</h4></div></div></div><a id="id844473" class="indexterm"></a><div class="para">
+ To create a Samba share, click the <span class="guibutton"><strong>Add</strong></span> button from the main Samba configuration window.
+ </div><div class="figure" title="Figure 9.7. Adding a Share" id="fig-samba-add-share"><div class="figure-contents"><div class="mediaobject"><img src="images/s-c-samba-create-share.png" alt="Adding a Share" /><div class="longdesc"><div class="para">
+ Adding a Samba Share
+ </div></div></div></div><h6>Figure 9.7. Adding a Share</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Basic</strong></span> tab configures the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Directory</strong></span> — The directory to share via Samba. The directory must exist before it can be entered here.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Share name</strong></span> — The actual name of the share that is seen from remote machines. By default, it is the same value as <span class="guilabel"><strong>Directory</strong></span>, but can be configured.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Descriptions</strong></span> — A brief description of the share.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Writable</strong></span> — Enables users to read and write to the shared directory
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Visible</strong></span> — Grants read-only rights to users for the shared directory.
+ </div></li></ul></div><div class="para">
+ On the <span class="guilabel"><strong>Access</strong></span> tab, select whether to allow only specified users to access the share or whether to allow all Samba users to access the share. If you select to allow access to specific users, select the users from the list of available Samba users.
+ </div><div class="para">
+ The share is added immediately after clicking <span class="guibutton"><strong>OK</strong></span>.
+ </div></div></div><div class="section" title="9.4.2. Command Line Configuration" id="s2-samba-configuring-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-configuring-cmdline">9.4.2. Command Line Configuration</h3></div></div></div><a id="id985478" class="indexterm"></a><div class="para">
+ Samba uses <code class="filename">/etc/samba/smb.conf</code> as its configuration file. If you change this configuration file, the changes do not take effect until you restart the Samba daemon with the command <code class="command">service smb restart</code>.
+ </div><div class="para">
+ To specify the Windows workgroup and a brief description of the Samba server, edit the following lines in your <code class="filename">smb.conf</code> file:
+ </div><pre class="screen">
+workgroup = <em class="replaceable"><code>WORKGROUPNAME</code></em>
+server string = <em class="replaceable"><code>BRIEF COMMENT ABOUT SERVER</code></em>
+</pre><div class="para">
+ Replace <em class="replaceable"><code>WORKGROUPNAME</code></em> with the name of the Windows workgroup to which this machine should belong. The <em class="replaceable"><code>BRIEF COMMENT ABOUT SERVER</code></em> is optional and is used as the Windows comment about the Samba system.
+ </div><div class="para">
+ To create a Samba share directory on your Linux system, add the following section to your <code class="command">smb.conf</code> file (after modifying it to reflect your needs and your system):
+ </div><pre class="screen">
+[<em class="replaceable"><code>sharename</code></em>]
+comment = <em class="replaceable"><code>Insert a comment here</code></em>
+path = <em class="replaceable"><code>/home/share/</code></em>
+valid users = <em class="replaceable"><code>tfox carole</code></em>
+public = no
+writable = yes
+printable = no
+create mask = 0765
+</pre><div class="para">
+ The above example allows the users <code class="command">tfox</code> and <code class="command">carole</code> to read and write to the directory <code class="filename">/home/share</code>, on the Samba server, from a Samba client.
+ </div></div><div class="section" title="9.4.3. Encrypted Passwords" id="s2-samba-encrypted-passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-encrypted-passwords">9.4.3. Encrypted Passwords</h3></div></div></div><div class="para">
+ Encrypted passwords are enabled by default because it is more secure to do so. To create a user with an encrypted password, use the command <code class="command">smbpasswd -a <em class="replaceable"><code><username></code></em> </code>.
+ </div><a id="id1772529" class="indexterm"></a><a id="id1772544" class="indexterm"></a><a id="id1772558" class="indexterm"></a><a id="id739709" class="indexterm"></a><a id="id739723" class="indexterm"></a><a id="id739737" class="indexterm"></a><a id="id989282" class="indexterm"></a></div></div><div class="section" title="9.5. Starting and Stopping Samba" id="s1-samba-startstop"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-startstop">9.5. Starting and Stopping Samba</h2></div></div></div><a id="id989309" class="indexterm"></a><a id="id2395413" class="indexterm"></a><a id="id2395431" class="indexterm"></a><a id="id2395449" class="indexterm"></a><a id="id560339" class="indexterm"></a><div class="para">
+ To start a Samba server, type the following command in a shell prompt while logged in as root:
+ </div><pre class="screen">
+<code class="command">/sbin/service smb start</code>
+</pre><div class="important"><h2>Important</h2><div class="para">
+ To set up a domain member server, you must first join the domain or Active Directory using the <code class="command">net join</code> command <span class="emphasis"><em>before</em></span> starting the <code class="command">smb</code> service.
+ </div></div><div class="para">
+ To stop the server, type the following command in a shell prompt while logged in as root:
+ </div><pre class="screen">
+<code class="command">/sbin/service smb stop</code>
+</pre><div class="para">
+ The <code class="option">restart</code> option is a quick way of stopping and then starting Samba. This is the most reliable way to make configuration changes take effect after editing the configuration file for Samba. Note that the restart option starts the daemon even if it was not running originally.
+ </div><div class="para">
+ To restart the server, type the following command in a shell prompt while logged in as root:
+ </div><pre class="screen">
+<code class="command"> /sbin/service smb restart </code>
+</pre><div class="para">
+ The <code class="option">condrestart</code> (<em class="firstterm">conditional restart</em>) option only starts <code class="command">smb</code> on the condition that it is currently running. This option is useful for scripts, because it does not start the daemon if it is not running.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ When the <code class="command">smb.conf</code> file is changed, Samba automatically reloads it after a few minutes. Issuing a manual <code class="command">restart</code> or <code class="command">reload</code> is just as effective.
+ </div></div><div class="para">
+ To conditionally restart the server, type the following command as root:
+ </div><pre class="screen">
+<code class="command"> /sbin/service smb condrestart </code>
+</pre><div class="para">
+ A manual reload of the <code class="command">smb.conf</code> file can be useful in case of a failed automatic reload by the <code class="command">smb</code> service. To ensure that the Samba server configuration file is reloaded without restarting the service, type the following command as root:
+ </div><pre class="screen">
+<code class="command"> /sbin/service smb reload </code>
+</pre><div class="para">
+ By default, the <code class="command">smb</code> service does <span class="emphasis"><em>not</em></span> start automatically at boot time. To configure Samba to start at boot time, use an initscript utility, such as <code class="command">/sbin/chkconfig</code>, <code class="command">/usr/sbin/ntsysv</code>, or the <span class="application"><strong>Services Configuration Tool</strong></span> program. Refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a> for more information regarding these tools.
+ </div></div><div class="section" title="9.6. Samba Server Types and the smb.conf File" id="s1-samba-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-servers">9.6. Samba Server Types and the <code class="command">smb.conf</code> File</h2></div></div></div><a id="id652179" class="indexterm"></a><a id="id652194" class="indexterm"></a><div class="para">
+ Samba configuration is straightforward. All modifications to Samba are done in the <code class="filename">/etc/samba/smb.conf</code> configuration file. Although the default <code class="filename">smb.conf</code> file is well documented, it does not address complex topics such as LDAP, Active Directory, and the numerous domain controller implementations.
+ </div><div class="para">
+ The following sections describe the different ways a Samba server can be configured. Keep in mind your needs and the changes required to the <code class="filename">smb.conf</code> file for a successful configuration.
+ </div><div class="section" title="9.6.1. Stand-alone Server" id="s2-samba-standalone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-standalone">9.6.1. Stand-alone Server</h3></div></div></div><a id="id584517" class="indexterm"></a><div class="para">
+ A stand-alone server can be a workgroup server or a member of a workgroup environment. A stand-alone server is not a domain controller and does not participate in a domain in any way. The following examples include several anonymous share-level security configurations and one user-level security configuration. For more information on share-level and user-level security modes, refer to <a class="xref" href="#s1-samba-security-modes" title="9.7. Samba Security Modes">Section 9.7, “Samba Security Modes”</a>.
+ </div><div class="section" title="9.6.1.1. Anonymous Read-Only" id="s3-samba-standalone-anonreadonly"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-standalone-anonreadonly">9.6.1.1. Anonymous Read-Only</h4></div></div></div><a id="id843385" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement anonymous read-only file sharing. The <code class="command">security = share</code> parameter makes a share anonymous. Note, security levels for a single Samba server cannot be mixed. The <code class="command">security</code> directive is a global Samba parameter located in the <code class="command">[global]</code> configuration section of the <code class="command">smb.conf</code> file.
+ </div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+[data]
+comment = Documentation Samba Server
+path = /export
+read only = Yes
+guest only = Yes
+</pre></div><div class="section" title="9.6.1.2. Anonymous Read/Write" id="s3-samba-standalone-anonreadwrite"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-standalone-anonreadwrite">9.6.1.2. Anonymous Read/Write</h4></div></div></div><a id="id582204" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement anonymous read/write file sharing. To enable anonymous read/write file sharing, set the <code class="command">read only</code> directive to <code class="command">no</code>. The <code class="command">force user</code> and <code class="command">force group</code> directives are also added to enforce the ownership of any newly placed files specified in the share.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ Although having an anonymous read/write server is possible, it is not recommended. Any files placed in the share space, regardless of user, are assigned the user/group combination as specified by a generic user (<code class="command">force user</code>) and group (<code class="command">force group</code>) in the <code class="filename">smb.conf</code> file.
+ </div></div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+[data]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+read only = No
+guest ok = Yes
+</pre></div><div class="section" title="9.6.1.3. Anonymous Print Server" id="s3-samba-standalone-anonprint"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-standalone-anonprint">9.6.1.3. Anonymous Print Server</h4></div></div></div><a id="id1004110" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement an anonymous print server. Setting <code class="command">browseable</code> to <code class="command">no</code> as shown does not list the printer in Windows <span class="guilabel"><strong>Network Neighborhood</strong></span>. Although hidden from browsing, configuring the printer explicitly is possible. By connecting to <code class="command">DOCS_SRV</code> using NetBIOS, the client can have access to the printer if the client is also part of the <code class="command">DOCS</code> workgroup. It is also assumed that the client has the correct local printer driver installed, as the <code class="command">use client driver</code> directive is set to <code class="command">Yes</code>. In this case, the Samba server has no responsibility for sharing printer drivers to the client.
+ </div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+printcap name = cups
+disable spools= Yes
+show add printer wizard = No
+printing = cups
+[printers]
+comment = All Printers
+path = /var/spool/samba
+guest ok = Yes
+printable = Yes
+use client driver = Yes
+browseable = Yes
+</pre></div><div class="section" title="9.6.1.4. Secure Read/Write File and Print Server" id="s3-samba-standalone-readwriteall"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-standalone-readwriteall">9.6.1.4. Secure Read/Write File and Print Server</h4></div></div></div><a id="id810361" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement a secure read/write print server. Setting the <code class="command">security</code> directive to <code class="command">user</code> forces Samba to authenticate client connections. Notice the <code class="command">[homes]</code> share does not have a <code class="command">force user</code> or <code class="command">force group</code> directive as the <code class="command">[public]</code> share does. The <code class="command">[homes]</code> share uses the authenticated user details for any files created as opposed to the <code class="command">force user</code> and <code class="command">force group</code> in <code class="command">[public]</code>.
+ </div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = user
+printcap name = cups
+disable spools = Yes
+show add printer wizard = No
+printing = cups
+[homes]
+comment = Home Directories
+valid users = %S
+read only = No
+browseable = No
+[public]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+guest ok = Yes
+[printers]
+comment = All Printers
+path = /var/spool/samba
+printer admin = john, ed, @admins
+create mask = 0600
+guest ok = Yes
+printable = Yes
+use client driver = Yes
+browseable = Yes
+</pre></div></div><div class="section" title="9.6.2. Domain Member Server" id="s2-samba-domain-member"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-domain-member">9.6.2. Domain Member Server</h3></div></div></div><a id="id1226138" class="indexterm"></a><div class="para">
+ A domain member, while similar to a stand-alone server, is logged into a domain controller (either Windows or Samba) and is subject to the domain's security rules. An example of a domain member server would be a departmental server running Samba that has a machine account on the Primary Domain Controller (PDC). All of the department's clients still authenticate with the PDC, and desktop profiles and all network policy files are included. The difference is that the departmental server has the ability to control printer and network shares.
+ </div><div class="section" title="9.6.2.1. Active Directory Domain Member Server" id="s3-samba-domain-member-ads"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-domain-member-ads">9.6.2.1. Active Directory Domain Member Server</h4></div></div></div><a id="id761994" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement an Active Directory domain member server. In this example, Samba authenticates users for services being run locally but is also a client of the Active Directory. Ensure that your kerberos <code class="command">realm</code> parameter is shown in all caps (for example <code class="command">realm = EXAMPLE.COM</code>). Since Windows 2000/2003 requires Kerberos for Active Directory authentication, the <code class="command">realm</code> directive is required. If Active Directory and Kerberos are running on different servers, the <code class="command">password server</code> directive may be required to help the distinction.
+ </div><pre class="screen">
+[global]
+realm = EXAMPLE.COM
+security = ADS
+encrypt passwords = yes
+# Optional. Use only if Samba cannot determine the Kerberos server automatically.
+password server = kerberos.example.com
+</pre><div class="para">
+ In order to join a member server to an Active Directory domain, the following steps must be completed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Configuration of the <code class="filename">smb.conf</code> file on the member server
+ </div></li><li class="listitem"><div class="para">
+ Configuration of Kerberos, including the <code class="filename">/etc/krb5.conf</code> file, on the member server
+ </div></li><li class="listitem"><div class="para">
+ Creation of the machine account on the Active Directory domain server
+ </div></li><li class="listitem"><div class="para">
+ Association of the member server to the Active Directory domain
+ </div></li></ul></div><div class="para">
+ To create the machine account and join the Windows 2000/2003 Active Directory, Kerberos must first be initialized for the member server wishing to join the Active Directory domain. To create an administrative Kerberos ticket, type the following command as root on the member server:
+ </div><pre class="screen">
+<strong class="userinput"><code>kinit administrator at EXAMPLE.COM</code></strong></pre><div class="para">
+ The <code class="command">kinit</code> command is a Kerberos initialization script that references the Active Directory administrator account and Kerberos realm. Since Active Directory requires Kerberos tickets, <code class="command">kinit</code> obtains and caches a Kerberos ticket-granting ticket for client/server authentication. For more information on Kerberos, the <code class="command">/etc/krb5.conf</code> file, and the <code class="command">kinit</code> command, refer to .
+ </div><div class="para">
+ To join an Active Directory server (windows1.example.com), type the following command as root on the member server:
+ </div><pre class="screen">
+<strong class="userinput"><code>net ads join -S windows1.example.com -U administrator%password</code></strong></pre><div class="para">
+ Since the machine <code class="command">windows1</code> was automatically found in the corresponding Kerberos realm (the <code class="command">kinit</code> command succeeded), the <code class="command">net</code> command connects to the Active Directory server using its required administrator account and password. This creates the appropriate machine account on the Active Directory and grants permissions to the Samba domain member server to join the domain.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ Since <code class="command">security = ads</code> and not <code class="command">security = user</code> is used, a local password backend such as <code class="filename">smbpasswd</code> is not needed. Older clients that do not support <code class="command">security = ads</code> are authenticated as if <code class="command">security = domain</code> had been set. This change does not affect functionality and allows local users not previously in the domain.
+ </div></div></div><div class="section" title="9.6.2.2. Windows NT4-based Domain Member Server" id="s3-samba-domain-member-nt4"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-domain-member-nt4">9.6.2.2. Windows NT4-based Domain Member Server</h4></div></div></div><a id="id1009984" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement a Windows NT4-based domain member server. Becoming a member server of an NT4-based domain is similar to connecting to an Active Directory. The main difference is NT4-based domains do not use Kerberos in their authentication method, making the <code class="command">smb.conf</code> file simpler. In this instance, the Samba member server functions as a pass through to the NT4-based domain server.
+ </div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = domain
+[homes]
+comment = Home Directories
+valid users = %S
+read only = No
+browseable = No
+[public]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+guest ok = Yes
+</pre><div class="para">
+ Having Samba as a domain member server can be useful in many situations. There are times where the Samba server can have other uses besides file and printer sharing. It may be beneficial to make Samba a domain member server in instances where Linux-only applications are required for use in the domain environment. Administrators appreciate keeping track of all machines in the domain, even if not Windows-based. In the event the Windows-based server hardware is deprecated, it is quite easy to modify the <code class="command">smb.conf</code> file to convert the server to a Samba-based PDC. If Windows NT-based servers are upgraded to Windows 2000/2003, the <code class="command">smb.conf</code> file is easily modifiable to incorporate the infrastructure change to Active Directory if needed.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ After configuring the <code class="command">smb.conf</code> file, join the domain <span class="emphasis"><em>before</em></span> starting Samba by typing the following command as root:
+ </div><pre class="screen">
+<strong class="userinput"><code>net rpc join -U administrator%password</code></strong></pre></div><div class="para">
+ Note that the <code class="option">-S</code> option, which specifies the domain server hostname, does not need to be stated in the <code class="command">net rpc join</code> command. Samba uses the hostname specified by the <code class="command">workgroup</code> directive in the <code class="filename">smb.conf</code> file instead of it being stated explicitly.
+ </div></div></div><div class="section" title="9.6.3. Domain Controller" id="s2-samba-domain-controller"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-domain-controller">9.6.3. Domain Controller</h3></div></div></div><a id="id900416" class="indexterm"></a><div class="para">
+ A domain controller in Windows NT is functionally similar to a Network Information Service (NIS) server in a Linux environment. Domain controllers and NIS servers both host user/group information databases as well as related services. Domain controllers are mainly used for security, including the authentication of users accessing domain resources. The service that maintains the user/group database integrity is called the <em class="firstterm">Security Account Manager</em> (SAM). The SAM database is stored differently between Windows and Linux Samba-based systems, therefore SAM replication cannot be achieved and platforms cannot be mixed in a PDC/BDC environment.
+ </div><div class="para">
+ In a Samba environment, there can be only one PDC and zero or more BDCs.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Samba cannot exist in a mixed Samba/Windows domain controller environment (Samba cannot be a BDC of a Windows PDC or vice versa). Alternatively, Samba PDCs and BDCs <span class="emphasis"><em>can</em></span> coexist.
+ </div></div><div class="section" title="9.6.3.1. Primary Domain Controller (PDC) using tdbsam" id="s3-samba-pdc-tdbsam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-pdc-tdbsam">9.6.3.1. Primary Domain Controller (PDC) using <code class="command">tdbsam</code> </h4></div></div></div><a id="id964433" class="indexterm"></a><div class="para">
+ The simplest and most common implementation of a Samba PDC uses the <code class="command">tdbsam</code> password database backend. Planned to replace the aging <code class="command">smbpasswd</code> backend, <code class="command">tdbsam</code> has numerous improvements that are explained in more detail in <a class="xref" href="#s1-samba-account-info-dbs" title="9.8. Samba Account Information Databases">Section 9.8, “Samba Account Information Databases”</a>. The <code class="command">passdb backend</code> directive controls which backend is to be used for the PDC.
+ </div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+passdb backend = tdbsam
+security = user
+add user script = /usr/sbin/useradd -m %u
+delete user script = /usr/sbin/userdel -r %u
+add group script = /usr/sbin/groupadd %g
+delete group script = /usr/sbin/groupdel %g
+add user to group script = /usr/sbin/usermod -G %g %u
+add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null -g machines %u
+# The following specifies the default logon script
+# Per user logon scripts can be specified in the user
+# account using pdbedit logon script = logon.bat
+# This sets the default profile path.
+# Set per user paths with pdbedit
+logon drive = H:
+domain logons = Yes
+os level = 35
+preferred master = Yes
+domain master = Yes
+[homes]
+ comment = Home Directories
+ valid users = %S
+ read only = No
+[netlogon]
+ comment = Network Logon Service
+ path = /var/lib/samba/netlogon/scripts
+ browseable = No
+ read only = No
+# For profiles to work, create a user directory under the
+# path shown.
+<code class="command">mkdir -p /var/lib/samba/profiles/john</code>
+[Profiles]
+ comment = Roaming Profile Share
+ path = /var/lib/samba/profiles
+ read only = No
+ browseable = No
+ guest ok = Yes
+ profile acls = Yes
+# Other resource shares ... ...
+</pre><div class="note"><h2>Note</h2><div class="para">
+ If you need more than one domain controller or have more than 250 users, do <span class="emphasis"><em>not</em></span> use a <code class="command">tdbsam</code> authentication backend. LDAP is recommended in these cases.
+ </div></div></div><div class="section" title="9.6.3.2. Primary Domain Controller (PDC) with Active Directory" id="samba-rgs-pdc-ads"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="samba-rgs-pdc-ads">9.6.3.2. Primary Domain Controller (PDC) with Active Directory</h4></div></div></div><a id="id781730" class="indexterm"></a><div class="para">
+ Although it is possible for Samba to be a member of an Active Directory, it is not possible for Samba to operate as an Active Directory domain controller.
+ </div></div></div></div><div class="section" title="9.7. Samba Security Modes" id="s1-samba-security-modes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-security-modes">9.7. Samba Security Modes</h2></div></div></div><a id="id646489" class="indexterm"></a><div class="para">
+ There are only two types of security modes for Samba, <span class="emphasis"><em>share-level</em></span> and <span class="emphasis"><em>user-level</em></span>, which are collectively known as <span class="emphasis"><em><em class="firstterm">security levels</em> </em></span>. Share-level security can only be implemented in one way, while user-level security can be implemented in one of four different ways. The different ways of implementing a security level are called <span class="emphasis"><em><em class="firstterm">security modes</em> </em></span>.
+ </div><div class="section" title="9.7.1. User-Level Security" id="s2-samba-user-level"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-user-level">9.7.1. User-Level Security</h3></div></div></div><a id="id785743" class="indexterm"></a><div class="para">
+ User-level security is the default setting for Samba. Even if the <code class="command">security = user</code> directive is not listed in the <code class="command">smb.conf</code> file, it is used by Samba. If the server accepts the client's username/password, the client can then mount multiple shares without specifying a password for each instance. Samba can also accept session-based username/password requests. The client maintains multiple authentication contexts by using a unique UID for each logon.
+ </div><div class="para">
+ In <code class="command">smb.conf</code>, the <code class="command">security = user</code> directive that sets user-level security is:
+ </div><pre class="screen">
+[GLOBAL]
+...
+security = user
+...
+</pre><div class="para">
+ The following sections describe other implementations of user-level security.
+ </div><div class="section" title="9.7.1.1. Domain Security Mode (User-Level Security)" id="s2-samba-domain-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-samba-domain-security-mode">9.7.1.1. Domain Security Mode (User-Level Security)</h4></div></div></div><a id="id865979" class="indexterm"></a><div class="para">
+ In domain security mode, the Samba server has a machine account (domain security trust account) and causes all authentication requests to be passed through to the domain controllers. The Samba server is made into a domain member server by using the following directives in <code class="command">smb.conf</code>:
+ </div><pre class="screen">
+[GLOBAL]
+...
+security = domain
+workgroup = MARKETING
+...
+</pre></div><div class="section" title="9.7.1.2. Active Directory Security Mode (User-Level Security)" id="s2-samba-ads-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-samba-ads-security-mode">9.7.1.2. Active Directory Security Mode (User-Level Security)</h4></div></div></div><a id="id866021" class="indexterm"></a><div class="para">
+ If you have an Active Directory environment, it is possible to join the domain as a native Active Directory member. Even if a security policy restricts the use of NT-compatible authentication protocols, the Samba server can join an ADS using Kerberos. Samba in Active Directory member mode can accept Kerberos tickets.
+ </div><div class="para">
+ In <code class="command">smb.conf</code>, the following directives make Samba an Active Directory member server:
+ </div><pre class="screen">
+[GLOBAL]
+...
+security = ADS
+realm = EXAMPLE.COM
+password server = kerberos.example.com
+...
+</pre></div><div class="section" title="9.7.1.3. Server Security Mode (User-Level Security)" id="s2-samba-server-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-samba-server-security-mode">9.7.1.3. Server Security Mode (User-Level Security)</h4></div></div></div><a id="id1191959" class="indexterm"></a><div class="para">
+ Server security mode was previously used when Samba was not capable of acting as a domain member server.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ It is highly recommended to <span class="emphasis"><em>not</em></span> use this mode since there are numerous security drawbacks.
+ </div></div><div class="para">
+ In <code class="filename">smb.conf</code>, the following directives enable Samba to operate in server security mode:
+ </div><pre class="screen">
+[GLOBAL]
+...
+encrypt passwords = Yes
+security = server
+password server = "NetBIOS_of_Domain_Controller"
+...
+</pre></div></div><div class="section" title="9.7.2. Share-Level Security" id="s2-samba-share-level"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-share-level">9.7.2. Share-Level Security</h3></div></div></div><a id="id733183" class="indexterm"></a><div class="para">
+ With share-level security, the server accepts only a password without an explicit username from the client. The server expects a password for each share, independent of the username. There have been recent reports that Microsoft Windows clients have compatibility issues with share-level security servers. Samba developers strongly discourage use of share-level security.
+ </div><div class="para">
+ In <code class="filename">smb.conf</code>, the <code class="command">security = share</code> directive that sets share-level security is:
+ </div><pre class="screen">
+[GLOBAL]
+...
+security = share
+...
+</pre></div></div><div class="section" title="9.8. Samba Account Information Databases" id="s1-samba-account-info-dbs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-account-info-dbs">9.8. Samba Account Information Databases</h2></div></div></div><a id="id1193884" class="indexterm"></a><div class="para">
+ The latest release of Samba offers many new features including new password database backends not previously available. Samba version 3.0.0 fully supports all databases used in previous versions of Samba. However, although supported, many backends may not be suitable for production use.
+ </div><div class="para">
+ The following is a list different backends you can use with Samba. Other backends not listed here may also be available.
+ </div><a id="id1193914" class="indexterm"></a><a id="id998639" class="indexterm"></a><a id="id998657" class="indexterm"></a><a id="id998680" class="indexterm"></a><a id="id851917" class="indexterm"></a><a id="id851931" class="indexterm"></a><a id="id851954" class="indexterm"></a><a id="id930687" class="indexterm"></a><a id="id930709" class="indexterm"></a><div class="variablelist"><dl><dt><span class="term">Plain Text</span></dt><dd><div class="para">
+ Plain text backends are nothing more than the <code class="command">/etc/passwd</code> type backends. With a plain text backend, all usernames and passwords are sent unencrypted between the client and the Samba server. This method is very unsecure and is not recommended for use by any means. It is possible that different Windows clients connecting to the Samba server with plain text passwords cannot support such an authentication method.
+ </div></dd><dt><span class="term"> <code class="command">smbpasswd</code> </span></dt><dd><div class="para">
+ A popular backend used in previous Samba packages, the <code class="command">smbpasswd</code> backend utilizes a plain ASCII text layout that includes the MS Windows LanMan and NT account, and encrypted password information. The <code class="command">smbpasswd</code> backend lacks the storage of the Windows NT/2000/2003 SAM extended controls. The <code class="command">smbpasswd</code> backend is not recommended because it does not scale well or hold any Windows information, such as RIDs for NT-based groups. The <code class="command">tdbsam</code> backend solves these issues for use in a smaller database (250 users), but is still not an enterprise-class solution.
+ </div></dd><dt><span class="term"> <code class="command">ldapsam_compat</code> </span></dt><dd><div class="para">
+ The <code class="command">ldapsam_compat</code> backend allows continued OpenLDAP support for use with upgraded versions of Samba. This option normally used when migrating to Samba 3.0.
+ </div></dd><dt><span class="term"> <code class="command">tdbsam</code> </span></dt><dd><div class="para">
+ The <code class="command">tdbsam</code> backend provides an ideal database backend for local servers, servers that do not need built-in database replication, and servers that do not require the scalability or complexity of LDAP. The <code class="command">tdbsam</code> backend includes all of the <code class="command">smbpasswd</code> database information as well as the previously-excluded SAM information. The inclusion of the extended SAM data allows Samba to implement the same account and system access controls as seen with Windows NT/2000/2003-based systems.
+ </div><div class="para">
+ The <code class="command">tdbsam</code> backend is recommended for 250 users at most. Larger organizations should require Active Directory or LDAP integration due to scalability and possible network infrastructure concerns.
+ </div></dd><dt><span class="term"> <code class="command">ldapsam</code> </span></dt><dd><div class="para">
+ The <code class="command">ldapsam</code> backend provides an optimal distributed account installation method for Samba. LDAP is optimal because of its ability to replicate its database to any number of servers using the OpenLDAP <code class="command">slurpd</code> daemon. LDAP databases are light-weight and scalable, and as such are preferred by large enterprises.
+ </div><div class="para">
+ If you are upgrading from a previous version of Samba to 3.0, note that the <code class="filename">/usr/share/doc/samba-<em class="replaceable"><code><version></code></em>/LDAP/samba.schema</code> has changed. This file contains the <em class="firstterm">attribute syntax definitions</em> and <em class="firstterm">objectclass definitions</em> that the <code class="command">ldapsam</code> backend will need in order to function properly.
+ </div><div class="para">
+ As such, if you are using the <code class="command">ldapsam</code> backend for your Samba server, you will need to configure <code class="command">slapd</code> to include this schema file. Refer to <a class="xref" href="#s1-ldap-files-schemas" title="14.5. The /etc/openldap/schema/ Directory">Section 14.5, “The <code class="filename">/etc/openldap/schema/</code> Directory”</a> for directions on how to do this.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ You will need to have the <code class="filename">openldap-server</code> package installed if you want to use the <code class="command">ldapsam</code> backend.
+ </div></div></dd><dt><span class="term"> <code class="command">mysqlsam</code> </span></dt><dd><div class="para">
+ The <code class="command">mysqlsam</code> backend uses a MySQL-based database backend. This is useful for sites that already implement MySQL. At present, <code class="command">mysqlsam</code> is now packed in a module separate from Samba, and as such is not officially supported by Samba.
+ </div></dd></dl></div></div><div class="section" title="9.9. Samba Network Browsing" id="s1-samba-network-browsing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-network-browsing">9.9. Samba Network Browsing</h2></div></div></div><a id="id818144" class="indexterm"></a><a id="id560459" class="indexterm"></a><div class="para">
+ <em class="firstterm">Network browsing</em> enables Windows and Samba servers to appear in the Windows <span class="guilabel"><strong>Network Neighborhood</strong></span>. Inside the <span class="guilabel"><strong>Network Neighborhood</strong></span>, icons are represented as servers and if opened, the server's shares and printers that are available are displayed.
+ </div><div class="para">
+ Network browsing capabilities require NetBIOS over TCP/IP. NetBIOS-based networking uses broadcast (UDP) messaging to accomplish browse list management. Without NetBIOS and WINS as the primary method for TCP/IP hostname resolution, other methods such as static files (<code class="filename">/etc/hosts</code>) or DNS, must be used.
+ </div><div class="para">
+ A domain master browser collates the browse lists from local master browsers on all subnets so that browsing can occur between workgroups and subnets. Also, the domain master browser should preferably be the local master browser for its own subnet.
+ </div><div class="section" title="9.9.1. Domain Browsing" id="s2-samba-domain-browsing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-domain-browsing">9.9.1. Domain Browsing</h3></div></div></div><a id="id880890" class="indexterm"></a><div class="para">
+ By default, a Windows server PDC for a domain is also the domain master browser for that domain. A Samba server must <span class="emphasis"><em>not</em></span> be set up as a domain master server in this type of situation
+ </div><div class="para">
+ For subnets that do not include the Windows server PDC, a Samba server can be implemented as a local master browser. Configuring the <code class="filename">smb.conf</code> for a local master browser (or no browsing at all) in a domain controller environment is the same as workgroup configuration.
+ </div></div><div class="section" title="9.9.2. WINS (Windows Internetworking Name Server)" id="s2-samba-wins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-wins">9.9.2. WINS (Windows Internetworking Name Server)</h3></div></div></div><a id="id948956" class="indexterm"></a><a id="id1984813" class="indexterm"></a><div class="para">
+ Either a Samba server or a Windows NT server can function as a WINS server. When a WINS server is used with NetBIOS enabled, UDP unicasts can be routed which allows name resolution across networks. Without a WINS server, the UDP broadcast is limited to the local subnet and therefore cannot be routed to other subnets, workgroups, or domains. If WINS replication is necessary, do not use Samba as your primary WINS server, as Samba does not currently support WINS replication.
+ </div><div class="para">
+ In a mixed NT/2000/2003 server and Samba environment, it is recommended that you use the Microsoft WINS capabilities. In a Samba-only environment, it is recommended that you use <span class="emphasis"><em>only one</em></span> Samba server for WINS.
+ </div><div class="para">
+ The following is an example of the <code class="filename">smb.conf</code> file in which the Samba server is serving as a WINS server:
+ </div><pre class="screen">
+[global]
+wins support = Yes
+</pre><div class="note"><h2>Tip</h2><div class="para">
+ All servers (including Samba) should connect to a WINS server to resolve NetBIOS names. Without WINS, browsing only occurs on the local subnet. Furthermore, even if a domain-wide list is somehow obtained, hosts cannot be resolved for the client without WINS.
+ </div></div></div></div><div class="section" title="9.10. Samba with CUPS Printing Support" id="s1-samba-cups"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-cups">9.10. Samba with CUPS Printing Support</h2></div></div></div><a id="id1757849" class="indexterm"></a><div class="para">
+ Samba allows client machines to share printers connected to the Samba server. In addition, Samba also allows client machines to send documents built in Linux to Windows printer shares. Although there are other printing systems that function with Fedora, CUPS (Common UNIX Print System) is the recommended printing system due to its close integration with Samba.
+ </div><div class="section" title="9.10.1. Simple smb.conf Settings" id="s2-samba-cups-smb.conf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-cups-smb.conf">9.10.1. Simple <code class="filename">smb.conf</code> Settings</h3></div></div></div><a id="id925077" class="indexterm"></a><div class="para">
+ The following example shows a very basic <code class="filename">smb.conf</code> configuration for CUPS support:
+ </div><pre class="screen">
+[global]
+load printers = Yes
+printing = cups
+printcap name = cups
+[printers]
+comment = All Printers
+path = /var/spool/samba
+printer = IBMInfoP
+browseable = No
+public = Yes
+guest ok = Yes
+writable = No
+printable = Yes
+printer admin = @ntadmins
+[print$]
+comment = Printer Drivers Share
+path = /var/lib/samba/drivers
+write list = ed, john
+printer admin = ed, john
+</pre><div class="para">
+ Other printing configurations are also possible. To add additional security and privacy for printing confidential documents, users can have their own print spooler not located in a public path. If a job fails, other users would not have access to the file.
+ </div><div class="para">
+ The <code class="command">print$</code> share contains printer drivers for clients to access if not available locally. The <code class="command">print$</code> share is optional and may not be required depending on the organization.
+ </div><div class="para">
+ Setting <code class="command">browseable</code> to <code class="command">Yes</code> enables the printer to be viewed in the Windows Network Neighborhood, provided the Samba server is set up correctly in the domain/workgroup.
+ </div></div></div><div class="section" title="9.11. Samba Distribution Programs" id="s1-samba-programs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-programs">9.11. Samba Distribution Programs</h2></div></div></div><a id="id759345" class="indexterm"></a><div class="formalpara" id="s2-samba-programs-findsmb"><h5 class="formalpara"> <code class="filename">findsmb</code> </h5><a id="id759373" class="indexterm"></a><a id="id572197" class="indexterm"></a>
+ <code class="command">findsmb <em class="replaceable"><code><subnet_broadcast_address></code></em> </code>
+ </div><div class="para">
+ The <code class="command">findsmb</code> program is a Perl script which reports information about SMB-aware systems on a specific subnet. If no subnet is specified the local subnet is used. Items displayed include IP address, NetBIOS name, workgroup or domain name, operating system, and version.
+ </div><div class="para">
+ The following example shows the output of executing <code class="command">findsmb</code> as any valid user on a system:
+ </div><pre class="screen">
+<strong class="userinput"><code>findsmb</code></strong>
+IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
+------------------------------------------------------------------
+10.1.59.25 VERVE [MYGROUP] [Unix] [Samba 3.0.0-15]
+10.1.59.26 STATION22 [MYGROUP] [Unix] [Samba 3.0.2-7.FC1]
+10.1.56.45 TREK +[WORKGROUP] [Windows 5.0] [Windows 2000 LAN Manager]
+10.1.57.94 PIXEL [MYGROUP] [Unix] [Samba 3.0.0-15]
+10.1.57.137 MOBILE001 [WORKGROUP] [Windows 5.0] [Windows 2000 LAN Manager]
+10.1.57.141 JAWS +[KWIKIMART] [Unix] [Samba 2.2.7a-security-rollup-fix]
+10.1.56.159 FRED +[MYGROUP] [Unix] [Samba 3.0.0-14.3E]
+10.1.59.192 LEGION *[MYGROUP] [Unix] [Samba 2.2.7-security-rollup-fix]
+10.1.56.205 NANCYN +[MYGROUP] [Unix] [Samba 2.2.7a-security-rollup-fix]
+</pre><div class="formalpara" id="s2-samba-programs-net"><h5 class="formalpara"> <code class="filename">net</code> </h5><a id="id954428" class="indexterm"></a><a id="id762297" class="indexterm"></a>
+ <code class="command">net <em class="replaceable"><code><protocol> <function> <misc_options> <target_options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">net</code> utility is similar to the <code class="command">net</code> utility used for Windows and MS-DOS. The first argument is used to specify the protocol to use when executing a command. The <code class="command"><em class="replaceable"><code><protocol></code></em> </code> option can be <code class="command">ads</code>, <code class="command">rap</code>, or <code class="command">rpc</code> for specifying the type of server connection. Active Directory uses <code class="command">ads</code>, Win9x/NT3 uses <code class="command">rap</code>, and Windows NT4/2000/2003 uses <code class="command">rpc</code>. If the protocol is omitted, <code class="command">net</code> automatically tries to determine it.
+ </div><div class="para">
+ The following example displays a list the available shares for a host named <code class="command">wakko</code>:
+ </div><pre class="screen">
+<strong class="userinput"><code>net -l share -S wakko</code></strong>
+Password:
+Enumerating shared resources (exports) on remote server:
+Share name Type Description
+---------- ---- -----------
+data Disk Wakko data share
+tmp Disk Wakko tmp share
+IPC$ IPC IPC Service (Samba Server)
+ADMIN$ IPC IPC Service (Samba Server)
+</pre><div class="para">
+ The following example displays a list of Samba users for a host named <code class="command">wakko</code>:
+ </div><pre class="screen">
+<strong class="userinput"><code>net -l user -S wakko</code></strong>
+root password:
+User name Comment
+-----------------------------
+andriusb Documentation
+joe Marketing
+lisa Sales
+</pre><div class="formalpara" id="s2-samba-programs-nmblookup"><h5 class="formalpara"> <code class="filename">nmblookup</code> </h5><a id="id600068" class="indexterm"></a><a id="id1521018" class="indexterm"></a>
+ <code class="command">nmblookup <em class="replaceable"><code><options> <netbios_name></code></em> </code>
+ </div><div class="para">
+ The <code class="command">nmblookup</code> program resolves NetBIOS names into IP addresses. The program broadcasts its query on the local subnet until the target machine replies.
+ </div><div class="para">
+ Here is an example:
+ </div><pre class="screen">
+<strong class="userinput"><code>nmblookup trek</code></strong>
+querying trek on 10.1.59.255
+10.1.56.45 trek<00>
+</pre><div class="formalpara" id="s2-samba-programs-pdbedit"><h5 class="formalpara"> <code class="filename">pdbedit</code> </h5><a id="id908483" class="indexterm"></a><a id="id908505" class="indexterm"></a>
+ <code class="command">pdbedit <em class="replaceable"><code><options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">pdbedit</code> program manages accounts located in the SAM database. All backends are supported including <code class="filename">smbpasswd</code>, LDAP, NIS+, and the <code class="filename">tdb</code> database library.
+ </div><div class="para">
+ The following are examples of adding, deleting, and listing users:
+ </div><pre class="screen">
+<strong class="userinput"><code>pdbedit -a kristin</code></strong>
+new password:
+retype new password:
+Unix username: kristin
+NT username:
+Account Flags: [U ]
+User SID: S-1-5-21-1210235352-3804200048-1474496110-2012
+Primary Group SID: S-1-5-21-1210235352-3804200048-1474496110-2077
+Full Name: Home Directory: \\wakko\kristin
+HomeDir Drive:
+Logon Script:
+Profile Path: \\wakko\kristin\profile
+Domain: WAKKO
+Account desc:
+Workstations: Munged
+dial:
+Logon time: 0
+Logoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Kickoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Password last set: Thu, 29 Jan 2004 08:29:28
+GMT Password can change: Thu, 29 Jan 2004 08:29:28 GMT
+Password must change: Mon, 18 Jan 2038 22:14:07 GMT
+<strong class="userinput"><code>pdbedit -v -L kristin</code></strong>
+Unix username: kristin
+NT username:
+Account Flags: [U ]
+User SID: S-1-5-21-1210235352-3804200048-1474496110-2012
+Primary Group SID: S-1-5-21-1210235352-3804200048-1474496110-2077
+Full Name:
+Home Directory: \\wakko\kristin
+HomeDir Drive:
+Logon Script:
+Profile Path: \\wakko\kristin\profile
+Domain: WAKKO
+Account desc:
+Workstations: Munged
+dial:
+Logon time: 0
+Logoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Kickoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Password last set: Thu, 29 Jan 2004 08:29:28 GMT
+Password can change: Thu, 29 Jan 2004 08:29:28 GMT
+Password must change: Mon, 18 Jan 2038 22:14:07 GMT
+<strong class="userinput"><code>pdbedit -L</code></strong>
+andriusb:505:
+joe:503:
+lisa:504:
+kristin:506:
+<strong class="userinput"><code>pdbedit -x joe</code></strong>
+<strong class="userinput"><code>pdbedit -L</code></strong>
+andriusb:505: lisa:504: kristin:506:
+</pre><div class="formalpara" id="s2-samba-programs-rpcclient"><h5 class="formalpara"> <code class="filename">rpcclient</code> </h5><a id="id1780220" class="indexterm"></a><a id="id596971" class="indexterm"></a>
+ <code class="command">rpcclient <em class="replaceable"><code><server> <options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">rpcclient</code> program issues administrative commands using Microsoft RPCs, which provide access to the Windows administration graphical user interfaces (GUIs) for systems management. This is most often used by advanced users that understand the full complexity of Microsoft RPCs.
+ </div><div class="formalpara" id="s2-samba-programs-smbcacls"><h5 class="formalpara"> <code class="filename">smbcacls</code> </h5><a id="id645047" class="indexterm"></a><a id="id645070" class="indexterm"></a>
+ <code class="command">smbcacls <em class="replaceable"><code><//server/share> <filename> <options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbcacls</code> program modifies Windows ACLs on files and directories shared by the Samba server.
+ </div><div class="formalpara" id="s2-samba-programs-smbclient"><h5 class="formalpara"> <code class="filename">smbclient</code> </h5><a id="id856670" class="indexterm"></a><a id="id931681" class="indexterm"></a>
+ <code class="command">smbclient <em class="replaceable"><code><//server/share> <password> <options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbclient</code> program is a versatile UNIX client which provides functionality similar to <code class="command">ftp</code>.
+ </div><div class="formalpara" id="s2-samba-programs-smbcontrol"><h5 class="formalpara"> <code class="filename">smbcontrol</code> </h5><a id="id988638" class="indexterm"></a><a id="id988660" class="indexterm"></a>
+ <code class="command">smbcontrol -i <em class="replaceable"><code><options></code></em> </code>
+ </div><div class="para">
+ <code class="command">smbcontrol <em class="replaceable"><code><options> <destination> <messagetype> <parameters></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbcontrol</code> program sends control messages to running <code class="command">smbd</code> or <code class="command">nmbd</code> daemons. Executing <code class="command">smbcontrol -i</code> runs commands interactively until a blank line or a 'q' is entered.
+ </div><div class="formalpara" id="s2-samba-programs-smbpasswd"><h5 class="formalpara"> <code class="filename">smbpasswd</code> </h5><a id="id568935" class="indexterm"></a><a id="id568958" class="indexterm"></a>
+ <code class="command">smbpasswd <em class="replaceable"><code><options> <username> <password></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbpasswd</code> program manages encrypted passwords. This program can be run by a superuser to change any user's password as well as by an ordinary user to change their own Samba password.
+ </div><div class="formalpara" id="s2-samba-programs-smbspool"><h5 class="formalpara"> <code class="filename">smbspool</code> </h5><a id="id794489" class="indexterm"></a><a id="id794510" class="indexterm"></a>
+ <code class="command">smbspool <em class="replaceable"><code><job> <user> <title> <copies> <options> <filename></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbspool</code> program is a CUPS-compatible printing interface to Samba. Although designed for use with CUPS printers, <code class="command">smbspool</code> can work with non-CUPS printers as well.
+ </div><div class="formalpara" id="s2-samba-programs-smbstatus"><h5 class="formalpara"> <code class="filename">smbstatus</code> </h5><a id="id928856" class="indexterm"></a><a id="id928879" class="indexterm"></a>
+ <code class="command">smbstatus <em class="replaceable"><code><options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbstatus</code> program displays the status of current connections to a Samba server.
+ </div><div class="formalpara" id="s2-samba-programs-smbtar"><h5 class="formalpara"> <code class="filename">smbtar</code> </h5><a id="id884891" class="indexterm"></a><a id="id872586" class="indexterm"></a>
+ <code class="command">smbtar <em class="replaceable"><code><options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbtar</code> program performs backup and restores of Windows-based share files and directories to a local tape archive. Though similar to the <code class="command">tar</code> command, the two are not compatible.
+ </div><div class="formalpara" id="s2-samba-programs-testparm"><h5 class="formalpara"> <code class="filename">testparm</code> </h5><a id="id933753" class="indexterm"></a><a id="id933776" class="indexterm"></a>
+ <code class="command">testparm <em class="replaceable"><code><options> <filename> <hostname IP_address></code></em> </code>
+ </div><div class="para">
+ The <code class="command">testparm</code> program checks the syntax of the <code class="filename">smb.conf</code> file. If your <code class="filename">smb.conf</code> file is in the default location (<code class="filename">/etc/samba/smb.conf</code>) you do not need to specify the location. Specifying the hostname and IP address to the <code class="command">testparm</code> program verifies that the <code class="filename">hosts.allow</code> and <code class="filename">host.deny</code> files are configured correctly. The <code class="command">testparm</code> program also displays a summary of your <code class="filename">smb.conf</code> file and the server's role (stand-alone, domain, etc.) after testing. This is convenient when debugging as it excludes comments and concisely presents information for experienced administrators to read.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>testparm</code></strong>
+Load smb config files from /etc/samba/smb.conf
+Processing section "[homes]"
+Processing section "[printers]"
+Processing section "[tmp]"
+Processing section "[html]"
+Loaded services file OK.
+Server role: ROLE_STANDALONE
+Press enter to see a dump of your service definitions
+<strong class="userinput"><code><enter></code></strong>
+# Global parameters
+[global]
+ workgroup = MYGROUP
+ server string = Samba Server
+ security = SHARE
+ log file = /var/log/samba/%m.log
+ max log size = 50
+ socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
+ dns proxy = No
+[homes]
+ comment = Home Directories
+ read only = No
+ browseable = No
+[printers]
+ comment = All Printers
+ path = /var/spool/samba
+ printable = Yes
+ browseable = No
+[tmp]
+ comment = Wakko tmp
+ path = /tmp
+ guest only = Yes
+[html]
+ comment = Wakko www
+ path = /var/www/html
+ force user = andriusb
+ force group = users
+ read only = No
+ guest only = Yes
+</pre><div class="formalpara" id="s2-samba-programs-wbinfo"><h5 class="formalpara"> <code class="filename">wbinfo</code> </h5><a id="id900518" class="indexterm"></a><a id="id900540" class="indexterm"></a>
+ <code class="command">wbinfo <em class="replaceable"><code><options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">wbinfo</code> program displays information from the <code class="command">winbindd</code> daemon. The <code class="command">winbindd</code> daemon must be running for <code class="command">wbinfo</code> to work.
+ </div></div><div class="section" title="9.12. Additional Resources" id="s1-samba-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-resources">9.12. Additional Resources</h2></div></div></div><a id="id947387" class="indexterm"></a><div class="para">
+ The following sections give you the means to explore Samba in greater detail.
+ </div><div class="section" title="9.12.1. Installed Documentation" id="s2-samba-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-resources-installed">9.12.1. Installed Documentation</h3></div></div></div><a id="id1989505" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/samba-<<em class="replaceable"><code>version-number</code></em>>/</code> — All additional files included with the Samba distribution. This includes all helper scripts, sample configuration files, and documentation.
+ </div><div class="para">
+ This directory also contains online versions of <em class="citetitle">The Official Samba-3 HOWTO-Collection</em> and <em class="citetitle">Samba-3 by Example</em>, both of which are cited below.
+ </div></li></ul></div></div><div class="section" title="9.12.2. Related Books" id="s2-samba-resources-published"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-resources-published">9.12.2. Related Books</h3></div></div></div><a id="id739621" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">The Official Samba-3 HOWTO-Collection</em> by John H. Terpstra and Jelmer R. Vernooij; Prentice Hall — The official Samba-3 documentation as issued by the Samba development team. This is more of a reference guide than a step-by-step guide.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Samba-3 by Example</em> by John H. Terpstra; Prentice Hall — This is another official release issued by the Samba development team which discusses detailed examples of OpenLDAP, DNS, DHCP, and printing configuration files. This has step-by-step related information that helps in real-world implementations.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Using Samba, 2nd Edition</em> by Jay T's, Robert Eckstein, and David Collier-Brown; O'Reilly — A good resource for novice to advanced users, which includes comprehensive reference material.
+ </div></li></ul></div></div><div class="section" title="9.12.3. Useful Websites" id="s2-samba-resources-community"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-resources-community">9.12.3. Useful Websites</h3></div></div></div><a id="id987195" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.samba.org/">http://www.samba.org/</a> — Homepage for the Samba distribution and all official documentation created by the Samba development team. Many resources are available in HTML and PDF formats, while others are only available for purchase. Although many of these links are not Fedora specific, some concepts may apply.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://us1.samba.org/samba/archives.html">http://samba.org/samba/archives.html </a> — Active email lists for the Samba community. Enabling digest mode is recommended due to high levels of list activity.
+ </div></li><li class="listitem"><div class="para">
+ Samba newsgroups — Samba threaded newsgroups, such as gmane.org, that use the NNTP protocol are also available. This an alternative to receiving mailing list emails.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://sourceforge.net/projects/smbldap-tools/">hhttp://sourceforge.net/projects/smbldap-tools/</a> — These are highly recommended for assisting in managing LDAP related resources. The scripts can be found at <code class="command">/usr/share/doc/samba-<em class="replaceable"><code>version_number</code></em>/LDAP/smbldap-tools</code> or can be downloaded from Sourceforge.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 10. Dynamic Host Configuration Protocol (DHCP)" id="ch-Dynamic_Host_Configuration_Protocol_DHCP" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. Dynamic Host Configuration Protocol (DHCP)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-dhcp-why">10.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-server">10.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#config-file">10.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="#lease-database">10.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="#id729711">10.2.3. Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="#dhcp-relay-agent">10.2.4. DHCP Relay Agent</a></span></dt></dl></dd><dt><span class="section"><a href="#s1
-dhcp-configuring-client">10.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="#sect-Configuring_a_Multihomed_DHCP_Server">10.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-dns_Host_Configuration">10.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">10.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="#s1-dhcp-additional-resources">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-dhcp-installed-docs">10.6.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id823674" class="indexterm"></a><a id="id715430" 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="10.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">10.1. Why Use DHCP?</h2></div></div></div><a id="id785975" 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="10.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">10.2. Configuring a DHCP Server</h2></div></div></div><a id="id837642" 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="10.2.2. Lease Database">Section 10.2.2, “Lease Database”</a> for more information.
+ </div><div class="section" title="10.2.1. Configuration File" id="config-file"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="config-file">10.2.1. Configuration File</h3></div></div></div><a id="id2393732" class="indexterm"></a><a id="id2393746" 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 mark (#) 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="id765325" 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="id770131" 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"><h2>Important</h2><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 class="note"><h2>Tip</h2><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 class="para">
+ In <a class="xref" href="#subnet" title="Example 10.1. Subnet Declaration">Example 10.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="id771078" 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 10.1. Subnet Declaration" id="subnet"><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><h6>Example 10.1. Subnet Declaration</h6></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 10.2. Range Parameter">Example 10.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 10.2. Range Parameter" id="dynamic-ip"><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><h6>Example 10.2. Range Parameter</h6></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 10.3. Static IP Address using DHCP">Example 10.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 10.3. Static IP Address using DHCP" id="static-ip"><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><h6>Example 10.3. Static IP Address using DHCP</h6></div><br class="example-break" /><a id="id575004" 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 10.4. Shared-network Declaration">Example 10.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 10.4. Shared-network Declaration" id="shared-network"><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><h6>Example 10.4. Shared-network Declaration</h6></div><br class="example-break" /><a id="id615876" class="indexterm"></a><div class="para">
+ As demonstrated in <a class="xref" href="#group" title="Example 10.5. Group Declaration">Example 10.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 10.5. Group Declaration" id="group"><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><h6>Example 10.5. Group Declaration</h6></div><br class="example-break" /><div class="note"><h2>Tip</h2><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 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="10.2.2. Lease Database" id="lease-database"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="lease-database">10.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="10.2.3. Starting and Stopping the Server"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id729711">10.2.3. Starting and Stopping the Server</h3></div></div></div><a id="id729717" class="indexterm"></a><a id="id729731" class="indexterm"></a><a id="id751694" class="indexterm"></a><a id="id751712" class="indexterm"></a><div class="important"><h2>Important</h2><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 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 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a>.
+ </div><a id="id838608" class="indexterm"></a><a id="id812152" 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="10.2.4. DHCP Relay Agent">Section 10.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="10.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">10.2.4. DHCP Relay Agent</h3></div></div></div><a id="id620355" class="indexterm"></a><a id="id620369" class="indexterm"></a><a id="id620382" 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="10.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">10.3. Configuring a DHCP Client</h2></div></div></div><a id="id569523" class="indexterm"></a><a id="id569536" 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"><h2>Tip</h2><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 class="section" title="10.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">10.4. Configuring a Multihomed DHCP Server</h2></div></div></div><a id="id1531173" 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><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><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><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><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"><h2>Alias Interfaces</h2><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 class="section" title="10.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">10.4.1. Host Configuration</h3></div></div></div><a id="id918116" 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="id1871664">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><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><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><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="id1531121">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="10.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">10.5. DHCP for IPv6 (DHCPv6)</h2></div></div></div><a id="id932884" class="indexterm"></a><a id="id932896" 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="10.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">10.6. Additional Resources</h2></div></div></div><a id="id561522" 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="10.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">10.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 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-httpd-v2">11.1. Apache HTTP Server 2.2</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-httpd-v2-features">11.1.1. Features of Apache HTTP Server 2.2</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-httpd-mig">11.2. Migrating Apache HTTP Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-httpd-v22-mig">11.2.1. Migrating Apache HTTP Server 2.0 Configuration Files</a></span></dt><dt><span class="section"><a href="#s3-httpd-v2-mig">11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-apache-startstop
">11.3. Starting and Stopping <code class="command">httpd</code> </a></span></dt><dt><span class="section"><a href="#s1-apache-config-ui">11.4. Apache HTTP Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-httpd-basic-settings">11.4.1. Basic Settings</a></span></dt><dt><span class="section"><a href="#s2-httpd-default-settings">11.4.2. Default Settings</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-apache-config">11.5. Configuration Directives in <code class="filename">httpd.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-tips">11.5.1. General Configuration Tips</a></span></dt><dt><span class="section"><a href="#s2-apache-sslcommands">11.5.2. Configuration Directives for SSL</a></span></dt><dt><span class="section"><a href="#s2-apache-mpm-containers">11.5.3. MPM Specific Server-Pool Directives</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-apache-addmods">11.6. Adding Modules<
/a></span></dt><dt><span class="section"><a href="#s1-apache-virtualhosts">11.7. Virtual Hosts</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-settingupvhosts">11.7.1. Setting Up Virtual Hosts</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-httpd-secure-server">11.8. Apache HTTP Secure Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-secureserver-optionalpackages">11.8.1. An Overview of Security-Related Packages</a></span></dt><dt><span class="section"><a href="#s2-secureserver-overview-certs">11.8.2. An Overview of Certificates and Security</a></span></dt><dt><span class="section"><a href="#s1-secureserver-oldcert">11.8.3. Using Pre-Existing Keys and Certificates</a></span></dt><dt><span class="section"><a href="#s2-secureserver-certs">11.8.4. Types of Certificates</a></span></dt><dt><span class="section"><a href="#s2-secureserver-generatingkey">11.8.5. Generating a Key</a></span></dt><dt><span class="se
ction"><a href="#s1-use-new-key">11.8.6. How to configure the server to use the new key</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-apache-additional-resources">11.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-additional-resources-web">11.9.1. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id703273" class="indexterm"></a><a id="id991452" class="indexterm"></a><div class="para">
+ The Apache HTTP Server is a robust, commercial-grade open source Web server developed by the Apache Software Foundation (<a href="http://www.apache.org/">http://www.apache.org/</a>). Fedora 13 includes the Apache HTTP Server 2.2 as well as a number of server modules designed to enhance its functionality.
+ </div><div class="para">
+ The default configuration file installed with the Apache HTTP Server works without alteration for most situations. This chapter outlines many of the directives found within its configuration file (<code class="filename">/etc/httpd/conf/httpd.conf</code>) to aid those who require a custom configuration or need to convert a configuration file from the older Apache HTTP Server 1.3 format.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ If using the graphical <span class="application"><strong>HTTP Configuration Tool</strong></span> (<span class="emphasis"><em>system-config-httpd </em></span>), <span class="emphasis"><em>do not</em></span> hand edit the Apache HTTP Server's configuration file as the <span class="application"><strong>HTTP Configuration Tool</strong></span> regenerates this file whenever it is used.
+ </div></div><div class="section" title="11.1. Apache HTTP Server 2.2" id="s1-httpd-v2"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-httpd-v2">11.1. 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.
+ </div><div class="para">
+ This section reviews some of the features of Apache HTTP Server 2.2 and outlines important changes. If you are upgrading from version 1.3, you should also read the instructions on migrating from version 1.3 to version 2.0. For instructions on migrating a version 1.3 configuration file to the 2.0 format, refer to <a class="xref" href="#s3-httpd-v2-mig" title="11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0">Section 11.2.2, “Migrating Apache HTTP Server 1.3 Configuration Files to 2.0”</a>.
+ </div><div class="section" title="11.1.1. Features of Apache HTTP Server 2.2" id="s2-httpd-v2-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-httpd-v2-features">11.1.1. Features of Apache HTTP Server 2.2</h3></div></div></div><a id="id960492" class="indexterm"></a><div class="para">
+ Apache HTTP Server 2.2 features the following improvements over version 2.0 :
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Improved caching modules (mod_cache, mod_disk_cache, mod_mem_cache).
+ </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><li class="listitem"><div class="para">
+ Support for proxy load balancing (mod_proxy_balancer)
+ </div></li><li class="listitem"><div class="para">
+ support for handling large files (namely, greater than 2GB) on 32-bit platforms
+ </div></li></ul></div><div class="para">
+ The following changes have been made to the default httpd configuration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The mod_cern_meta and mod_asis modules are no longer loaded by default.
+ </div></li><li class="listitem"><div class="para">
+ The mod_ext_filter module is now loaded by default.
+ </div></li></ul></div><div class="para">
+ If upgrading from a previous release of Fedora, the httpd configuration will need to be updated for httpd 2.2. For more information, refer to http://httpd.apache.org/docs/2.2/upgrading.html
+ </div></div></div><div class="section" title="11.2. Migrating Apache HTTP Server Configuration Files" id="s1-httpd-mig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-httpd-mig">11.2. Migrating Apache HTTP Server Configuration Files</h2></div></div></div><a id="id622044" class="indexterm"></a><a id="id622062" class="indexterm"></a><a id="id622079" class="indexterm"></a><div class="section" title="11.2.1. Migrating Apache HTTP Server 2.0 Configuration Files" id="s1-httpd-v22-mig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-httpd-v22-mig">11.2.1. Migrating Apache HTTP Server 2.0 Configuration Files</h3></div></div></div><a id="id698337" class="indexterm"></a><div class="para">
+ This section outlines migration from version 2.0 to 2.2. If you are migrating from version 1.3, please refer to <a class="xref" href="#s3-httpd-v2-mig" title="11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0">Section 11.2.2, “Migrating Apache HTTP Server 1.3 Configuration Files to 2.0”</a>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Configuration files and startup scripts from version 2.0 need minor adjustments particularly in module names which may have changed. Third party modules which worked in version 2.0 can also work in version 2.2 but need to be recompiled before you load them. Key modules that need to be noted are authentication and authorization modules. For each of the modules which has been renamed the <a href="http://httpd.apache.org/docs/2.2/mod/mod_so.html#loadmodule"><code class="command">LoadModule</code> </a> line will need to be updated.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">mod_userdir</code> module will only act on requests if you provide a <code class="command">UserDir</code> directive indicating a directory name. If you wish to maintain the procedures used in version 2.0, add the directive <code class="command">UserDir public_html</code> in your configuration file.
+ </div></li><li class="listitem"><div class="para">
+ To enable SSL, edit the <code class="filename">httpd.conf</code> file adding the necessary <code class="command">mod_ssl</code> directives. Use <code class="command">apachectl start</code> as <code class="command">apachectl startssl</code> is unavailable in version 2.2. You can view an example of SSL configuration for httpd in <code class="filename">conf/extra/httpd-ssl.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ To test your configuration it is advisable to use <code class="command">service httpd configtest</code> which will detect configuration errors.
+ </div></li></ul></div><div class="para">
+ More information on upgrading from version 2.0 to 2.2 can be found on <a href="http://httpd.apache.org/docs/2.2/upgrading.html">http://httpd.apache.org/docs/2.2/upgrading.html</a>.
+ </div></div><div class="section" title="11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0" id="s3-httpd-v2-mig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s3-httpd-v2-mig">11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</h3></div></div></div><a id="id850137" class="indexterm"></a><a id="id850154" class="indexterm"></a><a id="id850172" class="indexterm"></a><div class="para">
+ This section details migrating an Apache HTTP Server 1.3 configuration file to be utilized by Apache HTTP Server 2.0.
+ </div><div class="para">
+ If the <code class="filename">/etc/httpd/conf/httpd.conf</code> file is a modified version of the newly installed default and a saved a copy of the original configuration file is available, it may be easiest to invoke the <code class="command">diff</code> command, as in the following example (logged in as root):
+ </div><pre class="screen">
+<code class="command">diff -u httpd.conf.orig httpd.conf | less</code>
+</pre><div class="para">
+ This command highlights any modifications made. If a copy of the original file is not available, extract it from an RPM package using the <code class="command">rpm2cpio</code> and <code class="command">cpio</code> commands, as in the following example:
+ </div><pre class="screen">
+<code class="command">rpm2cpio apache-<em class="replaceable"><code><version-number></code></em>.i386.rpm | cpio -i --make</code>
+</pre><div class="para">
+ In the above command, replace <em class="replaceable"><code><version-number></code></em> with the version number for the <code class="filename">apache</code> package.
+ </div><div class="para">
+ Finally, it is useful to know that the Apache HTTP Server has a testing mode to check for configuration errors. To use access it, type the following command:
+ </div><pre class="screen">
+<code class="command">apachectl configtest</code>
+</pre><div class="section" title="11.2.2.1. Global Environment Configuration" id="s2-httpd-mig-global"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-httpd-mig-global">11.2.2.1. Global Environment Configuration</h4></div></div></div><div class="para">
+ The global environment section of the configuration file contains directives which affect the overall operation of the Apache HTTP Server, such as the number of concurrent requests it can handle and the locations of the various files. This section requires a large number of changes and should be based on the Apache HTTP Server 2.0 configuration file, while migrating the old settings into it.
+ </div><div class="section" title="11.2.2.1.1. Interface and Port Binding" id="s3-httpd-v2-mig-port"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-port">11.2.2.1.1. Interface and Port Binding</h5></div></div></div><a id="id768864" class="indexterm"></a><div class="para">
+ The <code class="command">BindAddress</code> and <code class="command">Port</code> directives no longer exist; their functionality is now provided by a more flexible <code class="command">Listen</code> directive.
+ </div><div class="para">
+ If <code class="command">Port 80</code> was set in the 1.3 version configuration file, change it to <code class="command">Listen 80</code> in the 2.0 configuration file. If <code class="command">Port</code> was set to some value <span class="emphasis"><em>other than 80</em></span>, then append the port number to the contents of the <code class="command">ServerName</code> directive.
+ </div><div class="para">
+ For example, the following is a sample Apache HTTP Server 1.3 directive:
+ </div><pre class="screen">
+<code class="command">Port 123 ServerName www.example.com</code>
+</pre><div class="para">
+ To migrate this setting to Apache HTTP Server 2.0, use the following structure:
+ </div><pre class="screen">
+<code class="command"><strong class="userinput"><code>Listen</code></strong> 123 ServerName www.example.com:<strong class="userinput"><code>123</code></strong> </code>
+</pre><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mpm_common.html#listen"> <code class="command">http://httpd.apache.org/docs-2.0/mod/mpm_common.html#listen</code> </a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/core.html#servername"> <code class="command">http://httpd.apache.org/docs-2.0/mod/core.html#servername</code> </a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.1.2. Server-Pool Size Regulation" id="s3-httpd-v2-mig-pool"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-pool">11.2.2.1.2. Server-Pool Size Regulation</h5></div></div></div><a id="id973569" class="indexterm"></a><a id="id973591" class="indexterm"></a><a id="id874599" class="indexterm"></a><a id="id874621" class="indexterm"></a><div class="para">
+ When the Apache HTTP Server accepts requests, it dispatches child processes or threads to handle them. This group of child processes or threads is known as a <em class="firstterm">server-pool</em>. Under Apache HTTP Server 2.0, the responsibility for creating and maintaining these server-pools has been abstracted to a group of modules called <em class="firstterm">Multi-Processing Modules</em> (<em class="firstterm">MPMs</em>). Unlike other modules, only one module from the MPM group can be loaded by the Apache HTTP Server. There are three MPM modules that ship with 2.0: <code class="command">prefork</code>, <code class="command">worker</code>, and <code class="command">perchild</code>. Currently only the <code class="command">prefork</code> and <code class="command">worker</code> MPMs are available, although the <code class="command">perchild</code> MPM may be available at a later date.
+ </div><div class="para">
+ The original Apache HTTP Server 1.3 behavior has been moved into the <code class="command">prefork</code> MPM. The <code class="command">prefork</code> MPM accepts the same directives as Apache HTTP Server 1.3, so the following directives may be migrated directly:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">StartServers</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MinSpareServers</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MaxSpareServers</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MaxClients</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MaxRequestsPerChild</code>
+ </div></li></ul></div><div class="para">
+ The <code class="command">worker</code> MPM implements a multi-process, multi-threaded server providing greater scalability. When using this MPM, requests are handled by threads, conserving system resources and allowing large numbers of requests to be served efficiently. Although some of the directives accepted by the <code class="command">worker</code> MPM are the same as those accepted by the <code class="command">prefork</code> MPM, the values for those directives should not be transfered directly from an Apache HTTP Server 1.3 installation. It is best to instead use the default values as a guide, then experiment to determine what values work best.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ To use the <code class="command">worker</code> MPM, create the file <code class="filename">/etc/sysconfig/httpd</code> and add the following directive:
+ </div><pre class="screen">
+<code class="command">HTTPD=/usr/sbin/httpd.worker</code>
+</pre></div><div class="para">
+ For more on the topic of MPMs, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mpm.html">http://httpd.apache.org/docs-2.0/mpm.html</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support" id="s3-httpd-v2-mig-dso"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-dso">11.2.2.1.3. Dynamic Shared Object (DSO) Support</h5></div></div></div><a id="id783076" class="indexterm"></a><div class="para">
+ There are many changes required here, and it is highly recommended that anyone trying to modify an Apache HTTP Server 1.3 configuration to suit version 2.0 (as opposed to migrating the changes into the version 2.0 configuration) copy this section from the stock Apache HTTP Server 2.0 configuration file.
+ </div><div class="para">
+ Those who do not want to copy the section from the stock Apache HTTP Server 2.0 configuration should note the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="command">AddModule</code> and <code class="command">ClearModuleList</code> directives no longer exist. These directives where used to ensure that modules could be enabled in the correct order. The Apache HTTP Server 2.0 API allows modules to specify their ordering, eliminating the need for these two directives.
+ </div></li><li class="listitem"><div class="para">
+ The order of the <code class="command">LoadModule</code> lines are no longer relevant in most cases.
+ </div></li><li class="listitem"><div class="para">
+ Many modules have been added, removed, renamed, split up, or incorporated into others.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">LoadModule</code> lines for modules packaged in their own RPMs (<code class="filename">mod_ssl</code>, <code class="filename">php</code>, <code class="filename">mod_perl</code>, and the like) are no longer necessary as they can be found in their relevant files within the <code class="filename">/etc/httpd/conf.d/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ The various <code class="command">HAVE_XXX</code> definitions are no longer defined.
+ </div></li></ul></div><div class="important"><h2>Important</h2><div class="para">
+ If modifying the original file, note that it is of paramount importance that the <code class="filename">httpd.conf</code> contains the following directive:
+ </div><pre class="screen">
+<code class="command">Include conf.d/*.conf</code>
+</pre><div class="para">
+ Omission of this directive results in the failure of all modules packaged in their own RPMs (such as <code class="filename">mod_perl</code>, <code class="filename">php</code>, and <code class="filename">mod_ssl</code>).
+ </div></div></div><div class="section" title="11.2.2.1.4. Other Global Environment Changes" id="s3-httpd-v2-mig-other"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-other">11.2.2.1.4. Other Global Environment Changes</h5></div></div></div><a id="id809602" class="indexterm"></a><div class="para">
+ The following directives have been removed from Apache HTTP Server 2.0's configuration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em> <code class="command">ServerType</code> </em></span> — The Apache HTTP Server can only be run as <code class="command">ServerType standalone</code> making this directive irrelevant.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em> <code class="command">AccessConfig</code> </em></span> and <span class="emphasis"><em><code class="command">ResourceConfig</code> </em></span> — These directives have been removed as they mirror the functionality of the <code class="command">Include</code> directive. If the <code class="command">AccessConfig</code> and <code class="command">ResourceConfig</code> directives are set, replace them with <code class="command">Include</code> directives.
+ </div><div class="para">
+ To ensure that the files are read in the order implied by the older directives, the <code class="command">Include</code> directives should be placed at the end of the <code class="filename">httpd.conf</code>, with the one corresponding to <code class="command">ResourceConfig</code> preceding the one corresponding to <code class="command">AccessConfig</code>. If using the default values, include them explicitly as <code class="filename">conf/srm.conf</code> and <code class="filename">conf/access.conf</code> files.
+ </div></li></ul></div></div></div><div class="section" title="11.2.2.2. Main Server Configuration" id="s2-httpd-v2-mig-main"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-httpd-v2-mig-main">11.2.2.2. Main Server Configuration</h4></div></div></div><div class="para">
+ The main server configuration section of the configuration file sets up the main server, which responds to any requests that are not handled by a virtual host defined within a <code class="command"><VirtualHost></code> container. Values here also provide defaults for any <code class="command"><VirtualHost></code> containers defined.
+ </div><div class="para">
+ The directives used in this section have changed little between Apache HTTP Server 1.3 and version 2.0. If the main server configuration is heavily customized, it may be easier to modify the existing configuration file to suit Apache HTTP Server 2.0. Users with only lightly customized main server sections should migrate their changes into the default 2.0 configuration.
+ </div><div class="section" title="11.2.2.2.1. UserDir Mapping" id="s3-httpd-mig-main-map"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-mig-main-map">11.2.2.2.1. <code class="command">UserDir</code> Mapping</h5></div></div></div><a id="id601075" class="indexterm"></a><div class="para">
+ The <code class="command">UserDir</code> directive is used to enable URLs such as <code class="filename">http://example.com/~bob/</code> to map to a subdirectory within the home directory of the user <code class="command">bob</code>, such as <code class="filename">/home/bob/public_html/</code>. A side-effect of this feature allows a potential attacker to determine whether a given username is present on the system. For this reason, the default configuration for Apache HTTP Server 2.0 disables this directive.
+ </div><div class="para">
+ To enable <code class="command">UserDir</code> mapping, change the directive in <code class="filename">httpd.conf</code> from:
+ </div><pre class="screen">
+<code class="command">UserDir disable</code>
+</pre><div class="para">
+ to the following:
+ </div><pre class="screen">
+<code class="command">UserDir <strong class="userinput"><code>public_html</code></strong> </code>
+</pre><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_userdir.html#userdir">http://httpd.apache.org/docs-2.0/mod/mod_userdir.html#userdir</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.2.2. Logging" id="s3-httpd-mig-main-log"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-mig-main-log">11.2.2.2.2. Logging</h5></div></div></div><a id="id737714" class="indexterm"></a><div class="para">
+ The following logging directives have been removed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">AgentLog</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">RefererLog</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">RefererIgnore</code>
+ </div></li></ul></div><div class="para">
+ However, agent and referrer logs are still available using the <code class="command">CustomLog</code> and <code class="command">LogFormat</code> directives.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#customlog">http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#customlog</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#logformat">http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#logformat</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.2.3. Directory Indexing" id="s3-httpd-mig-main-dirindex"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-mig-main-dirindex">11.2.2.2.3. Directory Indexing</h5></div></div></div><a id="id793628" class="indexterm"></a><div class="para">
+ The deprecated <code class="command">FancyIndexing</code> directive has now been removed. The same functionality is available through the <code class="command">FancyIndexing</code> <span class="emphasis"><em>option</em></span> within the <code class="command">IndexOptions</code> directive.
+ </div><div class="para">
+ The <code class="command">VersionSort</code> option to the <code class="command">IndexOptions</code> directive causes files containing version numbers to be sorted in a more natural way. For example, <code class="filename">httpd-2.0.6.tar</code> appears before <code class="filename">httpd-2.0.36.tar</code> in a directory index page.
+ </div><div class="para">
+ The defaults for the <code class="command">ReadmeName</code> and <code class="command">HeaderName</code> directives have changed from <code class="filename">README</code> and <code class="filename">HEADER</code> to <code class="filename">README.html</code> and <code class="filename">HEADER.html</code>.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#indexoptions">http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#indexoptions</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#readmename">http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#readmename</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#headername">http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#headername</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.2.4. Content Negotiation" id="s3-httpd-mig-main-cont"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-mig-main-cont">11.2.2.2.4. Content Negotiation</h5></div></div></div><a id="id983186" class="indexterm"></a><div class="para">
+ The <code class="command">CacheNegotiatedDocs</code> directive now takes the argument <code class="option">on</code> or <code class="option">off</code>. Existing instances of <code class="command">CacheNegotiatedDocs</code> should be replaced with <code class="command">CacheNegotiatedDocs on</code>.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_negotiation.html#cachenegotiateddocs">http://httpd.apache.org/docs-2.0/mod/mod_negotiation.html#cachenegotiateddocs</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.2.5. Error Documents" id="s3-httpd-mig-main-error"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-mig-main-error">11.2.2.2.5. Error Documents</h5></div></div></div><a id="id929195" class="indexterm"></a><div class="para">
+ To use a hard-coded message with the <code class="command">ErrorDocument</code> directive, the message should be enclosed in a pair of double quotation marks <code class="command">"</code>, rather than just preceded by a double quotation mark as required in Apache HTTP Server 1.3.
+ </div><div class="para">
+ For example, the following is a sample Apache HTTP Server 1.3 directive:
+ </div><pre class="screen">
+<code class="command">ErrorDocument 404 "The document was not found</code>
+</pre><div class="para">
+ To migrate an <code class="command">ErrorDocument</code> setting to Apache HTTP Server 2.0, use the following structure:
+ </div><pre class="screen">
+<code class="command">ErrorDocument 404 "The document was not found"</code>
+</pre><div class="para">
+ Note the trailing double quote in the previous <code class="command">ErrorDocument</code> directive example.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/core.html#errordocument">http://httpd.apache.org/docs-2.0/mod/core.html#errordocument</a>
+ </div></li></ul></div></div></div><div class="section" title="11.2.2.3. Virtual Host Configuration" id="s2-httpd-v2-mig-virtual"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-httpd-v2-mig-virtual">11.2.2.3. Virtual Host Configuration</h4></div></div></div><a id="id661562" class="indexterm"></a><div class="para">
+ The contents of all <code class="command"><VirtualHost></code> containers should be migrated in the same way as the main server section as described in <a class="xref" href="#s2-httpd-v2-mig-main" title="11.2.2.2. Main Server Configuration">Section 11.2.2.2, “Main Server Configuration”</a>.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Note that SSL/TLS virtual host configuration has been moved out of the main server configuration file and into <code class="filename">/etc/httpd/conf.d/ssl.conf</code>.
+ </div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/vhosts/">http://httpd.apache.org/docs-2.0/vhosts/</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4. Modules and Apache HTTP Server 2.0" id="s2-httpd-v2-mig-mod"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-httpd-v2-mig-mod">11.2.2.4. Modules and Apache HTTP Server 2.0</h4></div></div></div><a id="id611111" class="indexterm"></a><div class="para">
+ In Apache HTTP Server 2.0, the module system has been changed to allow modules to be chained together or combined in new and interesting ways. <em class="firstterm">Common Gateway Interface</em> (<em class="firstterm">CGI</em>) scripts, for example, can generate server-parsed HTML documents which can then be processed by <code class="filename">mod_include</code>. This opens up a tremendous number of possibilities with regards to how modules can be combined to achieve a specific goal.
+ </div><div class="para">
+ The way this works is that each request is served by exactly one <em class="firstterm">handler</em> module followed by zero or more <em class="firstterm">filter</em> modules.
+ </div><div class="para">
+ Under Apache HTTP Server 1.3, for example, a Perl script would be handled in its entirety by the Perl module (<code class="filename">mod_perl</code>). Under Apache HTTP Server 2.0, the request is initially <span class="emphasis"><em>handled</em></span> by the core module — which serves static files — and is then <span class="emphasis"><em>filtered</em></span> by <code class="filename">mod_perl</code>.
+ </div><div class="para">
+ Exactly how to use this, and all other new features of Apache HTTP Server 2.0, is beyond the scope of this document; however, the change has ramifications if the <code class="command">PATH_INFO</code> directive is used for a document which is handled by a module that is now implemented as a filter, as each contains trailing path information after the true file name. The core module, which initially handles the request, does not by default understand <code class="command">PATH_INFO</code> and returns <code class="computeroutput">404 Not Found</code> errors for requests that contain such information. As an alternative, use the <code class="command">AcceptPathInfo</code> directive to coerce the core module into accepting requests with <code class="command">PATH_INFO</code>.
+ </div><div class="para">
+ The following is an example of this directive:
+ </div><pre class="screen">
+<code class="command">AcceptPathInfo on</code>
+</pre><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/core.html#acceptpathinfo">http://httpd.apache.org/docs-2.0/mod/core.html#acceptpathinfo</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/handler.html">http://httpd.apache.org/docs-2.0/handler.html</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/filter.html">http://httpd.apache.org/docs-2.0/filter.html</a>
+ </div></li></ul></div><div class="section" title="11.2.2.4.1. The suexec Module" id="s3-httpd-v2-mig-mod-suexec"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-suexec">11.2.2.4.1. The <code class="filename">suexec</code> Module</h5></div></div></div><a id="id943871" class="indexterm"></a><a id="id943772" class="indexterm"></a><a id="id943791" class="indexterm"></a><div class="para">
+ In Apache HTTP Server 2.0, the <code class="filename">mod_suexec</code> module uses the <code class="filename">SuexecUserGroup</code> directive, rather than the <code class="filename">User</code> and <code class="filename">Group</code> directives, which is used for configuring virtual hosts. The <code class="filename">User</code> and <code class="filename">Group</code> directives can still be used in general, but are deprecated for configuring virtual hosts.
+ </div><div class="para">
+ For example, the following is a sample Apache HTTP Server 1.3 directive:
+ </div><pre class="screen">
+<code class="command"><VirtualHost vhost.example.com:80> User someone Group somegroup </VirtualHost></code>
+</pre><div class="para">
+ To migrate this setting to Apache HTTP Server 2.0, use the following structure:
+ </div><pre class="screen">
+<code class="command"><VirtualHost vhost.example.com:80> SuexecUserGroup someone somegroup </VirtualHost></code>
+</pre></div><div class="section" title="11.2.2.4.2. The mod_ssl Module" id="s3-httpd-v2-mig-mod-ssl"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-ssl">11.2.2.4.2. The <code class="filename">mod_ssl</code> Module</h5></div></div></div><a id="id963979" class="indexterm"></a><div class="para">
+ The configuration for <code class="filename">mod_ssl</code> has been moved from the <code class="filename">httpd.conf</code> file into the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file. For this file to be loaded, and for <code class="filename">mod_ssl</code> to work, the statement <code class="command">Include conf.d/*.conf</code> must be in the <code class="filename">httpd.conf</code> file as described in <a class="xref" href="#s3-httpd-v2-mig-dso" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support">Section 11.2.2.1.3, “Dynamic Shared Object (DSO) Support”</a>.
+ </div><div class="para">
+ <code class="command">ServerName</code> directives in SSL virtual hosts must explicitly specify the port number.
+ </div><div class="para">
+ For example, the following is a sample Apache HTTP Server 1.3 directive:
+ </div><pre class="screen">
+<code class="command"><VirtualHost _default_:443> # General setup for the virtual host ServerName ssl.example.name ... </VirtualHost></code>
+</pre><div class="para">
+ To migrate this setting to Apache HTTP Server 2.0, use the following structure:
+ </div><pre class="screen">
+<code class="command"><VirtualHost _default_:443> # General setup for the virtual host ServerName ssl.host.name<strong class="userinput"><code>:443</code></strong> ... </VirtualHost></code>
+</pre><div class="para">
+ It is also important to note that both the <code class="command">SSLLog</code> and <code class="command">SSLLogLevel</code> directives have been removed. The <code class="filename">mod_ssl</code> module now obeys the <code class="command">ErrorLog</code> and <code class="command">LogLevel</code> directives. Refer to <a class="xref" href="#s2-apache-errorlog" title="ErrorLog">ErrorLog</a> and <a class="xref" href="#s2-apache-loglevel" title="LogLevel">LogLevel</a> for more information about these directives.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_ssl.html">http://httpd.apache.org/docs-2.0/mod/mod_ssl.html</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/vhosts/">http://httpd.apache.org/docs-2.0/vhosts/</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4.3. The mod_proxy Module" id="s3-httpd-v2-mig-mod-proxy"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-proxy">11.2.2.4.3. The <code class="filename">mod_proxy</code> Module</h5></div></div></div><a id="id705323" class="indexterm"></a><div class="para">
+ Proxy access control statements are now placed inside a <code class="command"><Proxy></code> block rather than a <code class="command"><Directory proxy:></code>.
+ </div><div class="para">
+ The caching functionality of the old <code class="filename">mod_proxy</code> has been split out into the following three modules:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">mod_cache</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">mod_disk_cache</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">mod_mem_cache</code>
+ </div></li></ul></div><div class="para">
+ These generally use directives similar to the older versions of the <code class="filename">mod_proxy</code> module, but it is advisable to verify each directive before migrating any cache settings.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_proxy.html">http://httpd.apache.org/docs-2.0/mod/mod_proxy.html</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4.4. The mod_include Module" id="s3-httpd-v2-mig-mod-include"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-include">11.2.2.4.4. The <code class="filename">mod_include</code> Module</h5></div></div></div><a id="id748489" class="indexterm"></a><div class="para">
+ The <code class="filename">mod_include</code> module is now implemented as a filter and is therefore enabled differently. Refer to <a class="xref" href="#s2-httpd-v2-mig-mod" title="11.2.2.4. Modules and Apache HTTP Server 2.0">Section 11.2.2.4, “Modules and Apache HTTP Server 2.0”</a> for more about filters.
+ </div><div class="para">
+ For example, the following is a sample Apache HTTP Server 1.3 directive:
+ </div><pre class="screen">
+<code class="command">AddType text/html .shtml AddHandler server-parsed .shtml</code>
+</pre><div class="para">
+ To migrate this setting to Apache HTTP Server 2.0, use the following structure:
+ </div><pre class="screen">
+<code class="command">AddType text/html .shtml <strong class="userinput"><code>AddOutputFilter INCLUDES</code></strong> .shtml</code>
+</pre><div class="para">
+ Note that the <code class="command">Options +Includes</code> directive is still required for the <code class="command"><Directory></code> container or in a <code class="filename">.htaccess</code> file.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_include.html">http://httpd.apache.org/docs-2.0/mod/mod_include.html</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4.5. The mod_auth_dbm and mod_auth_db Modules" id="s3-httpd-v2-mig-mod-dbm"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-dbm">11.2.2.4.5. The <code class="filename">mod_auth_dbm</code> and <code class="filename">mod_auth_db</code> Modules</h5></div></div></div><a id="id600589" class="indexterm"></a><a id="id603291" class="indexterm"></a><div class="para">
+ Apache HTTP Server 1.3 supported two authentication modules, <code class="filename">mod_auth_db</code> and <code class="filename">mod_auth_dbm</code>, which used Berkeley Databases and DBM databases respectively. These modules have been combined into a single module named <code class="filename">mod_auth_dbm</code> in Apache HTTP Server 2.0, which can access several different database formats. To migrate from <code class="filename">mod_auth_db</code>, configuration files should be adjusted by replacing <code class="command">AuthDBUserFile</code> and <code class="command">AuthDBGroupFile</code> with the <code class="filename">mod_auth_dbm</code> equivalents, <code class="command">AuthDBMUserFile</code> and <code class="command">AuthDBMGroupFile</code>. Also, the directive <code class="command">AuthDBMType DB</code> must be added to indicate the type of database file in use.
+ </div><div class="para">
+ The following example shows a sample <code class="filename">mod_auth_db</code> configuration for Apache HTTP Server 1.3:
+ </div><pre class="screen">
+<code class="command"><Location /private/> AuthType Basic AuthName "My Private Files" AuthDBUserFile /var/www/authdb require valid-user </Location></code>
+</pre><div class="para">
+ To migrate this setting to version 2.0 of Apache HTTP Server, use the following structure:
+ </div><pre class="screen">
+<code class="command"><Location /private/> AuthType Basic AuthName "My Private Files" <strong class="userinput"><code>AuthDBMUserFile</code></strong> /var/www/authdb <strong class="userinput"><code>AuthDBMType DB</code></strong> require valid-user </Location></code>
+</pre><div class="para">
+ Note that the <code class="command">AuthDBMUserFile</code> directive can also be used in <code class="filename">.htaccess</code> files.
+ </div><div class="para">
+ The <code class="command">dbmmanage</code> Perl script, used to manipulate username and password databases, has been replaced by <code class="command">htdbm</code> in Apache HTTP Server 2.0. The <code class="command">htdbm</code> program offers equivalent functionality and, like <code class="filename">mod_auth_dbm</code>, can operate a variety of database formats; the <code class="option">-T</code> option can be used on the command line to specify the format to use.
+ </div><div class="para">
+ <a class="xref" href="#table-htdbm" title="Table 11.1. Migrating from dbmmanage to htdbm">Table 11.1, “Migrating from <code class="command">dbmmanage</code> to <code class="command">htdbm</code> ”</a> shows how to migrate from a DBM-format database to <code class="command">htdbm</code> format using <code class="command">dbmmanage</code>.
+ </div><div class="table" title="Table 11.1. Migrating from dbmmanage to htdbm" id="table-htdbm"><div class="table-contents"><table summary="Migrating from dbmmanage to htdbm " border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th>
+ Action
+ </th><th>
+ dbmmanage command (1.3)
+ </th><th>
+ Equivalent htdbm command (2.0)
+ </th></tr></thead><tbody><tr><td>
+ Add user to database (using given password)
+ </td><td>
+ <code class="command">dbmmanage authdb add username password</code>
+ </td><td>
+ <code class="command">htdbm -b -TDB authdb username password</code>
+ </td></tr><tr><td>
+ Add user to database (prompts for password)
+ </td><td>
+ <code class="command">dbmmanage authdb adduser username</code>
+ </td><td>
+ <code class="command">htdbm -TDB authdb username</code>
+ </td></tr><tr><td>
+ Remove user from database
+ </td><td>
+ <code class="command">dbmmanage authdb delete username</code>
+ </td><td>
+ <code class="command">htdbm -x -TDB authdb username</code>
+ </td></tr><tr><td>
+ List users in database
+ </td><td>
+ <code class="command">dbmmanage authdb view</code>
+ </td><td>
+ <code class="command">htdbm -l -TDB authdb</code>
+ </td></tr><tr><td>
+ Verify a password
+ </td><td>
+ <code class="command">dbmmanage authdb check username</code>
+ </td><td>
+ <code class="command">htdbm -v -TDB authdb username</code>
+ </td></tr></tbody></table></div><h6>Table 11.1. Migrating from <code class="command">dbmmanage</code> to <code class="command">htdbm</code> </h6></div><br class="table-break" /><div class="para">
+ The <code class="option">-m</code> and <code class="option">-s</code> options work with both <code class="command">dbmmanage</code> and <code class="command">htdbm</code>, enabling the use of the MD5 or SHA1 algorithms for hashing passwords, respectively.
+ </div><div class="para">
+ When creating a new database with <code class="command">htdbm</code>, the <code class="command">-c</code> option must be used.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_auth_dbm.html">http://httpd.apache.org/docs-2.0/mod/mod_auth_dbm.html</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4.6. The mod_perl Module" id="s3-httpd-v2-mig-mod-perl"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-perl">11.2.2.4.6. The <code class="filename">mod_perl</code> Module</h5></div></div></div><a id="id637062" class="indexterm"></a><div class="para">
+ The configuration for <code class="filename">mod_perl</code> has been moved from <code class="filename">httpd.conf</code> into the file <code class="filename">/etc/httpd/conf.d/perl.conf</code>. For this file to be loaded, and hence for <code class="filename">mod_perl</code> to work, the statement <code class="command">Include conf.d/*.conf</code> must be included in <code class="filename">httpd.conf</code> as described in <a class="xref" href="#s3-httpd-v2-mig-dso" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support">Section 11.2.2.1.3, “Dynamic Shared Object (DSO) Support”</a>.
+ </div><div class="para">
+ Occurrences of <code class="command">Apache::</code> in <code class="filename">httpd.conf</code> must be replaced with <code class="command">ModPerl::</code>. Additionally, the manner in which handlers are registered has been changed.
+ </div><div class="para">
+ This is a sample Apache HTTP Server 1.3 <code class="filename">mod_perl</code> configuration:
+ </div><pre class="screen">
+<code class="command"><Directory /var/www/perl> SetHandler perl-script PerlHandler Apache::Registry Options +ExecCGI </Directory></code>
+</pre><div class="para">
+ This is the equivalent <code class="filename">mod_perl</code> for Apache HTTP Server 2.0:
+ </div><pre class="screen">
+<code class="command"><Directory /var/www/perl> SetHandler perl-script <strong class="userinput"><code>PerlResponseHandler ModPerl::Registry</code></strong> Options +ExecCGI </Directory></code>
+</pre><div class="para">
+ Most modules for <code class="filename">mod_perl</code> 1.x should work without modification with <code class="filename">mod_perl</code> 2.x. XS modules require recompilation and may require minor Makefile modifications.
+ </div></div><div class="section" title="11.2.2.4.7. The mod_python Module" id="s3-httpd-v2-mig-mod-python"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-python">11.2.2.4.7. The <code class="filename">mod_python</code> Module</h5></div></div></div><div class="para">
+ Configuration for <code class="filename">mod_python</code> has moved from <code class="filename">httpd.conf</code> to the <code class="filename">/etc/httpd/conf.d/python.conf</code> file. For this file to be loaded, and hence for <code class="filename">mod_python</code> to work, the statement <code class="command">Include conf.d/*.conf</code> must be in <code class="filename">httpd.conf</code> as described in <a class="xref" href="#s3-httpd-v2-mig-dso" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support">Section 11.2.2.1.3, “Dynamic Shared Object (DSO) Support”</a>.
+ </div></div><div class="section" title="11.2.2.4.8. PHP" id="s3-httpd-v2-mig-mod-php"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-php">11.2.2.4.8. PHP</h5></div></div></div><a id="id1020710" class="indexterm"></a><div class="para">
+ The configuration for PHP has been moved from <code class="filename">httpd.conf</code> into the file <code class="filename">/etc/httpd/conf.d/php.conf</code>. For this file to be loaded, the statement <code class="command">Include conf.d/*.conf</code> must be in <code class="filename">httpd.conf</code> as described in <a class="xref" href="#s3-httpd-v2-mig-dso" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support">Section 11.2.2.1.3, “Dynamic Shared Object (DSO) Support”</a>.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ Any PHP configuration directives used in Apache HTTP Server 1.3 are now fully compatible, when migrating to Apache HTTP Server 2.0 on Fedora 13.
+ </div></div><div class="para">
+ In PHP version 4.2.0 and later the default set of predefined variables which are available in the global scope has changed. Individual input and server variables are, by default, no longer placed directly into the global scope. This change may cause scripts to break. Revert to the old behavior by setting <code class="command">register_globals</code> to <code class="command">On</code> in the file <code class="filename">/etc/php.ini</code>.
+ </div><div class="para">
+ For more on this topic, refer to the following URL for details concerning the global scope changes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.php.net/release_4_1_0.php">http://www.php.net/release_4_1_0.php</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4.9. The mod_authz_ldap Module" id="s3-httpd-v2-mig-mod-ldapz"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-ldapz">11.2.2.4.9. The <code class="filename">mod_authz_ldap</code> Module</h5></div></div></div><a id="id584126" class="indexterm"></a><div class="para">
+ Fedora ships with the <code class="filename">mod_authz_ldap</code> module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. The <code class="filename">mod_ssl</code> module is required when using the <code class="filename">mod_authz_ldap</code> module.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ The <code class="filename">mod_authz_ldap</code> module does not authenticate a user to an LDAP directory using an encrypted password hash. This functionality is provided by the experimental <code class="filename">mod_auth_ldap</code> module. Refer to the <code class="filename">mod_auth_ldap</code> module documentation online at <a href="http://httpd.apache.org/docs-2.0/mod/mod_auth_ldap.html">http://httpd.apache.org/docs-2.0/mod/mod_auth_ldap.html</a> for details on the status of this module.
+ </div></div><div class="para">
+ The <code class="filename">/etc/httpd/conf.d/authz_ldap.conf</code> file configures the <code class="filename">mod_authz_ldap</code> module.
+ </div><div class="para">
+ Refer to <code class="filename">/usr/share/doc/mod_authz_ldap-<em class="replaceable"><code><version></code></em>/index.html</code> (replacing <em class="replaceable"><code><version></code></em> with the version number of the package) or <a href="http://authzldap.othello.ch/">http://authzldap.othello.ch/</a> for more information on configuring the <code class="filename">mod_authz_ldap</code> third party module.
+ </div></div></div></div></div><div class="section" title="11.3. Starting and Stopping httpd" id="s1-apache-startstop"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-startstop">11.3. Starting and Stopping <code class="command">httpd</code> </h2></div></div></div><a id="id987084" class="indexterm"></a><a id="id987098" class="indexterm"></a><a id="id828457" class="indexterm"></a><a id="id828472" class="indexterm"></a><div class="para">
+ After installing the <code class="filename">httpd</code> package, review the Apache HTTP Server's documentation available online at <a href="http://httpd.apache.org/docs/2.2/">http://httpd.apache.org/docs/2.2/</a>.
+ </div><div class="para">
+ The <code class="filename">httpd</code> RPM installs the <code class="filename">/etc/init.d/httpd</code> script, which can be accessed using the <code class="command">/sbin/service</code> command.
+ </div><div class="para">
+ Starting <code class="command">httpd</code> using the <code class="command">apachectl</code> control script sets the environmental variables in <code class="filename">/etc/sysconfig/httpd</code> and starts <code class="command">httpd</code>. You can also set the environment variables using the init script.
+ </div><div class="para">
+ To start the server using the <code class="command">apachectl</code> control script as root type:
+ </div><pre class="screen">
+<code class="command">apachectl start</code>
+</pre><div class="para">
+ You can also start <code class="command">httpd</code> using <code class="command">/sbin/service httpd start</code>. This starts <code class="command">httpd</code> but does not set the environment variables. If you are using the default <code class="command">Listen</code> directive in <code class="command">httpd.conf</code>, which is port 80, you will need to have root privileges to start the apache server.
+ </div><div class="para">
+ To stop the server, as root type:
+ </div><pre class="screen">
+<code class="command">apachectl stop</code>
+</pre><div class="para">
+ You can also stop <code class="command">httpd</code> using <code class="command">/sbin/service httpd stop</code>. The <code class="option">restart</code> option is a shorthand way of stopping and then starting the Apache HTTP Server.
+ </div><div class="para">
+ You can restart the server as root by typing:
+ </div><pre class="screen">
+<code class="command">apachectl restart</code>
+or:
+<code class="command">/sbin/service httpd restart</code>
+</pre><div class="para">
+ Apache will display a message on the console or in the <code class="filename">ErrorLog</code> if it encounters an error while starting.
+ </div><div class="para">
+ By default, the <code class="command">httpd</code> service does <span class="emphasis"><em>not</em></span> start automatically at boot time. If you would wish to have Apache startup at boot time, you will need to add a call to <code class="command">apachectl</code> in your startup files within the <code class="filename">rc.N</code> directory. A typical file used is <code class="filename">rc.local</code>. As this starts Apache as root, it is recommended to properly configure your security and authentication before adding this call.
+ </div><div class="para">
+ You can also configure the <code class="command">httpd</code> service to start up at boot time, using an initscript utility, such as <code class="command">/sbin/chkconfig</code>, <span class="application"><strong>/usr/sbin/ntsysv</strong></span>, or the <span class="application"><strong>Services Configuration Tool</strong></span> program.
+ </div><div class="para">
+ You can also display the status of your httpd server by typing:
+ </div><pre class="screen">
+<code class="command">apachectl status</code>
+</pre><div class="para">
+ The status module <code class="command">mod_status</code> however needs to be enabled in your <code class="filename">httpd.conf</code> configuration file for this to work. For more details on <code class="command">mod_status</code> can be found on <a href="http://httpd.apache.org/docs/2.2/mod/mod_status.html">http://httpd.apache.org/docs/2.2/mod/mod_status.html</a>.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ If running the Apache HTTP Server as a secure server, the secure server's password is required after the machine boots when using an encrypted private SSL key.
+ </div><div class="para">
+ You can find more information on <a href="http://httpd.apache.org/docs/2.2/ssl">http://httpd.apache.org/docs/2.2/ssl</a>
+ </div></div></div><div class="section" title="11.4. Apache HTTP Server Configuration" id="s1-apache-config-ui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-config-ui">11.4. Apache HTTP Server Configuration</h2></div></div></div><a id="id2001131" class="indexterm"></a><a id="id2001145" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>HTTP Configuration Tool</strong></span> allows you to configure the <code class="filename">/etc/httpd/conf/httpd.conf</code> configuration file for the Apache HTTP Server. It does not use the old <code class="filename">srm.conf</code> or <code class="filename">access.conf</code> configuration files; leave them empty. Through the graphical interface, you can configure directives such as virtual hosts, logging attributes, and maximum number of connections. To start the HTTD Configuration Tool, click on <code class="filename">System > Administration > Server Settings > HTTP</code>.
+ </div><a id="id1002777" class="indexterm"></a><div class="para">
+ Only modules provided with Fedora can be configured with the <span class="application"><strong>HTTP Configuration Tool</strong></span>. If additional modules are installed, they can not be configured using this tool.
+ </div><div class="warning"><h2>Caution</h2><a id="id973133" class="indexterm"></a><div class="para">
+ Do not edit the <code class="filename">/etc/httpd/conf/httpd.conf</code> configuration file by hand if you wish to use this tool. The <span class="application"><strong>HTTP Configuration Tool</strong></span> generates this file after you save your changes and exit the program. If you want to add additional modules or configuration options that are not available in <span class="application"><strong>HTTP Configuration Tool</strong></span>, you cannot use this tool.
+ </div></div><div class="para">
+ The general steps for configuring the Apache HTTP Server using the <span class="application"><strong>HTTP Configuration Tool</strong></span> are as follows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Configure the basic settings under the <span class="guilabel"><strong>Main</strong></span> tab.
+ </div></li><li class="listitem"><div class="para">
+ Click on the <span class="guilabel"><strong>Virtual Hosts</strong></span> tab and configure the default settings.
+ </div></li><li class="listitem"><div class="para">
+ Under the <span class="guilabel"><strong>Virtual Hosts</strong></span> tab, configure the Default Virtual Host.
+ </div></li><li class="listitem"><div class="para">
+ To serve more than one URL or virtual host, add any additional virtual hosts.
+ </div></li><li class="listitem"><div class="para">
+ Configure the server settings under the <span class="guilabel"><strong>Server</strong></span> tab.
+ </div></li><li class="listitem"><div class="para">
+ Configure the connections settings under the <span class="guilabel"><strong>Performance Tuning</strong></span> tab.
+ </div></li><li class="listitem"><div class="para">
+ Copy all necessary files to the <code class="filename">DocumentRoot</code> and <code class="filename">cgi-bin</code> directories.
+ </div></li><li class="listitem"><div class="para">
+ Exit the application and select to save your settings.
+ </div></li></ol></div><div class="section" title="11.4.1. Basic Settings" id="s2-httpd-basic-settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-httpd-basic-settings">11.4.1. Basic Settings</h3></div></div></div><div class="para">
+ Use the <span class="guilabel"><strong>Main</strong></span> tab to configure the basic server settings.
+ </div><div class="figure" title="Figure 11.1. Basic Settings" id="httpd-main"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-main.png" alt="Basic Settings" /><div class="longdesc"><div class="para">
+ Basic Settings
+ </div></div></div></div><h6>Figure 11.1. Basic Settings</h6></div><br class="figure-break" /><a id="id586951" class="indexterm"></a><div class="para">
+ Enter a fully qualified domain name that you have the right to use in the <span class="guilabel"><strong>Server Name</strong></span> text area. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#servername"><code class="command">ServerName</code> </a> directive in <code class="filename">httpd.conf</code>. The <code class="command">ServerName</code> directive sets the hostname of the Web server. It is used when creating redirection URLs. If you do not define a server name, the Web server attempts to resolve it from the IP address of the system. The server name does not have to be the domain name resolved from the IP address of the server. For example, you might set the server name to www.example.com while the server's real DNS name is foo.example.com.
+ </div><a id="id1012413" class="indexterm"></a><div class="para">
+ Enter the email address of the person who maintains the Web server in the <span class="guilabel"><strong>Webmaster email address</strong></span> text area. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#serveradmin"><code class="command">ServerAdmin</code> </a> directive in <code class="filename">httpd.conf</code>. If you configure the server's error pages to contain an email address, this email address is used so that users can report a problem to the server's administrator. The default value is root at localhost.
+ </div><a id="id1012454" class="indexterm"></a><div class="para">
+ Use the <span class="guilabel"><strong>Available Addresses</strong></span> area to define the ports on which the server accepts incoming requests. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/mpm_common.html#listen"><code class="command">Listen</code> </a> directive in <code class="filename">httpd.conf</code>. By default, Red Hat configures the Apache HTTP Server to listen to port 80 for non-secure Web communications.
+ </div><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button to define additional ports on which to accept requests. A window as shown in <a class="xref" href="#httpd-listen" title="Figure 11.2. Available Addresses">Figure 11.2, “Available Addresses”</a> appears. Either choose the <span class="guilabel"><strong>Listen to all addresses</strong></span> option to listen to all IP addresses on the defined port or specify a particular IP address over which the server accepts connections in the <span class="guilabel"><strong>Address</strong></span> field. Only specify one IP address per port number. To specify more than one IP address with the same port number, create an entry for each IP address. If at all possible, use an IP address instead of a domain name to prevent a DNS lookup failure. Refer to <a href="http://httpd.apache.org/docs/2.2/dns-caveats.html">http://httpd.apache.org/docs/2.2/dns-caveats.html</a> for more information about <em class="citetitle">I
ssues Regarding DNS and Apache</em>.
+ </div><div class="para">
+ Entering an asterisk (*) in the <span class="guilabel"><strong>Address</strong></span> field is the same as choosing <span class="guilabel"><strong>Listen to all addresses</strong></span>. Clicking the <span class="guibutton"><strong>Edit</strong></span> button in the <span class="guilabel"><strong>Available Addresses</strong></span> frame shows the same window as the <span class="guibutton"><strong>Add</strong></span> button except with the fields populated for the selected entry. To delete an entry, select it and click the <span class="guibutton"><strong>Delete</strong></span> button.
+ </div><div class="note"><h2>Tip</h2><div class="para">
+ If you set the server to listen to a port under 1024, you must be root to start it. For port 1024 and above, <code class="command">httpd</code> can be started as a regular user.
+ </div></div><div class="figure" title="Figure 11.2. Available Addresses" id="httpd-listen"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-listen.png" alt="Available Addresses" /><div class="longdesc"><div class="para">
+ Available Addresses
+ </div></div></div></div><h6>Figure 11.2. Available Addresses</h6></div><br class="figure-break" /></div><div class="section" title="11.4.2. Default Settings" id="s2-httpd-default-settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-httpd-default-settings">11.4.2. Default Settings</h3></div></div></div><div class="para">
+ After defining the <span class="guilabel"><strong>Server Name</strong></span>, <span class="guilabel"><strong>Webmaster email address</strong></span>, and <span class="guilabel"><strong>Available Addresses</strong></span>, click the <span class="guilabel"><strong>Virtual Hosts</strong></span> tab. The figure below illustrates the <span class="guilabel"><strong>Virtual Hosts</strong></span> tab.
+ </div><div class="figure" title="Figure 11.3. Virtual Hosts Tab" id="httpd-virtual-hosts"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-virtualhosts.png" alt="Virtual Hosts Tab" /><div class="longdesc"><div class="para">
+ Virtual Hosts Tab
+ </div></div></div></div><h6>Figure 11.3. Virtual Hosts Tab</h6></div><br class="figure-break" /><div class="para">
+ Clicking on <span class="guilabel"><strong>Edit</strong></span> will display the <span class="guilabel"><strong>Virtual Host Properties</strong></span> window from which you can set your preferred settings. To add new settings, click on the <span class="guilabel"><strong>Add</strong></span> button which will also display the <span class="guilabel"><strong>Virtual Host Properties</strong></span> window. Clicking on the <span class="guilabel"><strong>Edit Default Settings</strong></span> button, displays the <span class="guilabel"><strong>Virtual Host Properties</strong></span> window without the <span class="guilabel"><strong>General Options</strong></span> tab.
+ </div><div class="para">
+ In the <span class="guilabel"><strong>General Options</strong></span> tab, you can change the hostname, the document root directory and also set the webmaster's email address. In the Host information, you can set the Virtual Host's IP Address and Host Name. The figure below illustrates the <span class="guilabel"><strong>General Options</strong></span> tab.
+ </div><div class="figure" title="Figure 11.4. General Options" id="httpd-general-options"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-general-options.png" width="444" alt="General Options" /><div class="longdesc"><div class="para">
+ General Options
+ </div></div></div></div><h6>Figure 11.4. General Options</h6></div><br class="figure-break" /><div class="para">
+ If you add a virtual host, the settings you configure for the virtual host take precedence for that virtual host. For a directive not defined within the virtual host settings, the default value is used.
+ </div><div class="section" title="11.4.2.1. Site Configuration" id="s3-httpd-site-config"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-httpd-site-config">11.4.2.1. Site Configuration</h4></div></div></div><div class="para">
+ The figure below illustrates the <span class="guibutton"><strong>Page Options</strong></span>tab from which you can configure the <span class="guilabel"><strong>Directory Page Search List</strong></span> and <span class="guilabel"><strong>Error Pages</strong></span>. If you are unsure of these settings, do not modify them.
+ </div><div class="figure" title="Figure 11.5. Site Configuration" id="httpd-site-config-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-siteconfig.png" width="444" alt="Site Configuration" /><div class="longdesc"><div class="para">
+ Site Configuration
+ </div></div></div></div><h6>Figure 11.5. Site Configuration</h6></div><br class="figure-break" /><a id="id588827" class="indexterm"></a><div class="para">
+ The entries listed in the <span class="guilabel"><strong>Directory Page Search List</strong></span> define the <a href="http://httpd.apache.org/docs/2.2/mod/mod_dir.html#directoryindex"><code class="command">DirectoryIndex</code> </a> directive. The <code class="command">DirectoryIndex</code> is the default page served by the server when a user requests an index of a directory by specifying a forward slash (/) at the end of the directory name.
+ </div><div class="para">
+ For example, when a user requests the page <code class="command">http://www.example.com/this_directory/</code>, they are going to get either the <code class="command">DirectoryIndex</code> page, if it exists, or a server-generated directory list. The server tries to find one of the files listed in the <code class="command">DirectoryIndex</code> directive and returns the first one it finds.
+ <a id="id1010839" class="indexterm"></a>
+ If it does not find any of these files and if <code class="command">Options Indexes</code> is set for that directory, the server generates and returns a list, in HTML format, of the subdirectories and files in the directory.
+ </div><a id="id1010864" class="indexterm"></a><div class="para">
+ Use the <span class="guilabel"><strong>Error Code</strong></span> section to configure Apache HTTP Server to redirect the client to a local or external URL in the event of a problem or error. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#errordocument"><code class="command">ErrorDocument</code> </a> directive. If a problem or error occurs when a client tries to connect to the Apache HTTP Server, the default action is to display the short error message shown in the <span class="guilabel"><strong>Error Code</strong></span> column. To override this default configuration, select the error code and click the <span class="guilabel"><strong>Edit</strong></span> button. Choose <span class="guimenuitem"><strong>Default</strong></span> to display the default short error message. Choose <span class="guimenuitem"><strong>URL</strong></span> to redirect the client to an external URL and enter a complete URL, including the <code class="command
">http://</code>, in the <span class="guilabel"><strong>Location</strong></span> field. Choose <span class="guimenuitem"><strong>File</strong></span> to redirect the client to an internal URL and enter a file location under the document root for the Web server. The location must begin the a slash (/) and be relative to the Document Root.
+ </div><div class="para">
+ For example, to redirect a 404 Not Found error code to a webpage that you created in a file called <code class="filename">404.html</code>, copy <code class="filename">404.html</code> to <code class="filename"><em class="replaceable"><code>DocumentRoot</code></em>/../error/404.html</code>. In this case, <em class="replaceable"><code>DocumentRoot</code></em> is the Document Root directory that you have defined (the default is <code class="filename">/var/www/html/</code>). If the Document Root is left as the default location, the file should be copied to <code class="filename">/var/www/error/404.html</code>. Then, choose <span class="guimenuitem"><strong>File</strong></span> as the Behavior for <span class="guilabel"><strong>404 - Not Found</strong></span> error code and enter <code class="filename">/error/404.html</code> as the <span class="guimenuitem"><strong>Location</strong></span>.
+ </div><div class="para">
+ From the <span class="guilabel"><strong>Default Error Page Footer</strong></span> menu, you can choose one of the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Show footer with email address</strong></span> — Display the default footer at the bottom of all error pages along with the email address of the website maintainer specified by the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#serveradmin"><code class="command">ServerAdmin</code> </a> directive.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Show footer</strong></span> — Display just the default footer at the bottom of error pages.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>No footer</strong></span> — Do not display a footer at the bottom of error pages.
+ </div></li></ul></div></div><div class="section" title="11.4.2.2. SSL Support" id="s3-httpd-ssl-variables"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-httpd-ssl-variables">11.4.2.2. SSL Support</h4></div></div></div><div class="para">
+ The <code class="command">mod_ssl</code> enables encryption of the HTTP protocol over SSL. SSL (Secure Sockets Layer) protocol is used for communication and encryption over TCP/IP networks. The SSL tab enables you to configure SSL for your server. To configure SSL you need to provide the path to your:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Certificate file - equivalent to using the <code class="command">SSLCertificateFile</code> directive which points the path to the PEM (Privacy Enhanced Mail)-encoded server certificate file.
+ </div></li><li class="listitem"><div class="para">
+ Key file - equivalent to using the <code class="command">SSLCertificateKeyFile</code> directive which points the path to the PEM-encoded server private key file.
+ </div></li><li class="listitem"><div class="para">
+ Certificate chain file - equivalent to using the <code class="command">SSLCertificateChainFile</code> directive which points the path to the certificate file containing all the server's chain of certificates.
+ </div></li><li class="listitem"><div class="para">
+ Certificate authority file - is an encrypted file used to confirm the authenticity or identity of parties communicating with the server.
+ </div></li></ul></div><div class="para">
+ You can find out more about configuration directives for SSL on <a href="http://httpd.apache.org/docs/2.2/mod/directives.html#S"> http://httpd.apache.org/docs/2.2/mod/directives.html#S</a>. You also need to determine which SSL options to enable. These are equivalent to using the <code class="command">SSLOptions</code> with the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ FakeBasicAuth - enables standard authentication methods used by Apache. This means that the Client X509 certificate's Subject Distinguished Name (DN) is translated into a basic HTTP username.
+ </div></li><li class="listitem"><div class="para">
+ ExportCertData - creates CGI environment variables in <code class="command">SSL_SERVER_CERT</code>, <code class="command">SSL_CLIENT_CERT</code> and <code class="command">SSL_CLIENT_CERT_CHAIN_n</code> where n is a number 0,1,2,3,4... These files are used for more certificate checks by CGI scripts.
+ </div></li><li class="listitem"><div class="para">
+ CompatEnvVars - enables backward compatibility for Apache SSL by adding CGI environment variables.
+ </div></li><li class="listitem"><div class="para">
+ StrictRequire - enables strict access which forces denial of access whenever the <code class="command">SSLRequireSSL</code> and <code class="command">SSLRequire</code> directives indicate access is forbiden.
+ </div></li><li class="listitem"><div class="para">
+ OptRenegotiate - enables avoidance of unnecessary handshakes by <code class="command">mod_ssl</code> which also performs safe parameter checks. It is recommended to enable OptRenegotiate on a per directory basis.
+ </div></li></ul></div><div class="para">
+ More information on the above SSL options can be found on <a href="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#ssloptions"> http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#ssloptions</a>. The figure below illustrates the SSL tab and the options discussed above.
+ </div><div class="figure" title="Figure 11.6. SSL" id="httpd-virtualhosts-ssl"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-virtualhosts-ssl.png" width="444" alt="SSL" /><div class="longdesc"><div class="para">
+ SSL
+ </div></div></div></div><h6>Figure 11.6. SSL</h6></div><br class="figure-break" /></div><div class="section" title="11.4.2.3. Logging" id="s3-httpd-logging"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-httpd-logging">11.4.2.3. Logging</h4></div></div></div><a id="id956348" class="indexterm"></a><a id="id773179" class="indexterm"></a><div class="para">
+ Use the <span class="guilabel"><strong>Logging</strong></span> tab to configure options for specific transfer and error logs.
+ </div><div class="para">
+ By default, the server writes the transfer log to the <code class="filename">/var/log/httpd/access_log</code> file and the error log to the <code class="filename">/var/log/httpd/error_log</code> file.
+ </div><div class="para">
+ The transfer log contains a list of all attempts to access the Web server. It records the IP address of the client that is attempting to connect, the date and time of the attempt, and the file on the Web server that it is trying to retrieve. Enter the name of the path and file in which to store this information. If the path and file name do not start with a slash (/), the path is relative to the server root directory as configured. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/mod_log_config.html#transferlog"><code class="command">TransferLog</code> </a> directive.
+ </div><div class="figure" title="Figure 11.7. Logging" id="httpd-logging-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-logging.png" width="444" alt="Logging" /><div class="longdesc"><div class="para">
+ Logging
+ </div></div></div></div><h6>Figure 11.7. Logging</h6></div><br class="figure-break" /><a id="id926429" class="indexterm"></a><a id="id1872909" class="indexterm"></a><div class="para">
+ You can configure a custom log format by checking <span class="guilabel"><strong>Use custom logging facilities</strong></span> and entering a custom log string in the <span class="guilabel"><strong>Custom Log String</strong></span> field. This configures the <a href="http://httpd.apache.org/docs/2.2/mod/mod_log_config.html#logformat"><code class="command">LogFormat</code> </a> directive. Refer to <a href="http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#formats"> http://httpd.apache.org/docs/2.2/mod/mod_log_config.html#logformat</a> for details on the format of this directive.
+ </div><a id="id1872956" class="indexterm"></a><div class="para">
+ The error log contains a list of any server errors that occur. Enter the name of the path and file in which to store this information. If the path and file name do not start with a slash (/), the path is relative to the server root directory as configured. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#errorlog"><code class="command">ErrorLog</code> </a> directive.
+ </div><a id="id1870550" class="indexterm"></a><div class="para">
+ Use the <span class="guilabel"><strong>Log Level</strong></span> menu to set the verbosity of the error messages in the error logs. It can be set (from least verbose to most verbose) to emerg, alert, crit, error, warn, notice, info or debug. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#loglevel"><code class="command">LogLevel</code> </a> directive.
+ </div><a id="id859942" class="indexterm"></a><div class="para">
+ The value chosen with the <span class="guilabel"><strong>Reverse DNS Lookup</strong></span> menu defines the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#hostnamelookups"><code class="command">HostnameLookups</code> </a> directive. Choosing <span class="guilabel"><strong>No Reverse Lookup</strong></span> sets the value to off. Choosing <span class="guilabel"><strong>Reverse Lookup</strong></span> sets the value to on. Choosing <span class="guilabel"><strong>Double Reverse Lookup</strong></span> sets the value to double.
+ </div><div class="para">
+ If you choose <span class="guilabel"><strong>Reverse Lookup</strong></span>, your server automatically resolves the IP address for each connection which requests a document from your Web server. Resolving the IP address means that your server makes one or more connections to the DNS in order to find out the hostname that corresponds to a particular IP address.
+ </div><div class="para">
+ If you choose <span class="guilabel"><strong>Double Reverse Lookup</strong></span>, your server performs a double-reverse DNS. In other words, after a reverse lookup is performed, a forward lookup is performed on the result. At least one of the IP addresses in the forward lookup must match the address from the first reverse lookup.
+ </div><div class="para">
+ Generally, you should leave this option set to <span class="guilabel"><strong>No Reverse Lookup</strong></span>, because the DNS requests add a load to your server and may slow it down. If your server is busy, the effects of trying to perform these reverse lookups or double reverse lookups may be quite noticeable.
+ </div><div class="para">
+ Reverse lookups and double reverse lookups are also an issue for the Internet as a whole. Each individual connection made to look up each hostname adds up. Therefore, for your own Web server's benefit, as well as for the Internet's benefit, you should leave this option set to <span class="guilabel"><strong>No Reverse Lookup</strong></span>.
+ </div></div><div class="section" title="11.4.2.4. Environment Variables" id="s3-httpd-environment-variables"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-httpd-environment-variables">11.4.2.4. Environment Variables</h4></div></div></div><div class="para">
+ Use the <span class="guilabel"><strong>Environment</strong></span> tab to configure options for specific variables to set, pass, or unset for CGI scripts.
+ </div><div class="para">
+ Sometimes it is necessary to modify environment variables for CGI scripts or server-side include (SSI) pages. The Apache HTTP Server can use the <code class="command">mod_env</code> module to configure the environment variables which are passed to CGI scripts and SSI pages. Use the <span class="guilabel"><strong>Environment Variables</strong></span> page to configure the directives for this module.
+ </div><div class="para">
+ Use the <span class="guilabel"><strong>Set for CGI Scripts</strong></span> section to set an environment variable that is passed to CGI scripts and SSI pages. For example, to set the environment variable <code class="filename">MAXNUM</code> to <code class="filename">50</code>, click the <span class="guibutton"><strong>Add</strong></span> button inside the <span class="guilabel"><strong>Set for CGI Script</strong></span> section, as shown in <a class="xref" href="#httpd-environment-variables-screen" title="Figure 11.8. Environment Variables">Figure 11.8, “Environment Variables”</a>, and type <strong class="userinput"><code>MAXNUM</code></strong> in the <span class="guilabel"><strong>Environment Variable</strong></span> text field and <strong class="userinput"><code>50</code></strong> in the <span class="guilabel"><strong>Value to set</strong></span> text field. Click <span class="guibutton"><strong>OK</strong></span> to add it to the list. The <span class="guilabe
l"><strong>Set for CGI Scripts</strong></span> section configures the <a href="http://httpd.apache.org/docs/2.2/mod/mod_env.html#setenv"><code class="command">SetEnv</code> </a> directive.
+ </div><div class="para">
+ Use the <span class="guilabel"><strong>Pass to CGI Scripts</strong></span> section to pass the value of an environment variable when the server is first started to CGI scripts. To see this environment variable, type the command <code class="command">env</code> at a shell prompt. Click the <span class="guibutton"><strong>Add</strong></span> button inside the <span class="guilabel"><strong>Pass to CGI Scripts</strong></span> section and enter the name of the environment variable in the resulting dialog box. Click <span class="guibutton"><strong>OK</strong></span> to add it to the list. The <span class="guilabel"><strong>Pass to CGI Scripts</strong></span> section configures the <a href="http://httpd.apache.org/docs/2.2/mod/mod_env.html#passenv"><code class="command">PassEnv</code> </a> directive.
+ </div><div class="figure" title="Figure 11.8. Environment Variables" id="httpd-environment-variables-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-environment.png" width="444" alt="Environment Variables" /><div class="longdesc"><div class="para">
+ Environment Variables
+ </div></div></div></div><h6>Figure 11.8. Environment Variables</h6></div><br class="figure-break" /><div class="para">
+ To remove an environment variable so that the value is not passed to CGI scripts and SSI pages, use the <span class="guilabel"><strong>Unset for CGI Scripts</strong></span> section. Click <span class="guibutton"><strong>Add</strong></span> in the <span class="guilabel"><strong>Unset for CGI Scripts</strong></span> section, and enter the name of the environment variable to unset. Click <span class="guibutton"><strong>OK</strong></span> to add it to the list. This corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/mod_env.html#unsetenv"><code class="command">UnsetEnv</code> </a> directive.
+ </div><div class="para">
+ To edit any of these environment values, select it from the list and click the corresponding <span class="guibutton"><strong>Edit</strong></span> button. To delete any entry from the list, select it and click the corresponding <span class="guibutton"><strong>Delete</strong></span> button.
+ </div><div class="para">
+ To learn more about environment variables in the Apache HTTP Server, refer to the following: <a href="http://httpd.apache.org/docs/2.2/env.html">http://httpd.apache.org/docs/2.2/env.html</a>
+ </div></div><div class="section" title="11.4.2.5. Directories" id="s3-httpd-directories"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-httpd-directories">11.4.2.5. Directories</h4></div></div></div><div class="para">
+ Use the <span class="guilabel"><strong>Directories</strong></span> page in the <span class="guilabel"><strong>Performance</strong></span> tab to configure options for specific directories. This corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#directory"><code class="command"><Directory></code> </a> directive.
+ </div><div class="figure" title="Figure 11.9. Directories" id="httpd-directories-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-directories.png" width="444" alt="Directories" /><div class="longdesc"><div class="para">
+ Directories
+ </div></div></div></div><h6>Figure 11.9. Directories</h6></div><br class="figure-break" /><div class="para">
+ Click the <span class="guibutton"><strong>Edit</strong></span> button in the top right-hand corner to configure the <span class="guilabel"><strong>Default Directory Options</strong></span> for all directories that are not specified in the <span class="guilabel"><strong>Directory</strong></span> list below it. The options that you choose are listed as the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#options"><code class="command">Options</code> </a> directive within the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#directory"> <code class="command"><Directory></code> </a> directive. You can configure the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>ExecCGI</strong></span> — Allow execution of CGI scripts. CGI scripts are not executed if this option is not chosen.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>FollowSymLinks</strong></span> — Allow symbolic links to be followed.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Includes</strong></span> — Allow server-side includes.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>IncludesNOEXEC</strong></span> — Allow server-side includes, but disable the <code class="command">#exec</code> and <code class="command">#include</code> commands in CGI scripts.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Indexes</strong></span> — Display a formatted list of the directory's contents, if no <code class="command">DirectoryIndex</code> (such as <code class="filename">index.html</code>) exists in the requested directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Multiview</strong></span> — Support content-negotiated multiviews; this option is disabled by default.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>SymLinksIfOwnerMatch</strong></span> — Only follow symbolic links if the target file or directory has the same owner as the link.
+ </div></li></ul></div><div class="para">
+ To specify options for specific directories, click the <span class="guibutton"><strong>Add</strong></span> button beside the <span class="guilabel"><strong>Directory</strong></span> list box. A window as shown in <a class="xref" href="#httpd-directories-add" title="Figure 11.10. Directory Settings">Figure 11.10, “Directory Settings”</a> appears. Enter the directory to configure in the <span class="guilabel"><strong>Directory</strong></span> text field at the bottom of the window. Select the options in the right-hand list and configure the <a href="http://httpd.apache.org/docs-2.0/mod/mod_access.html#order"><code class="command">Order</code> </a> directive with the left-hand side options. The <code class="command">Order</code> directive controls the order in which allow and deny directives are evaluated. In the <span class="guilabel"><strong>Allow hosts from</strong></span> and <span class="guilabel"><strong>Deny hosts from</strong></span> text field, you can spec
ify one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Allow all hosts — Type <strong class="userinput"><code>all</code></strong> to allow access to all hosts.
+ </div></li><li class="listitem"><div class="para">
+ Partial domain name — Allow all hosts whose names match or end with the specified string.
+ </div></li><li class="listitem"><div class="para">
+ Full IP address — Allow access to a specific IP address.
+ </div></li><li class="listitem"><div class="para">
+ A subnet — Such as <strong class="userinput"><code>192.168.1.0/255.255.255.0</code></strong>
+ </div></li><li class="listitem"><div class="para">
+ A network CIDR specification — such as <strong class="userinput"><code>10.3.0.0/16</code></strong>
+ </div></li></ul></div><div class="figure" title="Figure 11.10. Directory Settings" id="httpd-directories-add"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-directories-add.png" width="444" alt="Directory Settings" /><div class="longdesc"><div class="para">
+ Directory Settings
+ </div></div></div></div><h6>Figure 11.10. Directory Settings</h6></div><br class="figure-break" /><div class="para">
+ If you check the <span class="guilabel"><strong>Let .htaccess files override directory options</strong></span>, the configuration directives in the <code class="filename">.htaccess</code> file take precedence.
+ </div></div></div></div><div class="section" title="11.5. Configuration Directives in httpd.conf" id="s1-apache-config"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-config">11.5. Configuration Directives in <code class="filename">httpd.conf</code> </h2></div></div></div><a id="id1000724" class="indexterm"></a><a id="id1000739" class="indexterm"></a><a id="id1000753" class="indexterm"></a><a id="id646985" class="indexterm"></a><a id="id647008" class="indexterm"></a><div class="para">
+ The Apache HTTP Server configuration file is <code class="filename">/etc/httpd/conf/httpd.conf</code>. The <code class="filename">httpd.conf</code> file is well-commented and mostly self-explanatory. The default configuration works for most situations; however, it is a good idea to become familiar some of the more important configuration options.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ With the release of Apache HTTP Server 2.2, many configuration options have changed. If migrating from version 1.3 to 2.2, please firstly read <a class="xref" href="#s3-httpd-v2-mig" title="11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0">Section 11.2.2, “Migrating Apache HTTP Server 1.3 Configuration Files to 2.0”</a>.
+ </div></div><div class="section" title="11.5.1. General Configuration Tips" id="s2-apache-tips"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-tips">11.5.1. General Configuration Tips</h3></div></div></div><div class="para">
+ If configuring the Apache HTTP Server, edit <code class="filename">/etc/httpd/conf/httpd.conf</code> and then either reload, restart, or stop and start the <code class="command">httpd</code> process as outlined in <a class="xref" href="#s1-apache-startstop" title="11.3. Starting and Stopping httpd">Section 11.3, “Starting and Stopping <code class="command">httpd</code> ”</a>.
+ </div><div class="para">
+ Before editing <code class="filename">httpd.conf</code>, make a copy the original file. Creating a backup makes it easier to recover from mistakes made while editing the configuration file.
+ </div><div class="para">
+ If a mistake is made and the Web server does not work correctly, first review recently edited passages in <code class="filename">httpd.conf</code> to verify there are no typos.
+ </div><div class="para">
+ Next look in the Web server's error log, <code class="filename">/var/log/httpd/error_log</code>. The error log may not be easy to interpret, depending on your level of expertise. However, the last entries in the error log should provide useful information.
+ </div><div class="para">
+ The following subsections contain a list of short descriptions for many of the directives included in <code class="filename">httpd.conf</code>. These descriptions are not exhaustive. For more information, refer to the Apache documentation online at <a href="http://httpd.apache.org/docs/2.2/">http://httpd.apache.org/docs/2.2/</a>.
+ </div><div class="para">
+ For more information about <code class="filename">mod_ssl</code> directives, refer to the documentation online at <a href="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html">http://httpd.apache.org/docs/2.2/mod/mod_ssl.html</a>.
+ </div><a id="id949141" class="indexterm"></a><a id="id949159" class="indexterm"></a><div class="formalpara" id="s2-apache-accessfilename"><h5 class="formalpara">AccessFileName</h5><a id="id741819" class="indexterm"></a><a id="id741837" class="indexterm"></a>
+ <code class="command">AccessFileName</code> names the file which the server should use for access control information in each directory. The default is <code class="filename">.htaccess</code>.
+ </div><div class="para">
+ Immediately after the <code class="command">AccessFileName</code> directive, a set of <code class="command">Files</code> tags apply access control to any file beginning with a <code class="filename">.ht</code>. These directives deny Web access to any <code class="filename">.htaccess</code> files (or other files which begin with <code class="filename">.ht</code>) for security reasons.
+ </div><div class="formalpara" id="s2-apache-action"><h5 class="formalpara">Action</h5><a id="id905325" class="indexterm"></a><a id="id905344" class="indexterm"></a>
+ <code class="command">Action</code> specifies a MIME content type and CGI script pair, so that when a file of that media type is requested, a particular CGI script is executed.
+ </div><div class="formalpara" id="s2-apache-adddescription"><h5 class="formalpara">AddDescription</h5><a id="id856746" class="indexterm"></a><a id="id856765" class="indexterm"></a>
+ When using <code class="command">FancyIndexing</code> as an <code class="command">IndexOptions</code> parameter, the <code class="command">AddDescription</code> directive can be used to display user-specified descriptions for certain files or file types in a server generated directory listing. The <code class="command">AddDescription</code> directive supports listing specific files, wildcard expressions, or file extensions.
+ </div><div class="formalpara" id="s2-apache-addencoding"><h5 class="formalpara">AddEncoding</h5><a id="id606298" class="indexterm"></a><a id="id986187" class="indexterm"></a>
+ <code class="command">AddEncoding</code> names file name extensions which should specify a particular encoding type. <code class="command">AddEncoding</code> can also be used to instruct some browsers to uncompress certain files as they are downloaded.
+ </div><div class="formalpara" id="s2-apache-addhandler"><h5 class="formalpara">AddHandler</h5><a id="id986235" class="indexterm"></a><a id="id1780076" class="indexterm"></a><a id="id1780094" class="indexterm"></a>
+ <code class="command">AddHandler</code> maps file extensions to specific handlers. For example, the <code class="command">cgi-script</code> handler can be matched with the extension <code class="filename">.cgi</code> to automatically treat a file ending with <code class="filename">.cgi</code> as a CGI script. The following is a sample <code class="command">AddHandler</code> directive for the <code class="filename">.cgi</code> extension.
+ </div><pre class="screen">
+<code class="command">AddHandler cgi-script .cgi</code>
+</pre><div class="para">
+ This directive enables CGIs outside of the <code class="filename">cgi-bin</code> to function in any directory on the server which has the <code class="command">ExecCGI</code> option within the directories container. Refer to <a class="xref" href="#s2-apache-directory" title="Directory">Directory</a> for more information about setting the <code class="command">ExecCGI</code> option for a directory.
+ </div><div class="para">
+ In addition to CGI scripts, the <code class="command">AddHandler</code> directive is used to process server-parsed HTML and image-map files.
+ </div><div class="formalpara" id="s2-apache-addicon"><h5 class="formalpara">AddIcon</h5><a id="id1117257" class="indexterm"></a><a id="id1117275" class="indexterm"></a>
+ <code class="command">AddIcon</code> specifies which icon to show in server generated directory listings for files with certain extensions. For example, the Web server is set to show the icon <code class="filename">binary.gif</code> for files with <code class="filename">.bin</code> or <code class="filename">.exe</code> extensions.
+ </div><div class="formalpara" id="s2-apache-addiconbyencoding"><h5 class="formalpara">AddIconByEncoding</h5><a id="id979407" class="indexterm"></a><a id="id979425" class="indexterm"></a>
+ This directive names icons which are displayed by files with MIME encoding in server generated directory listings. For example, by default, the Web server shows the <code class="filename">compressed.gif</code> icon next to MIME encoded x-compress and x-gzip files in server generated directory listings.
+ </div><div class="formalpara" id="s2-apache-addiconbytype"><h5 class="formalpara">AddIconByType</h5><a id="id767603" class="indexterm"></a><a id="id767621" class="indexterm"></a>
+ This directive names icons which are displayed next to files with MIME types in server generated directory listings. For example, the server shows the icon <code class="filename">text.gif</code> next to files with a mime-type of <code class="computeroutput">text</code>, in server generated directory listings.
+ </div><div class="formalpara" id="s2-apache-addlanguage"><h5 class="formalpara">AddLanguage</h5><a id="id775678" class="indexterm"></a><a id="id775696" class="indexterm"></a>
+ <code class="command">AddLanguage</code> associates file name extensions with specific languages. This directive is useful for Apache HTTP Servers which serve content in multiple languages based on the client Web browser's language settings.
+ </div><div class="formalpara" id="s2-apache-addtype"><h5 class="formalpara">AddType</h5><a id="id814007" class="indexterm"></a><a id="id814026" class="indexterm"></a><a id="id1483786" class="indexterm"></a><a id="id1483797" class="indexterm"></a>
+ Use the <code class="command">AddType</code> directive to define or override a default MIME type and file extension pairs. The following example directive tells the Apache HTTP Server to recognize the <code class="command">.tgz</code> file extension:
+ </div><pre class="screen">
+<code class="command">AddType application/x-tar .tgz</code>
+</pre><div class="formalpara" id="s2-apache-alias"><h5 class="formalpara">Alias</h5><a id="id612599" class="indexterm"></a><a id="id612617" class="indexterm"></a>
+ The <code class="command">Alias</code> setting allows directories outside the <code class="command">DocumentRoot</code> directory to be accessible. Any URL ending in the alias automatically resolves to the alias' path. By default, one alias for an <code class="filename">icons/</code> directory is already set up. An <code class="filename">icons/</code> directory can be accessed by the Web server, but the directory is not in the <code class="command"> DocumentRoot</code>.
+ </div><div class="formalpara" id="s2-apache-allow"><h5 class="formalpara">Allow</h5><a id="id816968" class="indexterm"></a><a id="id816986" class="indexterm"></a>
+ <code class="command">Allow</code> specifies which client can access a given directory. The client can be <code class="command">all</code>, a domain name, an IP address, a partial IP address, a network/netmask pair, and so on. The <code class="command">DocumentRoot</code> directory is configured to <code class="command">Allow</code> requests from <code class="command">all</code>, meaning everyone has access.
+ </div><div class="formalpara" id="s2-apache-allowoverride"><h5 class="formalpara">AllowOverride</h5><a id="id764011" class="indexterm"></a><a id="id764030" class="indexterm"></a>
+ The <code class="command">AllowOverride</code> directive sets whether any <code class="command">Options</code> can be overridden by the declarations in an <code class="filename">.htaccess</code> file. By default, both the root directory and the <code class="command">DocumentRoot</code> are set to allow no <code class="filename">.htaccess</code> overrides.
+ </div><div class="formalpara" id="s2-apache-browsermatch"><h5 class="formalpara">BrowserMatch</h5><a id="id679467" class="indexterm"></a><a id="id810209" class="indexterm"></a>
+ The <code class="command">BrowserMatch</code> directive allows the server to define environment variables and take appropriate actions based on the User-Agent HTTP header field — which identifies the client's Web browser type. By default, the Web server uses <code class="command">BrowserMatch</code> to deny connections to specific browsers with known problems and also to disable keepalives and HTTP header flushes for browsers that are known to have problems with those actions.
+ </div><div class="formalpara" id="s2-apache-cachedirectives"><h5 class="formalpara">Cache Directives</h5><a id="id810259" class="indexterm"></a><a id="id810269" class="indexterm"></a><a id="id859556" class="indexterm"></a>
+ A number of commented cache directives are supplied by the default Apache HTTP Server configuration file. In most cases, uncommenting these lines by removing the hash mark (<code class="command">#</code>) from the beginning of the line is sufficient. The following, however, is a list of some of the more important cache-related directives.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">CacheEnable</code> — Specifies whether the cache is a disk, memory, or file descriptor cache. By default <code class="command">CacheEnable</code> configures a disk cache for URLs at or below <code class="filename">/</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">CacheRoot</code> — Specifies the name of the directory containing cached files. The default <code class="command">CacheRoot</code> is the <code class="filename">/var/httpd/proxy/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">CacheSize</code> — Specifies how much space the cache can use in kilobytes. The default <code class="command">CacheSize</code> is <code class="command">5</code> KB.
+ </div></li></ul></div><div class="para">
+ The following is a list of some of the other common cache-related directives.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">CacheMaxExpire</code> — Specifies how long HTML documents are retained (without a reload from the originating Web server) in the cache. The default is <code class="command">24</code> hours (<code class="command">86400</code> seconds).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">CacheLastModifiedFactor</code> — Specifies the creation of an expiry (expiration) date for a document which did not come from its originating server with its own expiry set. The default <code class="command">CacheLastModifiedFactor</code> is set to <code class="command">0.1</code>, meaning that the expiry date for such documents equals one-tenth of the amount of time since the document was last modified.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">CacheDefaultExpire</code> — Specifies the expiry time in hours for a document that was received using a protocol that does not support expiry times. The default is set to <code class="command">1</code> hour (<code class="command">3600</code> seconds).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">NoProxy</code> — Specifies a space-separated list of subnets, IP addresses, domains, or hosts whose content is not cached. This setting is most useful for Intranet sites.
+ </div></li></ul></div><div class="formalpara" id="s2-apache-cachenegotiateddocs"><h5 class="formalpara">CacheNegotiatedDocs</h5><a id="id2400599" class="indexterm"></a><a id="id2400617" class="indexterm"></a>
+ By default, the Web server asks proxy servers not to cache any documents which were negotiated on the basis of content (that is, they may change over time or because of the input from the requester). If <code class="command">CacheNegotiatedDocs</code> is set to <code class="option">on</code>, this function is disabled and proxy servers are allowed to cache such documents.
+ </div><div class="formalpara" id="s2-apache-customlog"><h5 class="formalpara">CustomLog</h5><a id="id658998" class="indexterm"></a><a id="id659016" class="indexterm"></a><a id="id659035" class="indexterm"></a>
+ <code class="command">CustomLog</code> identifies the log file and the log file format. By default, the access log is recorded to the <code class="filename">/var/log/httpd/access_log</code> file while errors are recorded in the <code class="filename">/var/log/httpd/error_log</code> file.
+ </div><div class="para">
+ The default <code class="command">CustomLog</code> format is the <code class="option">combined</code> log file format, as illustrated here:
+ </div><pre class="screen">
+<code class="command"><em class="replaceable"><code>remotehost rfc931 user date "request" status bytes referrer user-agent</code></em> </code>
+</pre><div class="formalpara" id="s2-apache-defaulticon"><h5 class="formalpara">DefaultIcon</h5><a id="id824912" class="indexterm"></a><a id="id824930" class="indexterm"></a>
+ <code class="command">DefaultIcon</code> specifies the icon displayed in server generated directory listings for files which have no other icon specified. The <code class="filename">unknown.gif</code> image file is the default.
+ </div><div class="formalpara" id="s2-apache-defaulttype"><h5 class="formalpara">DefaultType</h5><a id="id771007" class="indexterm"></a><a id="id771025" class="indexterm"></a>
+ <code class="command">DefaultType</code> sets a default content type for the Web server to use for documents whose MIME types cannot be determined. The default is <code class="command"> text/plain</code>.
+ </div><div class="formalpara" id="s2-apache-deny"><h5 class="formalpara">Deny</h5><a id="id1020859" class="indexterm"></a><a id="id1020878" class="indexterm"></a>
+ <code class="command">Deny</code> works similar to <code class="command">Allow</code>, except it specifies who is denied access. The <code class="command">DocumentRoot</code> is not configured to <code class="command">Deny</code> requests from anyone by default.
+ </div><div class="formalpara" id="s2-apache-directory"><h5 class="formalpara">Directory</h5><a id="id894145" class="indexterm"></a><a id="id894164" class="indexterm"></a>
+ <code class="command"><Directory /path/to/directory></code> and <code class="command"></Directory></code> tags create a container used to enclose a group of configuration directives which apply only to a specific directory and its subdirectories. Any directive which is applicable to a directory may be used within <code class="command">Directory</code> tags.
+ </div><div class="para">
+ By default, very restrictive parameters are applied to the root directory (<code class="filename">/</code>), using the <code class="command">Options</code> (refer to <a class="xref" href="#s2-apache-options" title="Options">Options</a>) and <code class="command">AllowOverride</code> (refer to <a class="xref" href="#s2-apache-allowoverride" title="AllowOverride">AllowOverride</a>) directives. Under this configuration, any directory on the system which needs more permissive settings has to be explicitly given those settings.
+ </div><div class="para">
+ In the default configuration, another <code class="command">Directory</code> container is configured for the <code class="command">DocumentRoot</code> which assigns less rigid parameters to the directory tree so that the Apache HTTP Server can access the files residing there.
+ </div><a id="id812076" class="indexterm"></a><div class="para">
+ The <code class="command">Directory</code> container can be also be used to configure additional <code class="filename">cgi-bin</code> directories for server-side applications outside of the directory specified in the <code class="command">ScriptAlias</code> directive (refer to <a class="xref" href="#s2-apache-scriptalias" title="ScriptAlias">ScriptAlias</a> for more information).
+ </div><div class="para">
+ To accomplish this, the <code class="command">Directory</code> container must set the <code class="command">ExecCGI</code> option for that directory.
+ </div><div class="para">
+ For example, if CGI scripts are located in <code class="command">/home/my_cgi_directory</code>, add the following <code class="command">Directory</code> container to the <code class="filename">httpd.conf</code> file:
+ </div><pre class="screen">
+<code class="command"><Directory /home/my_cgi_directory> Options +ExecCGI </Directory></code>
+</pre><div class="para">
+ Next, the <code class="command">AddHandler</code> directive must be uncommented to identify files with the <code class="filename">.cgi</code> extension as CGI scripts. Refer to <a class="xref" href="#s2-apache-addhandler" title="AddHandler">AddHandler</a> for instructions on setting <code class="command">AddHandler</code>.
+ </div><div class="para">
+ For this to work, permissions for CGI scripts, and the entire path to the scripts, must be set to 0755.
+ </div><div class="formalpara" id="s2-apache-directoryindex"><h5 class="formalpara">DirectoryIndex</h5><a id="id735393" class="indexterm"></a><a id="id1760137" class="indexterm"></a>
+ The <code class="command">DirectoryIndex</code> is the default page served by the server when a user requests an index of a directory by specifying a forward slash (/) at the end of the directory name.
+ </div><div class="para">
+ When a user requests the page http://<em class="replaceable"><code>example</code></em>/<em class="replaceable"><code>this_directory</code></em>/, they get either the <code class="command">DirectoryIndex</code> page, if it exists, or a server-generated directory list. The default for <code class="command">DirectoryIndex</code> is <code class="filename">index.html</code> and the <code class="filename">index.html.var</code> type map. The server tries to find either of these files and returns the first one it finds. If it does not find one of these files and <code class="command">Options Indexes</code> is set for that directory, the server generates and returns a listing, in HTML format, of the subdirectories and files within the directory, unless the directory listing feature is turned off.
+ </div><div class="formalpara" id="s2-apache-documentroot"><h5 class="formalpara">DocumentRoot</h5><a id="id867229" class="indexterm"></a><a id="id867247" class="indexterm"></a>
+ <code class="command">DocumentRoot</code> is the directory which contains most of the HTML files which are served in response to requests. The default <code class="command">DocumentRoot</code>, for both the non-secure and secure Web servers, is the <code class="filename">/var/www/html</code> directory. For example, the server might receive a request for the following document:
+ </div><pre class="screen">
+<code class="command">http://example.com/foo.html</code>
+</pre><div class="para">
+ The server looks for the following file in the default directory:
+ </div><pre class="screen">
+<code class="filename">/var/www/html/foo.html</code>
+</pre><div class="para">
+ To change the <code class="command">DocumentRoot</code> so that it is not shared by the secure and the non-secure Web servers, refer to <a class="xref" href="#s1-apache-virtualhosts" title="11.7. Virtual Hosts">Section 11.7, “Virtual Hosts”</a>.
+ </div><div class="formalpara" id="s2-apache-errordocument"><h5 class="formalpara">ErrorDocument</h5><a id="id948125" class="indexterm"></a><a id="id597072" class="indexterm"></a>
+ The <code class="command">ErrorDocument</code> directive associates an HTTP response code with a message or a URL to be sent back to the client. By default, the Web server outputs a simple and usually cryptic error message when an error occurs. The <code class="command">ErrorDocument</code> directive forces the Web server to instead output a customized message or page.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ To be valid, the message <span class="emphasis"><em>must</em></span> be enclosed in a pair of double quotes <code class="command">"</code>.
+ </div></div><div class="formalpara" id="s2-apache-errorlog"><h5 class="formalpara">ErrorLog</h5><a id="id577328" class="indexterm"></a><a id="id577346" class="indexterm"></a>
+ <code class="command">ErrorLog</code> specifies the file where server errors are logged. By default, this directive is set to <code class="filename">/var/log/httpd/error_log</code>.
+ </div><a id="id941924" class="indexterm"></a><div class="formalpara" id="s2-apache-extendedstatus"><h5 class="formalpara">ExtendedStatus</h5><a id="id941953" class="indexterm"></a><a id="id941972" class="indexterm"></a>
+ The <code class="command">ExtendedStatus</code> directive controls whether Apache generates basic (<code class="command">off</code>) or detailed server status information (<code class="command">on</code>), when the <code class="command">server-status</code> handler is called. The <code class="command">server-status</code> handler is called using <code class="command">Location</code> tags. More information on calling <code class="command">server-status</code> is included in <a class="xref" href="#s2-apache-location" title="Location">Location</a>.
+ </div><div class="formalpara" id="s2-apache-group"><h5 class="formalpara">Group</h5><a id="id728347" class="indexterm"></a><a id="id991078" class="indexterm"></a>
+ Specifies the group name of the Apache HTTP Server processes.
+ </div><div class="para">
+ This directive has been deprecated for the configuration of virtual hosts.
+ </div><div class="para">
+ By default, <code class="command">Group</code> is set to <code class="command">apache</code>.
+ </div><div class="formalpara" id="s2-apache-headername"><h5 class="formalpara">HeaderName</h5><a id="id1871703" class="indexterm"></a><a id="id1871721" class="indexterm"></a>
+ <code class="command">HeaderName</code> names the file which, if it exists in the directory, is prepended to the start of server generated directory listings. Like <code class="command">ReadmeName</code>, the server tries to include it as an HTML document if possible or in plain text if not.
+ </div><div class="formalpara" id="s2-apache-hostnamelookups"><h5 class="formalpara">HostnameLookups</h5><a id="id821278" class="indexterm"></a><a id="id821296" class="indexterm"></a><a id="id821314" class="indexterm"></a>
+ <code class="command">HostnameLookups</code> can be set to <code class="option">on</code>, <code class="option">off</code>, or <code class="option">double</code>. If <code class="command">HostnameLookups</code> is set to <code class="option">on</code>, the server automatically resolves the IP address for each connection. Resolving the IP address means that the server makes one or more connections to a DNS server, adding processing overhead. If <code class="command">HostnameLookups</code> is set to <code class="option">double</code>, the server performs a double-reverse DNS look up adding even more processing overhead.
+ </div><div class="para">
+ To conserve resources on the server, <code class="command">HostnameLookups</code> is set to <code class="option">off</code> by default.
+ </div><div class="para">
+ If hostnames are required in server log files, consider running one of the many log analyzer tools that perform the DNS lookups more efficiently and in bulk when rotating the Web server log files.
+ </div><div class="formalpara" id="s2-apache-ifdefine"><h5 class="formalpara">IfDefine</h5><a id="id611570" class="indexterm"></a><a id="id611588" class="indexterm"></a>
+ The <code class="command">IfDefine</code> tags surround configuration directives that are applied if the "test" stated in the <code class="command">IfDefine</code> tag is true. The directives are ignored if the test is false.
+ </div><div class="para">
+ The test in the <code class="command">IfDefine</code> tags is a parameter name (for example, <code class="command">HAVE_PERL</code>). If the parameter is defined, meaning that it is provided as an argument to the server's start-up command, then the test is true. In this case, when the Web server is started, the test is true and the directives contained in the <code class="command">IfDefine</code> tags are applied.
+ </div><div class="formalpara" id="s2-apache-ifmodule"><h5 class="formalpara">IfModule</h5><a id="id810455" class="indexterm"></a><a id="id810473" class="indexterm"></a>
+ <code class="command"><IfModule></code> and <code class="command"></IfModule></code> tags create a conditional container which are only activated if the specified module is loaded. Directives within the <code class="command">IfModule</code> container are processed under one of two conditions. The directives are processed if the module contained within the starting <code class="command"><IfModule></code> tag is loaded. Or, if an exclamation point <span class="keycap"><strong>!</strong></span> appears before the module name, the directives are processed only if the module specified in the <code class="command"><IfModule></code> tag is <span class="emphasis"><em>not</em></span> loaded.
+ </div><div class="para">
+ For more information about Apache HTTP Server modules, refer to <a class="xref" href="#s1-apache-addmods" title="11.6. Adding Modules">Section 11.6, “Adding Modules”</a>.
+ </div><div class="formalpara" id="s2-apache-include"><h5 class="formalpara">Include</h5><a id="id756739" class="indexterm"></a><a id="id756757" class="indexterm"></a>
+ <code class="command">Include</code> allows other configuration files to be included at runtime.
+ </div><div class="para">
+ The path to these configuration files can be absolute or relative to the <code class="command">ServerRoot</code>.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ For the server to use individually packaged modules, such as <code class="filename">mod_ssl</code>, <code class="filename">mod_perl</code>, and <code class="filename">php</code>, the following directive must be included in <code class="command">Section 1: Global Environment</code> of <code class="filename">httpd.conf</code>:
+ </div><pre class="screen">
+<code class="command">Include conf.d/*.conf</code>
+</pre></div><div class="formalpara" id="s2-apache-indexignore"><h5 class="formalpara">IndexIgnore</h5><a id="id878769" class="indexterm"></a><a id="id995598" class="indexterm"></a>
+ <code class="command">IndexIgnore</code> lists file extensions, partial file names, wildcard expressions, or full file names. The Web server does not include any files which match any of those parameters in server generated directory listings.
+ </div><div class="formalpara" id="s2-apache-indexoptions"><h5 class="formalpara">IndexOptions</h5><a id="id995643" class="indexterm"></a><a id="id686004" class="indexterm"></a>
+ <code class="command">IndexOptions</code> controls the appearance of server generated directing listings, by adding icons, file descriptions, and so on. If <code class="command">Options Indexes</code> is set (refer to <a class="xref" href="#s2-apache-options" title="Options">Options</a>), the Web server generates a directory listing when the Web server receives an HTTP request for a directory without an index.
+ </div><div class="para">
+ First, the Web server looks in the requested directory for a file matching the names listed in the <code class="command">DirectoryIndex</code> directive (usually, <code class="filename">index.html</code>). If an <code class="filename">index.html</code> file is not found, Apache HTTP Server creates an HTML directory listing of the requested directory. The appearance of this directory listing is controlled, in part, by the <code class="command">IndexOptions</code> directive.
+ </div><div class="para">
+ The default configuration turns on <code class="command">FancyIndexing</code>. This means that a user can re-sort a directory listing by clicking on column headers. Another click on the same header switches from ascending to descending order. <code class="command">FancyIndexing</code> also shows different icons for different files, based upon file extensions.
+ </div><div class="para">
+ The <code class="command">AddDescription</code> option, when used in conjunction with <code class="command">FancyIndexing</code>, presents a short description for the file in server generated directory listings.
+ </div><div class="para">
+ <code class="command">IndexOptions</code> has a number of other parameters which can be set to control the appearance of server generated directories. The <code class="command">IconHeight</code> and <code class="command">IconWidth</code> parameters require the server to include HTML <code class="command">HEIGHT</code> and <code class="command">WIDTH</code> tags for the icons in server generated webpages. The <code class="command">IconsAreLinks</code> parameter combines the graphical icon with the HTML link anchor, which contains the URL link target.
+ </div><div class="formalpara" id="s2-apache-keepalive"><h5 class="formalpara">KeepAlive</h5><a id="id805200" class="indexterm"></a><a id="id805218" class="indexterm"></a><a id="id805241" class="indexterm"></a><a id="id1521491" class="indexterm"></a>
+ <code class="command">KeepAlive</code> sets whether the server allows more than one request per connection and can be used to prevent any one client from consuming too much of the server's resources.
+ </div><div class="para">
+ By default <code class="command">Keepalive</code> is set to <code class="command">off</code>. If <code class="command">Keepalive</code> is set to <code class="command">on</code> and the server becomes very busy, the server can quickly spawn the maximum number of child processes. In this situation, the server slows down significantly. If <code class="command">Keepalive</code> is enabled, it is a good idea to set the the <code class="command">KeepAliveTimeout</code> low (refer to <a class="xref" href="#s2-apache-keepalivetimeout" title="KeepAliveTimeout">KeepAliveTimeout</a> for more information about the <code class="command">KeepAliveTimeout</code> directive) and monitor the <code class="filename">/var/log/httpd/error_log</code> log file on the server. This log reports when the server is running out of child processes.
+ </div><div class="formalpara" id="s2-apache-keepalivetimeout"><h5 class="formalpara">KeepAliveTimeout</h5><a id="id1804039" class="indexterm"></a><a id="id1804057" class="indexterm"></a>
+ <code class="command">KeepAliveTimeout</code> sets the number of seconds the server waits after a request has been served before it closes the connection. Once the server receives a request, the <code class="command">Timeout</code> directive applies instead. The <code class="command">KeepAliveTimeout</code> directive is set to 15 seconds by default.
+ </div><div class="formalpara" id="s2-apache-languagepriority"><h5 class="formalpara">LanguagePriority</h5><a id="id1884890" class="indexterm"></a><a id="id1884909" class="indexterm"></a>
+ <code class="command">LanguagePriority</code> sets precedence for different languages in case the client Web browser has no language preference set.
+ </div><div class="formalpara" id="s2-apache-listen"><h5 class="formalpara">Listen</h5><a id="id669448" class="indexterm"></a><a id="id669466" class="indexterm"></a>
+ The <code class="command">Listen</code> command identifies the ports on which the Web server accepts incoming requests. By default, the Apache HTTP Server is set to listen to port 80 for non-secure Web communications and (in the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file which defines any secure servers) to port 443 for secure Web communications.
+ </div><div class="para">
+ If the Apache HTTP Server is configured to listen to a port under 1024, only the root user can start it. For port 1024 and above, <code class="command">httpd</code> can be started as a regular user.
+ </div><div class="para">
+ The <code class="command">Listen</code> directive can also be used to specify particular IP addresses over which the server accepts connections.
+ </div><div class="formalpara" id="s2-apache-loadmodule"><h5 class="formalpara">LoadModule</h5><a id="id818278" class="indexterm"></a><a id="id1002515" class="indexterm"></a>
+ <code class="command">LoadModule</code> is used to load Dynamic Shared Object (DSO) modules. More information on the Apache HTTP Server's DSO support, including instructions for using the <code class="command">LoadModule</code> directive, can be found in <a class="xref" href="#s1-apache-addmods" title="11.6. Adding Modules">Section 11.6, “Adding Modules”</a>. Note, the load order of the modules is <span class="emphasis"><em>no longer important</em></span> with Apache HTTP Server 2.0. Refer to <a class="xref" href="#s3-httpd-v2-mig-dso" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support">Section 11.2.2.1.3, “Dynamic Shared Object (DSO) Support”</a> for more information about Apache HTTP Server 2.0 DSO support.
+ </div><div class="formalpara" id="s2-apache-location"><h5 class="formalpara">Location</h5><a id="id689870" class="indexterm"></a><a id="id689888" class="indexterm"></a><a id="id689906" class="indexterm"></a>
+ The <code class="command"><Location></code> and <code class="command"></Location></code> tags create a container in which access control based on URL can be specified.
+ </div><div class="para">
+ For instance, to allow people connecting from within the server's domain to see status reports, use the following directives:
+ </div><pre class="screen">
+<code class="command"><Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from <em class="replaceable"><code><.example.com></code></em> </Location></code>
+</pre><div class="para">
+ Replace <em class="replaceable"><code><.example.com></code></em> with the second-level domain name for the Web server.
+ </div><div class="para">
+ To provide server configuration reports (including installed modules and configuration directives) to requests from inside the domain, use the following directives:
+ </div><pre class="screen">
+<code class="command"><Location /server-info> SetHandler server-info Order deny,allow Deny from all Allow from <em class="replaceable"><code><.example.com></code></em> </Location></code>
+</pre><div class="para">
+ Again, replace <em class="replaceable"><code><.example.com></code></em> with the second-level domain name for the Web server.
+ </div><div class="formalpara" id="s2-apache-logformat"><h5 class="formalpara">LogFormat</h5><a id="id1189886" class="indexterm"></a><a id="id1189904" class="indexterm"></a><a id="id1189927" class="indexterm"></a><a id="id624202" class="indexterm"></a>
+ The <code class="command">LogFormat</code> directive configures the format of the various Web server log files. The actual <code class="command">LogFormat</code> used depends on the settings given in the <code class="command">CustomLog</code> directive (refer to <a class="xref" href="#s2-apache-customlog" title="CustomLog">CustomLog</a>).
+ </div><div class="para">
+ The following are the format options if the <code class="command">CustomLog</code> directive is set to <code class="command">combined</code>:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">%h</code> (remote host's IP address or hostname) </span></dt><dd><div class="para">
+ Lists the remote IP address of the requesting client. If <code class="command">HostnameLookups</code> is set to <code class="option">on</code>, the client hostname is recorded unless it is not available from DNS.
+ </div></dd><dt><span class="term"> <code class="command">%l</code> (rfc931) </span></dt><dd><div class="para">
+ Not used. A hyphen <span class="keycap"><strong>-</strong></span> appears in the log file for this field.
+ </div></dd><dt><span class="term"> <code class="command">%u</code> (authenticated user) </span></dt><dd><div class="para">
+ Lists the username of the user recorded if authentication was required. Usually, this is not used, so a hyphen <span class="keycap"><strong>-</strong></span> appears in the log file for this field.
+ </div></dd><dt><span class="term"> <code class="command">%t</code> (date) </span></dt><dd><div class="para">
+ Lists the date and time of the request.
+ </div></dd><dt><span class="term"> <code class="command">%r</code> (request string) </span></dt><dd><div class="para">
+ Lists the request string exactly as it came from the browser or client.
+ </div></dd><dt><span class="term"> <code class="command">%s</code> (status) </span></dt><dd><div class="para">
+ Lists the HTTP status code which was returned to the client host.
+ </div></dd><dt><span class="term"> <code class="command">%b</code> (bytes) </span></dt><dd><div class="para">
+ Lists the size of the document.
+ </div></dd><dt><span class="term"> <code class="command">%\"%{Referer}i\"</code> (referrer) </span></dt><dd><div class="para">
+ Lists the URL of the webpage which referred the client host to Web server.
+ </div></dd><dt><span class="term"> <code class="command">%\"%{User-Agent}i\"</code> (user-agent) </span></dt><dd><div class="para">
+ Lists the type of Web browser making the request.
+ </div></dd></dl></div><div class="formalpara" id="s2-apache-loglevel"><h5 class="formalpara">LogLevel</h5><a id="id717744" class="indexterm"></a><a id="id717763" class="indexterm"></a>
+ <code class="command">LogLevel</code> sets how verbose the error messages in the error logs are. <code class="command">LogLevel</code> can be set (from least verbose to most verbose) to <code class="command">emerg</code>, <code class="command">alert</code>, <code class="command">crit</code>, <code class="command">error</code>, <code class="command">warn</code>, <code class="command">notice</code>, <code class="command">info</code>, or <code class="command">debug</code>. The default <code class="command">LogLevel</code> is <code class="command">warn</code>.
+ </div><div class="formalpara" id="s2-apache-maxkeepaliverequests"><h5 class="formalpara">MaxKeepAliveRequests</h5><a id="id907433" class="indexterm"></a><a id="id590764" class="indexterm"></a>
+ This directive sets the maximum number of requests allowed per persistent connection. The Apache Project recommends a high setting, which improves the server's performance. <code class="command">MaxKeepAliveRequests</code> is set to <code class="command">100</code> by default, which should be appropriate for most situations.
+ </div><div class="formalpara" id="s2-apache-namevirtualhost"><h5 class="formalpara">NameVirtualHost</h5><a id="id590812" class="indexterm"></a><a id="id802414" class="indexterm"></a>
+ The <code class="command">NameVirtualHost</code> directive associates an IP address and port number, if necessary, for any name-based virtual hosts. Name-based virtual hosting allows one Apache HTTP Server to serve different domains without using multiple IP addresses.
+ </div><div class="note"><h2>Note</h2><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 class="para">
+ To enable name-based virtual hosting, uncomment the <code class="command">NameVirtualHost</code> configuration directive and add the correct IP address. Then add additional <code class="command">VirtualHost</code> containers for each virtual host as is necessary for your configuration.
+ </div><div class="formalpara" id="s2-apache-options"><h5 class="formalpara">Options</h5><a id="id867651" class="indexterm"></a><a id="id867669" class="indexterm"></a><a id="id867688" class="indexterm"></a><a id="id568764" class="indexterm"></a>
+ The <code class="command">Options</code> directive controls which server features are available in a particular directory. For example, under the restrictive parameters specified for the root directory, <code class="command">Options</code> is only set to the <code class="command">FollowSymLinks</code> directive. No features are enabled, except that the server is allowed to follow symbolic links in the root directory.
+ </div><div class="para">
+ By default, in the <code class="command">DocumentRoot</code> directory, <code class="command">Options</code> is set to include <code class="command">Indexes</code> and <code class="command">FollowSymLinks</code>. <code class="command">Indexes</code> permits the server to generate a directory listing for a directory if no <code class="command">DirectoryIndex</code> (for example, <code class="filename">index.html</code>) is specified. <code class="command">FollowSymLinks</code> allows the server to follow symbolic links in that directory.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ <code class="command">Options</code> statements from the main server configuration section need to be replicated to each <code class="command">VirtualHost</code> container individually. Refer to <a class="xref" href="#s2-apache-virtualhost" title="VirtualHost">VirtualHost</a> for more information.
+ </div></div><div class="formalpara" id="s2-apache-order"><h5 class="formalpara">Order</h5><a id="id590098" class="indexterm"></a><a id="id555517" class="indexterm"></a>
+ The <code class="command">Order</code> directive controls the order in which <code class="command">allow</code> and <code class="command">deny</code> directives are evaluated. The server is configured to evaluate the <code class="command">Allow</code> directives before the <code class="command">Deny</code> directives for the <code class="command">DocumentRoot</code> directory.
+ </div><div class="formalpara" id="s2-apache-pidfile"><h5 class="formalpara">PidFile</h5><a id="id590342" class="indexterm"></a><a id="id590360" class="indexterm"></a>
+ <code class="command">PidFile</code> names the file where the server records its process ID (PID). By default the PID is listed in <code class="filename">/var/run/httpd.pid</code>.
+ </div><div class="formalpara" id="s2-apache-proxy"><h5 class="formalpara">Proxy</h5><a id="id590150" class="indexterm"></a><a id="id590168" class="indexterm"></a>
+ <code class="command"><Proxy *></code> and <code class="command"></Proxy></code> tags create a container which encloses a group of configuration directives meant to apply only to the proxy server. Many directives which are allowed within a <code class="command"><Directory></code> container may also be used within <code class="command"><Proxy></code> container.
+ </div><div class="formalpara" id="s2-apache-proxyrequests"><h5 class="formalpara">ProxyRequests</h5><a id="id568480" class="indexterm"></a><a id="id568499" class="indexterm"></a><a id="id568517" class="indexterm"></a>
+ To configure the Apache HTTP Server to function as a proxy server, remove the hash mark (<code class="command">#</code>) from the beginning of the <code class="command"><IfModule mod_proxy.c></code> line, the ProxyRequests, and each line in the <code class="command"><Proxy></code> stanza. Set the <code class="command">ProxyRequests</code> directive to <code class="command">On</code>, and set which domains are allowed access to the server in the <code class="command">Allow from</code> directive of the <code class="command"><Proxy></code> stanza.
+ </div><div class="formalpara" id="s2-apache-readmename"><h5 class="formalpara">ReadmeName</h5><a id="id809198" class="indexterm"></a><a id="id741720" class="indexterm"></a>
+ <code class="command">ReadmeName</code> names the file which, if it exists in the directory, is appended to the end of server generated directory listings. The Web server first tries to include the file as an HTML document and then tries to include it as plain text. By default, <code class="command">ReadmeName</code> is set to <code class="filename">README.html</code>.
+ </div><div class="formalpara" id="s2-apache-redirect"><h5 class="formalpara">Redirect</h5><a id="id741773" class="indexterm"></a><a id="id787440" class="indexterm"></a>
+ When a webpage is moved, <code class="command">Redirect</code> can be used to map the file location to a new URL. The format is as follows:
+ </div><pre class="screen">
+<code class="command">Redirect /<em class="replaceable"><code><old-path></code></em>/<em class="replaceable"><code><file-name></code></em> http://<em class="replaceable"><code><current-domain></code></em>/<em class="replaceable"><code><current-path></code></em>/<em class="replaceable"><code><file-name></code></em> </code>
+</pre><div class="para">
+ In this example, replace <em class="replaceable"><code><old-path></code></em> with the old path information for <em class="replaceable"><code><file-name></code></em> and <em class="replaceable"><code><current-domain></code></em> and <em class="replaceable"><code><current-path></code></em> with the current domain and path information for <em class="replaceable"><code><file-name></code></em>.
+ </div><div class="para">
+ In this example, any requests for <em class="replaceable"><code><file-name></code></em> at the old location is automatically redirected to the new location.
+ </div><div class="para">
+ For more advanced redirection techniques, use the <code class="command">mod_rewrite</code> module included with the Apache HTTP Server. For more information about configuring the <code class="command">mod_rewrite</code> module, refer to the Apache Software Foundation documentation online at <a href="http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html"> http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html</a>.
+ </div><div class="formalpara" id="s2-apache-scriptalias"><h5 class="formalpara">ScriptAlias</h5><a id="id798188" class="indexterm"></a><a id="id798206" class="indexterm"></a>
+ The <code class="command">ScriptAlias</code> directive defines where CGI scripts are located. Generally, it is not good practice to leave CGI scripts within the <code class="command">DocumentRoot</code>, where they can potentially be viewed as text documents. For this reason, a special directory outside of the <code class="command">DocumentRoot</code> directory containing server-side executables and scripts is designated by the <code class="command">ScriptAlias</code> directive. This directory is known as a <code class="filename">cgi-bin</code> and is set to <code class="filename">/var/www/cgi-bin/</code> by default.
+ </div><div class="para">
+ It is possible to establish directories for storing executables outside of the <code class="filename">cgi-bin/</code> directory. For instructions on doing so, refer to <a class="xref" href="#s2-apache-addhandler" title="AddHandler">AddHandler</a> and <a class="xref" href="#s2-apache-directory" title="Directory">Directory</a>.
+ </div><div class="formalpara" id="s2-apache-serveradmin"><h5 class="formalpara">ServerAdmin</h5><a id="id1018908" class="indexterm"></a><a id="id764264" class="indexterm"></a><a id="id764282" class="indexterm"></a>
+ Sets the <code class="command">ServerAdmin</code> directive to the email address of the Web server administrator. This email address shows up in error messages on server-generated Web pages, so users can report a problem by sending email to the server administrator.
+ </div><div class="para">
+ By default, <code class="command">ServerAdmin</code> is set to <code class="command">root at localhost</code>.
+ </div><div class="para">
+ A common way to set up <code class="command">ServerAdmin</code> is to set it to <code class="command">webmaster at example.com</code>. Once set, alias <code class="command">webmaster</code> to the person responsible for the Web server in <code class="filename">/etc/aliases</code> and run <code class="command">/usr/bin/newaliases</code>.
+ </div><div class="formalpara" id="s2-apache-servername"><h5 class="formalpara">ServerName</h5><a id="id997587" class="indexterm"></a><a id="id997606" class="indexterm"></a>
+ <code class="command">ServerName</code> specifies a hostname and port number (matching the <code class="command">Listen</code> directive) for the server. The <code class="command">ServerName</code> does not need to match the machine's actual hostname. For example, the Web server may be <code class="computeroutput">www.example.com</code>, but the server's hostname is actually <code class="computeroutput">foo.example.com</code>. The value specified in <code class="command">ServerName</code> must be a valid Domain Name Service (DNS) name that can be resolved by the system — do not make something up.
+ </div><div class="para">
+ The following is a sample <code class="command">ServerName</code> directive:
+ </div><pre class="screen">
+<code class="command">ServerName www.example.com:80</code>
+</pre><div class="para">
+ When specifying a <code class="command">ServerName</code>, be sure the IP address and server name pair are included in the <code class="filename">/etc/hosts</code> file.
+ </div><div class="formalpara" id="s2-apache-serverroot"><h5 class="formalpara">ServerRoot</h5><a id="id1012564" class="indexterm"></a><a id="id1012583" class="indexterm"></a>
+ The <code class="command">ServerRoot</code> directive specifies the top-level directory containing website content. By default, <code class="command">ServerRoot</code> is set to <code class="filename">"/etc/httpd"</code> for both secure and non-secure servers.
+ </div><div class="formalpara" id="s2-apache-serversignature"><h5 class="formalpara">ServerSignature</h5><a id="id642580" class="indexterm"></a><a id="id642598" class="indexterm"></a>
+ The <code class="command">ServerSignature</code> directive adds a line containing the Apache HTTP Server server version and the <code class="command">ServerName</code> to any server-generated documents, such as error messages sent back to clients. <code class="command">ServerSignature</code> is set to <code class="command">on</code> by default.
+ </div><div class="para">
+ <code class="command">ServerSignature</code> can be set to <code class="command">EMail</code> which adds a <code class="command">mailto:ServerAdmin</code> HTML tag to the signature line of auto-generated responses. <code class="command">ServerSignature</code> can also be set to <code class="command">Off</code> to stop Apache from sending out its version number and module information. Please also check the <code class="command">ServerTokens</code> settings.
+ </div><div class="formalpara" id="s2-apache-servertoken"><h5 class="formalpara">ServerTokens</h5><a id="id809552" class="indexterm"></a><a id="id1189948" class="indexterm"></a>
+ The <code class="command">ServerTokens</code> directive determines if the Server response header field sent back to clients should include details of the Operating System type and information about compiled-in modules. By default, <code class="command">ServerTokens</code> is set to <code class="command">Full</code> which sends information about the Operating System type and compiled-in modules. Setting the <code class="command">ServerTokens</code> to <code class="command">Prod</code> sends the product name only and is recommended as many hackers check information in the Server header when scanning for vulnerabilities. You can also set the <code class="command">ServerTokens</code> to <code class="command">Min</code> (minimal) or to <code class="command">OS</code> (operating system).
+ </div><div class="formalpara" id="s2-apache-suexecusergroup"><h5 class="formalpara">SuexecUserGroup</h5><a id="id676308" class="indexterm"></a><a id="id676330" class="indexterm"></a><a id="id676348" class="indexterm"></a>
+ The <code class="command">SuexecUserGroup</code> directive, which originates from the <code class="command">mod_suexec</code> module, allows the specification of user and group execution privileges for CGI programs. Non-CGI requests are still processed with the user and group specified in the <code class="command">User</code> and <code class="command">Group</code> directives.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ From version 2.0, the <code class="command">SuexecUserGroup</code> directive replaced the Apache HTTP Server 1.3 configuration of using the <code class="command">User</code> and <code class="command">Group</code> directives inside the configuration of <code class="command">VirtualHosts</code> sections.
+ </div></div><div class="formalpara" id="s2-apache-timeout"><h5 class="formalpara">Timeout</h5><a id="id692910" class="indexterm"></a><a id="id692928" class="indexterm"></a>
+ <code class="command">Timeout</code> defines, in seconds, the amount of time that the server waits for receipts and transmissions during communications. <code class="command">Timeout</code> is set to <code class="command">300</code> seconds by default, which is appropriate for most situations.
+ </div><div class="formalpara" id="s2-apache-typesconfig"><h5 class="formalpara">TypesConfig</h5><a id="id1768939" class="indexterm"></a><a id="id1768957" class="indexterm"></a>
+ <code class="command">TypesConfig</code> names the file which sets the default list of MIME type mappings (file name extensions to content types). The default <code class="command"> TypesConfig</code> file is <code class="filename">/etc/mime.types</code>. Instead of editing <code class="filename">/etc/mime.types</code>, the recommended way to add MIME type mappings is to use the <code class="command"> AddType</code> directive.
+ </div><div class="para">
+ For more information about <code class="command">AddType</code>, refer to <a class="xref" href="#s2-apache-addtype" title="AddType">AddType</a>.
+ </div><div class="formalpara" id="s2-apache-usecanonicalname"><h5 class="formalpara">UseCanonicalName</h5><a id="id960894" class="indexterm"></a><a id="id960912" class="indexterm"></a>
+ When set to <code class="option">on</code>, this directive configures the Apache HTTP Server to reference itself using the value specified in the <code class="command">ServerName</code> and <code class="command">Port</code> directives. When <code class="command">UseCanonicalName</code> is set to <code class="option">off</code>, the server instead uses the value used by the requesting client when referring to itself.
+ </div><div class="para">
+ <code class="command">UseCanonicalName</code> is set to <code class="option">off</code> by default.
+ </div><div class="formalpara" id="s2-apache-user"><h5 class="formalpara">User</h5><a id="id880679" class="indexterm"></a><a id="id880698" class="indexterm"></a>
+ The <code class="command">User</code> directive sets the username of the server process and determines what files the server is allowed to access. Any files inaccessible to this user are also inaccessible to clients connecting to the Apache HTTP Server.
+ </div><div class="para">
+ By default <code class="command">User</code> is set to <code class="command">apache</code>.
+ </div><div class="para">
+ This directive has been deprecated for the configuration of virtual hosts.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ For security reasons, the Apache HTTP Server does not run as the root user.
+ </div></div><div class="formalpara" id="s2-apache-userdir"><h5 class="formalpara">UserDir</h5><a id="id578568" class="indexterm"></a><a id="id578586" class="indexterm"></a><a id="id955928" class="indexterm"></a><a id="id955943" class="indexterm"></a>
+ <code class="command">UserDir</code> is the subdirectory within each user's home directory where they should place personal HTML files which are served by the Web server. This directive is set to <code class="option"> disable</code> by default.
+ </div><div class="para">
+ The name for the subdirectory is set to <code class="filename">public_html</code> in the default configuration. For example, the server might receive the following request:
+ </div><pre class="screen">
+<code class="command">http://<em class="replaceable"><code>example.com</code></em>/~<em class="replaceable"><code>username</code></em>/foo.html</code>
+</pre><div class="para">
+ The server would look for the file:
+ </div><pre class="screen">
+<code class="filename">/home/username/public_html/foo.html</code>
+</pre><div class="para">
+ In the above example, <code class="filename">/home/username/</code> is the user's home directory (note that the default path to users' home directories may vary).
+ </div><div class="para">
+ Make sure that the permissions on the users' home directories are set correctly. Users' home directories must be set to 0711. The read (r) and execute (x) bits must be set on the users' <code class="filename">public_html</code> directories (0755 also works). Files that are served in a users' <code class="filename">public_html</code> directories must be set to at least 0644.
+ </div><div class="formalpara" id="s2-apache-virtualhost"><h5 class="formalpara">VirtualHost</h5><a id="id908744" class="indexterm"></a><a id="id744337" class="indexterm"></a>
+ <code class="command"><VirtualHost></code> and <code class="command"></VirtualHost></code> tags create a container outlining the characteristics of a virtual host. The <code class="command">VirtualHost</code> container accepts most configuration directives.
+ </div><div class="para">
+ A commented <code class="command">VirtualHost</code> container is provided in <code class="filename">httpd.conf</code>, which illustrates the minimum set of configuration directives necessary for each virtual host. Refer to <a class="xref" href="#s1-apache-virtualhosts" title="11.7. Virtual Hosts">Section 11.7, “Virtual Hosts”</a> for more information about virtual hosts.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ The default SSL virtual host container now resides in the file <code class="filename">/etc/httpd/conf.d/ssl.conf</code>.
+ </div></div></div><div class="section" title="11.5.2. Configuration Directives for SSL" id="s2-apache-sslcommands"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-sslcommands">11.5.2. Configuration Directives for SSL</h3></div></div></div><a id="id643546" class="indexterm"></a><a id="id643556" class="indexterm"></a><div class="para">
+ The directives in <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file can be configured to enable secure Web communications using SSL and TLS.
+ </div><div class="formalpara" id="s3-apache-setenvif"><h5 class="formalpara">SetEnvIf</h5><a id="id977890" class="indexterm"></a><a id="id977908" class="indexterm"></a>
+ <code class="command">SetEnvIf</code> sets environment variables based on the headers of incoming connections. It is <span class="emphasis"><em>not</em></span> solely an SSL directive, though it is present in the supplied <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file. It's purpose in this context is to disable HTTP keepalive and to allow SSL to close the connection without a closing notification from the client browser. This setting is necessary for certain browsers that do not reliably shut down the SSL connection.
+ </div><div class="para">
+ For more information on other directives within the SSL configuration file, refer to the following URLs:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ http://localhost/manual/mod/mod_ssl.html
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html">http://httpd.apache.org/docs/2.2/mod/mod_ssl.html</a>
+ </div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
+ In most cases, SSL directives are configured appropriately during the installation of Fedora. Be careful when altering Apache HTTP Secure Server directives, misconfiguration can lead to security vulnerabilities.
+ </div></div></div><div class="section" title="11.5.3. MPM Specific Server-Pool Directives" id="s2-apache-mpm-containers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mpm-containers">11.5.3. MPM Specific Server-Pool Directives</h3></div></div></div><a id="id910361" class="indexterm"></a><div class="para">
+ As explained in <a class="xref" href="#s3-httpd-v2-mig-pool" title="11.2.2.1.2. Server-Pool Size Regulation">Section 11.2.2.1.2, “Server-Pool Size Regulation”</a>, the responsibility for managing characteristics of the server-pool falls to a module group called MPMs under Apache HTTP Server 2.0. The characteristics of the server-pool differ depending upon which MPM is used. For this reason, an <code class="command">IfModule</code> container is necessary to define the server-pool for the MPM in use.
+ </div><div class="para">
+ By default, Apache HTTP Server 2.0 defines the server-pool for both the <code class="command">prefork</code> and <code class="command">worker</code> MPMs.
+ </div><div class="para">
+ The following section list directives found within the MPM-specific server-pool containers.
+ </div><div class="formalpara" id="s3-apache-maxclients"><h5 class="formalpara">MaxClients</h5><a id="id1934760" class="indexterm"></a><a id="id1032432" class="indexterm"></a>
+ <code class="command">MaxClients</code> sets a limit on the total number of server processes, or simultaneously connected clients, that can run at one time. The main purpose of this directive is to keep a runaway Apache HTTP Server from crashing the operating system. For busy servers this value should be set to a high value. The server's default is set to 150 regardless of the MPM in use. However, it is not recommended that the value for <code class="command">MaxClients</code> exceeds <code class="command">256</code> when using the <code class="command">prefork</code> MPM.
+ </div><div class="formalpara" id="s3-apache-maxrequestsperchild"><h5 class="formalpara">MaxRequestsPerChild</h5><a id="id818582" class="indexterm"></a><a id="id818600" class="indexterm"></a>
+ <code class="command">MaxRequestsPerChild</code> sets the total number of requests each child server process serves before the child dies. The main reason for setting <code class="command">MaxRequestsPerChild</code> is to avoid long-lived process induced memory leaks. The default <code class="command">MaxRequestsPerChild</code> for the <code class="command">prefork</code> MPM is <code class="command">4000</code> and for the <code class="command">worker</code> MPM is <code class="command">0</code>.
+ </div><div class="formalpara" id="s3-apache-minmaxspareservers"><h5 class="formalpara">MinSpareServers and MaxSpareServers</h5><a id="id866596" class="indexterm"></a><a id="id866614" class="indexterm"></a><a id="id866633" class="indexterm"></a><a id="id873376" class="indexterm"></a>
+ These values are only used with the <code class="command">prefork</code> MPM. They adjust how the Apache HTTP Server dynamically adapts to the perceived load by maintaining an appropriate number of spare server processes based on the number of incoming requests. The server checks the number of servers waiting for a request and kills some if there are more than <code class="command">MaxSpareServers</code> or creates some if the number of servers is less than <code class="command">MinSpareServers</code>.
+ </div><div class="para">
+ The default <code class="command">MinSpareServers</code> value is <code class="command">5</code>; the default <code class="command">MaxSpareServers</code> value is <code class="command">20</code>. These default settings should be appropriate for most situations. Be careful not to increase the <code class="command">MinSpareServers</code> to a large number as doing so creates a heavy processing load on the server even when traffic is light.
+ </div><div class="formalpara" id="s3-apache-minmaxsparethreads"><h5 class="formalpara">MinSpareThreads and MaxSpareThreads</h5><a id="id662168" class="indexterm"></a><a id="id662186" class="indexterm"></a><a id="id771549" class="indexterm"></a><a id="id771567" class="indexterm"></a>
+ These values are only used with the <code class="command">worker</code> MPM. They adjust how the Apache HTTP Server dynamically adapts to the perceived load by maintaining an appropriate number of spare server threads based on the number of incoming requests. The server checks the number of server threads waiting for a request and kills some if there are more than <code class="command">MaxSpareThreads</code> or creates some if the number of servers is less than <code class="command">MinSpareThreads</code>.
+ </div><div class="para">
+ The default <code class="command">MinSpareThreads</code> value is <code class="command">25</code>; the default <code class="command">MaxSpareThreads</code> value is <code class="command">75</code>. These default settings should be appropriate for most situations. The value for <code class="command">MaxSpareThreads</code> must be greater than or equal to the sum of <code class="command">MinSpareThreads</code> and <code class="command">ThreadsPerChild</code>, else the Apache HTTP Server automatically corrects it.
+ </div><div class="formalpara" id="s3-apache-startservers"><h5 class="formalpara">StartServers</h5><a id="id1119041" class="indexterm"></a><a id="id1119059" class="indexterm"></a>
+ The <code class="command">StartServers</code> directive sets how many server processes are created upon startup. Since the Web server dynamically kills and creates server processes based on traffic load, it is not necessary to change this parameter. The Web server is set to start <code class="command">8</code> server processes at startup for the <code class="command">prefork</code> MPM and <code class="command">2</code> for the <code class="command">worker</code> MPM.
+ </div><div class="formalpara" id="s3-apache-threadsperchild"><h5 class="formalpara">ThreadsPerChild</h5><a id="id898845" class="indexterm"></a><a id="id613927" class="indexterm"></a>
+ This value is only used with the <code class="command">worker</code> MPM. It sets the number of threads within each child process. The default value for this directive is <code class="command">25</code>.
+ </div></div></div><div class="section" title="11.6. Adding Modules" id="s1-apache-addmods"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-addmods">11.6. Adding Modules</h2></div></div></div><a id="id613976" class="indexterm"></a><a id="id777336" class="indexterm"></a><a id="id777350" class="indexterm"></a><a id="id777365" class="indexterm"></a><a id="id777375" class="indexterm"></a><div class="para">
+ The Apache HTTP Server is distributed with a number of modules. More information about Apache HTTP modules can be found on <a href="http://httpd.apache.org/docs/2.2/mod/">http://httpd.apache.org/docs/2.2/mod/</a>.
+ </div><div class="para">
+ The Apache HTTP Server supports <em class="firstterm">Dynamically Shared Objects</em> (<em class="firstterm">DSO</em>s), or modules, which can easily be loaded at runtime as necessary.
+ </div><div class="para">
+ The Apache Project provides complete DSO documentation online at <a href="http://httpd.apache.org/docs/2.2/dso.html">http://httpd.apache.org/docs/2.2/dso.html</a>. Or, if the <code class="filename">http-manual</code> package is installed, documentation about DSOs can be found online at <a href="http://localhost/manual/mod/">http://localhost/manual/mod/</a>.
+ </div><div class="para">
+ For the Apache HTTP Server to use a DSO, it must be specified in a <code class="command">LoadModule</code> directive within <code class="filename">/etc/httpd/conf/httpd.conf</code>. If the module is provided by a separate package, the line must appear within the modules configuration file in the <code class="filename">/etc/httpd/conf.d/</code> directory. Refer to <a class="xref" href="#s2-apache-loadmodule" title="LoadModule">LoadModule</a> for more information.
+ </div><div class="para">
+ If adding or deleting modules from <code class="filename">http.conf</code>, Apache HTTP Server must be reloaded or restarted, as referred to in <a class="xref" href="#s1-apache-startstop" title="11.3. Starting and Stopping httpd">Section 11.3, “Starting and Stopping <code class="command">httpd</code> ”</a>.
+ </div><div class="para">
+ If creating a new module, first install the <code class="filename">httpd-devel</code> package which contains the include files, the header files, as well as the <em class="firstterm">APache eXtenSion</em> (<code class="command">/usr/sbin/apxs</code>) application, which uses the include files and the header files to compile DSOs.
+ </div><div class="para">
+ After writing a module, use <code class="command">/usr/sbin/apxs</code> to compile the module sources outside the Apache source tree. For more information about using the <code class="command">/usr/sbin/apxs</code> command, refer to the the Apache documentation online at <a href="http://httpd.apache.org/docs/2.2/dso.html">http://httpd.apache.org/docs/2.2/dso.html</a> as well as the <code class="command">apxs</code> man page.
+ </div><div class="para">
+ Once compiled, put the module in the <code class="filename">/usr/lib/httpd/modules/</code> directory. For 64-bit Fedora hosts using the defaut 64-bit user-space, this path will be <code class="filename">/usr/lib64/httpd/modules/</code>. Then add a <code class="command">LoadModule</code> line to the <code class="filename">httpd.conf</code>, using the following structure:
+ </div><pre class="screen">
+<code class="command">LoadModule <em class="replaceable"><code><module-name> <path/to/module.so></code></em> </code>
+</pre><div class="para">
+ Where <em class="replaceable"><code><module-name></code></em> is the name of the module and <em class="replaceable"><code><path/to/module.so></code></em> is the path to the DSO.
+ </div></div><div class="section" title="11.7. Virtual Hosts" id="s1-apache-virtualhosts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-virtualhosts">11.7. Virtual Hosts</h2></div></div></div><a id="id695635" class="indexterm"></a><a id="id695649" class="indexterm"></a><a id="id1010011" class="indexterm"></a><a id="id1010025" class="indexterm"></a><a id="id1010040" class="indexterm"></a><a id="id1010058" 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. A complete guide to using virtual hosts is available online at <a href="http://httpd.apache.org/docs/2.2/vhosts/">http://httpd.apache.org/docs/2.2/vhosts/</a>.
+ </div><div class="section" title="11.7.1. Setting Up Virtual Hosts" id="s2-apache-settingupvhosts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-settingupvhosts">11.7.1. Setting Up Virtual Hosts</h3></div></div></div><div class="para">
+ To create a name-based virtual host, it is best to use the virtual host container provided in <code class="filename">httpd.conf</code> as an example.
+ </div><div class="para">
+ The virtual host example read as follows:
+ </div><pre class="screen">#<VirtualHost *:80>
+# ServerAdmin webmaster at dummy-host.example.com
+# DocumentRoot /www/docs/dummy-host.example.com
+# ServerName dummy-host.example.com
+# ErrorLog logs/dummy-host.example.com-error_log
+# CustomLog logs/dummy-host.example.com-access_log common
+#</VirtualHost></pre><pre class="screen">#NameVirtualHost *:80
+#
+#<VirtualHost *:80>
+# ServerAdmin webmaster at dummy-host.example.com
+# DocumentRoot /www/docs/dummy-host.example.com
+# ServerName dummy-host.example.com
+# ErrorLog logs/dummy-host.example.com-error_log
+# CustomLog logs/dummy-host.example.com-access_log common #</VirtualHost></pre><div class="para">
+ To activate name-based virtual hosting, uncomment the <code class="command">NameVirtualHost</code> line by removing the hash mark (<code class="command">#</code>) and replace the asterisk (<code class="command">*</code>) with the IP address assigned to the machine.
+ </div><div class="para">
+ Next, configure a virtual host by uncommenting and customizing the <code class="command"><VirtualHost></code> container.
+ </div><div class="para">
+ On the <code class="command"><VirtualHost></code> line, change the asterisk (<code class="command">*</code>) to the server's IP address. Change the <code class="command">ServerName</code> to a <span class="emphasis"><em>valid</em></span> DNS name assigned to the machine, and configure the other directives as necessary.
+ </div><div class="para">
+ The <code class="command"><VirtualHost></code> container is highly customizable and accepts almost every directive available within the main server configuration.
+ </div><a id="id1713355" class="indexterm"></a><div class="note"><h2>Tip</h2><div class="para">
+ If configuring a virtual host to listen on a non-default port, that port must be added to the <code class="command">Listen</code> directive in the global settings section of <code class="filename">/etc/httpd/conf/httpd.conf</code> file.
+ </div></div><div class="para">
+ To activate a newly created virtual host, the Apache HTTP Server must be reloaded or restarted. Refer to <a class="xref" href="#s1-apache-startstop" title="11.3. Starting and Stopping httpd">Section 11.3, “Starting and Stopping <code class="command">httpd</code> ”</a> for further instructions.
+ </div><div class="para">
+ Comprehensive information about creating and configuring both name-based and IP address-based virtual hosts is provided online at <a href="http://httpd.apache.org/docs/2.2/vhosts/">http://httpd.apache.org/docs/2.2/vhosts/</a>.
+ </div></div></div><div class="section" title="11.8. Apache HTTP Secure Server Configuration" id="s1-httpd-secure-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-httpd-secure-server">11.8. Apache HTTP Secure Server Configuration</h2></div></div></div><a id="id872725" class="indexterm"></a><div class="para">
+ This section provides basic information on the Apache HTTP Server with the <code class="filename">mod_ssl</code> security module enabled to use the OpenSSL library and toolkit. The combination of these three components are referred to in this section as the secure Web server or just as the secure server.
+ </div><div class="para">
+ The <code class="filename">mod_ssl</code> module is a security module for the Apache HTTP Server. The <code class="filename">mod_ssl</code> module uses the tools provided by the OpenSSL Project to add a very important feature to the Apache HTTP Server — the ability to encrypt communications. In contrast, regular HTTP communications between a browser and a Web server are sent in plain text, which could be intercepted and read by someone along the route between the browser and the server.
+ </div><div class="para">
+ This section is not meant to be complete and exclusive documentation for any of these programs. When possible, this guide points to appropriate places where you can find more in-depth documentation on particular subjects.
+ </div><div class="para">
+ This section shows you how to install these programs. You can also learn the steps necessary to generate a private key and a certificate request, how to generate your own self-signed certificate, and how to install a certificate to use with your secure server.
+ </div><div class="para">
+ The <code class="filename">mod_ssl</code> configuration file is located at <code class="filename">/etc/httpd/conf.d/ssl.conf</code>. For this file to be loaded, and hence for <code class="filename">mod_ssl</code> to work, you must have the statement <code class="computeroutput">Include conf.d/*.conf</code> in the <code class="filename">/etc/httpd/conf/httpd.conf</code> file. This statement is included by default in the default Apache HTTP Server configuration file.
+ </div><div class="section" title="11.8.1. An Overview of Security-Related Packages" id="s2-secureserver-optionalpackages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-secureserver-optionalpackages">11.8.1. An Overview of Security-Related Packages</h3></div></div></div><a id="id1681429" class="indexterm"></a><div class="para">
+ To enable the secure server, you must have the following packages installed at a minimum:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="filename">httpd</code> </span></dt><dd><div class="para">
+ The <code class="filename">httpd</code> package contains the <code class="command">httpd</code> daemon and related utilities, configuration files, icons, Apache HTTP Server modules, man pages, and other files used by the Apache HTTP Server.
+ </div></dd><dt><span class="term"> <code class="filename">mod_ssl</code> </span></dt><dd><div class="para">
+ The <code class="filename">mod_ssl</code> package includes the <code class="filename">mod_ssl</code> module, which provides strong cryptography for the Apache HTTP Server via the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols.
+ </div></dd><dt><span class="term"> <code class="filename">openssl</code> </span></dt><dd><div class="para">
+ The <code class="filename">openssl</code> package contains the OpenSSL toolkit. The OpenSSL toolkit implements the SSL and TLS protocols, and also includes a general purpose cryptography library.
+ </div></dd></dl></div><div class="para">
+ Additionally, other software packages provide certain security functionalities (but are not required by the secure server to function):
+ </div></div><div class="section" title="11.8.2. An Overview of Certificates and Security" id="s2-secureserver-overview-certs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-secureserver-overview-certs">11.8.2. An Overview of Certificates and Security</h3></div></div></div><a id="id977869" class="indexterm"></a><a id="id1209417" class="indexterm"></a><a id="id1209432" class="indexterm"></a><a id="id1209446" class="indexterm"></a><div class="para">
+ Your secure server provides security using a combination of the Secure Sockets Layer (SSL) protocol and (in most cases) a digital certificate from a Certificate Authority (CA). SSL handles the encrypted communications as well as the mutual authentication between browsers and your secure server. The CA-approved digital certificate provides authentication for your secure server (the CA puts its reputation behind its certification of your organization's identity). When your browser is communicating using SSL encryption, the <code class="computeroutput">https://</code> prefix is used at the beginning of the Uniform Resource Locator (URL) in the navigation bar.
+ </div><div class="para">
+ Encryption depends upon the use of keys (think of them as secret encoder/decoder rings in data format). In conventional or symmetric cryptography, both ends of the transaction have the same key, which they use to decode each other's transmissions. In public or asymmetric cryptography, two keys co-exist: a public key and a private key. A person or an organization keeps their private key a secret and publishes their public key. Data encoded with the public key can only be decoded with the private key; data encoded with the private key can only be decoded with the public key.
+ </div><div class="para">
+ To set up your secure server, use public cryptography to create a public and private key pair. In most cases, you send your certificate request (including your public key), proof of your company's identity, and payment to a CA. The CA verifies the certificate request and your identity, and then sends back a certificate for your secure server.
+ </div><div class="para">
+ A secure server uses a certificate to identify itself to Web browsers. You can generate your own certificate (called a "self-signed" certificate), or you can get a certificate from a CA. A certificate from a reputable CA guarantees that a website is associated with a particular company or organization.
+ </div><div class="para">
+ Alternatively, you can create your own self-signed certificate. Note, however, that self-signed certificates should not be used in most production environments. Self-signed certificates are not automatically accepted by a user's browser — users are prompted by the browser to accept the certificate and create the secure connection. Refer to <a class="xref" href="#s2-secureserver-certs" title="11.8.4. Types of Certificates">Section 11.8.4, “Types of Certificates”</a> for more information on the differences between self-signed and CA-signed certificates.
+ </div><div class="para">
+ Once you have a self-signed certificate or a signed certificate from the CA of your choice, you must install it on your secure server.
+ </div></div><div class="section" title="11.8.3. Using Pre-Existing Keys and Certificates" id="s1-secureserver-oldcert"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-secureserver-oldcert">11.8.3. Using Pre-Existing Keys and Certificates</h3></div></div></div><a id="id862996" class="indexterm"></a><div class="para">
+ If you already have an existing key and certificate (for example, if you are installing the secure server to replace another company's secure server product), you can probably use your existing key and certificate with the secure server. The following two situations provide instances where you are not able to use your existing key and certificate:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>If you are changing your IP address or domain name</em></span> — Certificates are issued for a particular IP address and domain name pair. You must get a new certificate if you are changing your IP address or domain name.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id786045" class="indexterm"></a>
+ <span class="emphasis"><em>If you have a certificate from VeriSign and you are changing your server software</em></span> — VeriSign is a widely used CA. If you already have a VeriSign certificate for another purpose, you may have been considering using your existing VeriSign certificate with your new secure server. However, you are not be allowed to because VeriSign issues certificates for one specific server software and IP address/domain name combination.
+ </div><div class="para">
+ If you change either of those parameters (for example, if you previously used a different secure server product), the VeriSign certificate you obtained to use with the previous configuration will not work with the new configuration. You must obtain a new certificate.
+ </div></li></ul></div><div class="para">
+ If you have an existing key and certificate that you can use, you do not have to generate a new key and obtain a new certificate. However, you may need to move and rename the files which contain your key and certificate.
+ </div><div class="para">
+ Move your existing key file to:
+ </div><pre class="screen">
+<code class="filename">/etc/pki/tls/private/server.key</code>
+</pre><div class="para">
+ Move your existing certificate file to:
+ </div><pre class="screen">
+<code class="filename">/etc/pki/tls/certs/server.crt</code>
+</pre><div class="para">
+ <a id="id740047" class="indexterm"></a>
+ <a id="id740061" class="indexterm"></a>
+ If you are upgrading from the Red Hat Secure Web Server, your old key (<code class="filename">httpsd.key</code>) and certificate (<code class="filename">httpsd.crt</code>) are located in <code class="filename">/etc/httpd/conf/</code>. Move and rename your key and certificate so that the secure server can use them. Use the following two commands to move and rename your key and certificate files:
+ </div><pre class="screen">
+<code class="command">mv /etc/httpd/conf/httpsd.key /etc/pki/tls/private/server.key mv /etc/httpd/conf/httpsd.crt /etc/pki/tls/certs/server.crt</code>
+</pre><div class="para">
+ Then, start your secure server with the command:
+ </div><pre class="screen">
+<code class="command">/sbin/service httpd start</code>
+</pre></div><div class="section" title="11.8.4. Types of Certificates" id="s2-secureserver-certs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-secureserver-certs">11.8.4. Types of Certificates</h3></div></div></div><a id="id922911" class="indexterm"></a><div class="para">
+ If you installed your secure server from the RPM package provided by Red Hat, a randomly generated private key and a test certificate are generated and put into the appropriate directories. Before you begin using your secure server, however, you must generate your own key and obtain a certificate which correctly identifies your server.
+ </div><div class="para">
+ You need a key and a certificate to operate your secure server — which means that you can either generate a self-signed certificate or purchase a CA-signed certificate from a CA. What are the differences between the two?
+ </div><div class="para">
+ A CA-signed certificate provides two important capabilities for your server:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Browsers (usually) automatically recognize the certificate and allow a secure connection to be made, without prompting the user.
+ </div></li><li class="listitem"><div class="para">
+ When a CA issues a signed certificate, they are guaranteeing the identity of the organization that is providing the webpages to the browser.
+ </div></li></ul></div><div class="para">
+ If your secure server is being accessed by the public at large, your secure server needs a certificate signed by a CA so that people who visit your website know that the website is owned by the organization who claims to own it. Before signing a certificate, a CA verifies that the organization requesting the certificate was actually who they claimed to be.
+ </div><div class="para">
+ Most Web browsers that support SSL have a list of CAs whose certificates they automatically accept. If a browser encounters a certificate whose authorizing CA is not in the list, the browser asks the user to either accept or decline the connection.
+ </div><div class="para">
+ You can generate a self-signed certificate for your secure server, but be aware that a self-signed certificate does not provide the same functionality as a CA-signed certificate. A self-signed certificate is not automatically recognized by most Web browsers and does not provide any guarantee concerning the identity of the organization that is providing the website. A CA-signed certificate provides both of these important capabilities for a secure server. If your secure server is to be used in a production environment, a CA-signed certificate is recommended.
+ </div><div class="para">
+ The process of getting a certificate from a CA is fairly easy. A quick overview is as follows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Create an encryption private and public key pair.
+ </div></li><li class="listitem"><div class="para">
+ Create a certificate request based on the public key. The certificate request contains information about your server and the company hosting it.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id652062" class="indexterm"></a>
+ <a id="id652080" class="indexterm"></a>
+ <a id="id652094" class="indexterm"></a>
+ Send the certificate request, along with documents proving your identity, to a CA. Red Hat does not make recommendations on which certificate authority to choose. Your decision may be based on your past experiences, on the experiences of your friends or colleagues, or purely on monetary factors.
+ </div><div class="para">
+ Once you have decided upon a CA, you need to follow the instructions they provide on how to obtain a certificate from them.
+ </div></li><li class="listitem"><div class="para">
+ When the CA is satisfied that you are indeed who you claim to be, they provide you with a digital certificate.
+ </div></li><li class="listitem"><div class="para">
+ Install this certificate on your secure server and begin handling secure transactions.
+ </div></li></ol></div><div class="para">
+ Whether you are getting a certificate from a CA or generating your own self-signed certificate, the first step is to generate a key. Refer to <a class="xref" href="#s2-secureserver-generatingkey" title="11.8.5. Generating a Key">Section 11.8.5, “Generating a Key”</a> for instructions.
+ </div></div><div class="section" title="11.8.5. Generating a Key" id="s2-secureserver-generatingkey"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-secureserver-generatingkey">11.8.5. Generating a Key</h3></div></div></div><a id="id806631" class="indexterm"></a><div class="para">
+ You must be root to generate a key.
+ </div><div class="para">
+ First, use the <code class="command">cd</code> command to change to the <code class="filename">/etc/httpd/conf/</code> directory. Remove the fake key and certificate that were generated during the installation with the following commands:
+ </div><pre class="screen">
+<code class="command">rm ssl.key/server.key</code>
+ <code class="command">rm ssl.crt/server.crt</code>
+</pre><div class="para">
+ The <code class="filename">crypto-utils</code> package contains the <code class="command">genkey</code> utility which you can use to generate keys as the name implies. To create your own private key, please ensure the <code class="filename">crypto-utils</code> package is installed. You can view more options by typing <code class="command">man genkey</code> in your terminal. Assuming you wish to generate keys for www.example.com using the <code class="command">genkey</code> utility, type in the following command in your terminal:
+ </div><pre class="screen">
+<code class="command">genkey www.example.com</code>
+</pre><div class="para">
+ Please note that the <code class="command">make</code> based process is no longer shipped with RHEL 5. This will start the <code class="command">genkey</code> graphical user interface. The figure below illustrates the first screen. To navigate, use the keyboard arrow and tab keys. This windows indicates where your key will be stored and prompts you to proceed or cancel the operation. To proceed to the next step, select <span class="guilabel"><strong>Next</strong></span> and press the Return (Enter) key.
+ </div><div class="figure" title="Figure 11.11. Keypair generation" id="keypair-gen"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey1.png" width="444" alt="Keypair generation" /><div class="longdesc"><div class="para">
+ Keypair generation
+ </div></div></div></div><h6>Figure 11.11. Keypair generation</h6></div><br class="figure-break" /><div class="para">
+ The next screen prompts you to choose the size of your key. As indicated, the smaller the size of your key, the faster will the response from your server be and the lesser your level of security. On selecting your preferred, key size using the arrow keys, select <span class="guilabel"><strong>Next</strong></span> to proceed to the next step. The figure below illustrates the key size selection screen.
+ </div><div class="figure" title="Figure 11.12. Choose key size" id="keysize-choose"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey2.png" width="444" alt="Choose key size" /><div class="longdesc"><div class="para">
+ Choose key size
+ </div></div></div></div><h6>Figure 11.12. Choose key size</h6></div><br class="figure-break" /><div class="para">
+ Selecting the next step will initiate the random bits generation process which may take some time depending on the size of your selected key. The larger the size of your key, the longer it will take to generate it.
+ </div><div class="figure" title="Figure 11.13. Generating random bits" id="random-bits"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey3.png" width="444" alt="Generating random bits" /><div class="longdesc"><div class="para">
+ Generating random bits
+ </div></div></div></div><h6>Figure 11.13. Generating random bits</h6></div><br class="figure-break" /><div class="para">
+ On generating your key, you will be prompted to send a Certificate Request (CSR) to a Certificate Authority (CA).
+ </div><div class="figure" title="Figure 11.14. Generate CSR" id="generate-csr"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey4.png" width="444" alt="Generate CSR" /><div class="longdesc"><div class="para">
+ Generate CSR
+ </div></div></div></div><h6>Figure 11.14. Generate CSR</h6></div><br class="figure-break" /><div class="para">
+ Selecting <span class="guilabel"><strong>Yes</strong></span> will prompt you to select the Certificate Authority you wish to send your request to. Selecting <span class="guilabel"><strong>No</strong></span> will allow you to generate a self-signed certificate. The next step for this is illustrated in <a class="xref" href="#private-signed-cert" title="Figure 11.17. Generating a self signed certificate for your server">Figure 11.17, “Generating a self signed certificate for your server”</a>.
+ </div><div class="figure" title="Figure 11.15. Choose Certificate Authority (CA)" id="choose-cert-auth"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey5.png" width="444" alt="Choose Certificate Authority (CA)" /><div class="longdesc"><div class="para">
+ Choose Certificate Authority (CA)
+ </div></div></div></div><h6>Figure 11.15. Choose Certificate Authority (CA)</h6></div><br class="figure-break" /><div class="para">
+ On Selecting your preferred option, select <span class="guilabel"><strong>Next</strong></span> to proceed to the next step. The next screen allows you to enter the details of your certificate.
+ </div><div class="figure" title="Figure 11.16. Enter details for your certificate" id="enter-cert-details"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey6.png" width="444" alt="Enter details for your certificate" /><div class="longdesc"><div class="para">
+ Enter details for your certificate
+ </div></div></div></div><h6>Figure 11.16. Enter details for your certificate</h6></div><br class="figure-break" /><div class="para">
+ If you prefer to generate a self signed cert key pair, you should not generate a CSR. To do this, select <span class="guilabel"><strong>No</strong></span> as your preferred option in the Generate CSR screen. This will display the figure below from which you can enter your certificate details. Entering your certificate details and pressing the return key will display the <a class="xref" href="#protect-private-key" title="Figure 11.19. Protecting your private key">Figure 11.19, “Protecting your private key”</a> from which you can choose to encrypt your private key or not.
+ </div><div class="figure" title="Figure 11.17. Generating a self signed certificate for your server" id="private-signed-cert"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey8.png" width="444" alt="Generating a self signed certificate for your server" /><div class="longdesc"><div class="para">
+ Generating a self signed certificate for your server
+ </div></div></div></div><h6>Figure 11.17. Generating a self signed certificate for your server</h6></div><br class="figure-break" /><div class="para">
+ On entering the details of your certificate, select <span class="guilabel"><strong>Next</strong></span> to proceed. The figure below illustrates an example of a the next screen displayed after completing the details for a certificate to be sent to Equifax. Please note that if you are generating a self signed key, for your server, this screen is not displayed.
+ </div><div class="figure" title="Figure 11.18. Begin certificate request" id="begin-cert-request"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey7.png" width="444" alt="Begin certificate request" /><div class="longdesc"><div class="para">
+ Begin certificate request
+ </div></div></div></div><h6>Figure 11.18. Begin certificate request</h6></div><br class="figure-break" /><div class="para">
+ Pressing the return key, will display the next screen from which you can enable or disable the encryption of the private key. Use the spacebar to enable or disable this. When enabled, a [*] character will be displayed. On selecting your preferred option, select <span class="guilabel"><strong>Next</strong></span> to proceed to the next step.
+ </div><div class="figure" title="Figure 11.19. Protecting your private key" id="protect-private-key"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey9.png" width="444" alt="Protecting your private key" /><div class="longdesc"><div class="para">
+ Protecting your private key
+ </div></div></div></div><h6>Figure 11.19. Protecting your private key</h6></div><br class="figure-break" /><div class="para">
+ The next screen allows you to set your key passphase. Please do not lose this pass phase as you will not be able to run the server without it. You will need to regenerate a new private or public key pair and request a new certificate from your CA as indicated. For security, the passphase is not displayed as you type. On typing your preferred passphase, select <span class="guilabel"><strong>Next</strong></span> to go back to your terminal.
+ </div><div class="figure" title="Figure 11.20. Set passphase" id="set-passphase"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey10.png" width="444" alt="Set passphase" /><div class="longdesc"><div class="para">
+ Set passphase
+ </div></div></div></div><h6>Figure 11.20. Set passphase</h6></div><br class="figure-break" /><div class="para">
+ If you attempt to run <code class="command">genkey makeca</code> on a server that has an existing key pair, an error message will be displayed as illustrated below. You need to delete your existing key file as indicated to generate a new key pair.
+ </div><div class="figure" title="Figure 11.21. genkey error" id="genkey-error"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey11.png" width="444" alt="genkey error" /><div class="longdesc"><div class="para">
+ genkey error
+ </div></div></div></div><h6>Figure 11.21. genkey error</h6></div><br class="figure-break" /><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs/2.2/ssl/">http://httpd.apache.org/docs/2.2/ssl/</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs/2.2/vhosts/">http://httpd.apache.org/docs/2.2/vhosts/</a>
+ </div></li></ul></div></div><div class="section" title="11.8.6. How to configure the server to use the new key" id="s1-use-new-key"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-use-new-key">11.8.6. How to configure the server to use the new key</h3></div></div></div><a id="id847160" class="indexterm"></a><div class="para">
+ The steps to configure the Apache HTTP Server to use the new key are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Obtain the signed certificate from the CA after submitting the CSR.
+ </div></li><li class="listitem"><div class="para">
+ Copy the certificate to the path, for example <code class="filename">/etc/pki/tls/certs/www.example.com.crt</code>
+ </div></li><li class="listitem"><div class="para">
+ Edit <code class="filename">/etc/httpd/conf.d/ssl.conf</code>. Change the SSLCertificateFile and SSLCertificateKey lines to be.
+ </div><pre class="screen">
+SSLCertificateFile /etc/pki/tls/certs/www.example.com.crt
+SSLCertificateKeyFile /etc/pki/tls/private/www.example.com.key
+</pre><div class="para">
+ where the "www.example.com" part should match the argument passed on the <code class="command">genkey</code> command.
+ </div></li></ul></div></div></div><div class="section" title="11.9. Additional Resources" id="s1-apache-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-additional-resources">11.9. Additional Resources</h2></div></div></div><a id="id873498" class="indexterm"></a><div class="para">
+ To learn more about the Apache HTTP Server, refer to the following resources.
+ </div><div class="section" title="11.9.1. Useful Websites" id="s2-apache-additional-resources-web"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-additional-resources-web">11.9.1. Useful Websites</h3></div></div></div><a id="id829382" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/">http://httpd.apache.org/</a> — The official website for the Apache HTTP Server with documentation on all the directives and default modules.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.modssl.org/">http://www.modssl.org/</a> — The official website for <code class="filename">mod_ssl</code>.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.apacheweek.com/">http://www.apacheweek.com/</a> — A comprehensive online weekly newsletter about all things Apache.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 12. FTP" id="ch-FTP" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 12. FTP</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-ftp-protocol">12.1. The File Transfer Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol-multiport">12.1.1. Multiple Ports, Multiple Modes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ftp-servers">12.2. FTP Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-servers-vsftpd">12.2.1. <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">12.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s1-ftp-vsftpd-start">12.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dd><dl><dt>
<span class="section"><a href="#s2-ftp-vsftpd-start-multi">12.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ftp-vsftpd-conf">12.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-daemon">12.5.1. Daemon Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-login">12.5.2. Log In Options and Access Controls</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-anon">12.5.3. Anonymous User Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-usr">12.5.4. Local User Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-dir">12.5.5. Directory Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-file">12.5.6. File Transfer Options</a></span></dt><dt><span class="section"><
a href="#s2-ftp-vsftpd-conf-opt-log">12.5.7. Logging Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf-opt-net">12.5.8. Network Options</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ftp-resources">12.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-installed-documentation">12.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-ftp-useful-websites">12.6.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id856832" class="indexterm"></a><a id="id822068" class="indexterm"></a><div class="para">
+ File Transfer Protocol (FTP) is one of the oldest and most commonly used protocols found on the Internet today. Its purpose is to reliably transfer files between computer hosts on a network without requiring the user to log directly into the remote host or have knowledge of how to use the remote system. It allows users to access files on remote systems using a standard set of simple commands.
+ </div><div class="para">
+ This chapter outlines the basics of the FTP protocol, as well as configuration options for the primary FTP server shipped with Fedora, <code class="command">vsftpd</code>.
+ </div><div class="section" title="12.1. The File Transfer Protocol" id="s1-ftp-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ftp-protocol">12.1. The File Transfer Protocol</h2></div></div></div><a id="id596574" class="indexterm"></a><div class="para">
+ However, because FTP is so prevalent on the Internet, it is often required to share files to the public. System administrators, therefore, should be aware of the FTP protocol's unique characteristics.
+ </div><div class="section" title="12.1.1. Multiple Ports, Multiple Modes" id="s2-ftp-protocol-multiport"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-protocol-multiport">12.1.1. Multiple Ports, Multiple Modes</h3></div></div></div><a id="id883175" class="indexterm"></a><a id="id868103" class="indexterm"></a><a id="id932812" class="indexterm"></a><a id="id703526" class="indexterm"></a><div class="para">
+ Unlike most protocols used on the Internet, FTP requires multiple network ports to work properly. When an FTP client application initiates a connection to an FTP server, it opens port 21 on the server — known as the <em class="firstterm">command port</em>. This port is used to issue all commands to the server. Any data requested from the server is returned to the client via a <em class="firstterm">data port</em>. The port number for data connections, and the way in which data connections are initialized, vary depending upon whether the client requests the data in <em class="firstterm">active</em> or <em class="firstterm">passive</em> mode.
+ </div><div class="para">
+ The following defines these modes:
+ </div><div class="variablelist"><dl><dt><span class="term">active mode</span></dt><dd><div class="para">
+ Active mode is the original method used by the FTP protocol for transferring data to the client application. When an active mode data transfer is initiated by the FTP client, the server opens a connection from port 20 on the server to the IP address and a random, unprivileged port (greater than 1024) specified by the client. This arrangement means that the client machine must be allowed to accept connections over any port above 1024. With the growth of insecure networks, such as the Internet, the use of firewalls to protect client machines is now prevalent. Because these client-side firewalls often deny incoming connections from active mode FTP servers, passive mode was devised.
+ </div></dd><dt><span class="term">passive mode</span></dt><dd><div class="para">
+ Passive mode, like active mode, is initiated by the FTP client application. When requesting data from the server, the FTP client indicates it wants to access the data in passive mode and the server provides the IP address and a random, unprivileged port (greater than 1024) on the server. The client then connects to that port on the server to download the requested information.
+ </div><div class="para">
+ While passive mode resolves issues for client-side firewall interference with data connections, it can complicate administration of the server-side firewall. You can reduce the number of open ports on a server by limiting the range of unprivileged ports on the FTP server. This also simplifies the process of configuring firewall rules for the server. Refer to <a class="xref" href="#s2-ftp-vsftpd-conf-opt-net" title="12.5.8. Network Options">Section 12.5.8, “Network Options”</a> for more about limiting passive ports.
+ </div></dd></dl></div></div></div><div class="section" title="12.2. FTP Servers" id="s1-ftp-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ftp-servers">12.2. FTP Servers</h2></div></div></div><a id="id949751" class="indexterm"></a><a id="id949773" class="indexterm"></a><a id="id949794" class="indexterm"></a><a id="id761524" class="indexterm"></a><div class="para">
+ Fedora ships with two different FTP servers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>Red Hat Content Accelerator</strong></span> — A kernel-based Web server that delivers high performance Web server and FTP services. Since speed as its primary design goal, it has limited functionality and runs only as an anonymous FTP server. For more information about configuring and administering <span class="application"><strong>Red Hat Content Accelerator</strong></span>, consult the documentation available online at <a href="http://www.redhat.com/docs/manuals/tux/">http://www.redhat.com/docs/manuals/tux/</a>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vsftpd</code> — A fast, secure FTP daemon which is the preferred FTP server for Fedora. The remainder of this chapter focuses on <code class="command">vsftpd</code>.
+ </div></li></ul></div><div class="section" title="12.2.1. vsftpd" id="s2-ftp-servers-vsftpd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-servers-vsftpd">12.2.1. <code class="command">vsftpd</code> </h3></div></div></div><div class="para">
+ The Very Secure FTP Daemon (<code class="command">vsftpd</code>) is designed from the ground up to be fast, stable, and, most importantly, secure. <code class="command">vsftpd</code> is the only stand-alone FTP server distributed with Fedora, due to its ability to handle large numbers of connections efficiently and securely.
+ </div><div class="para">
+ The security model used by <code class="command">vsftpd</code> has three primary aspects:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Strong separation of privileged and non-privileged processes</em></span> — Separate processes handle different tasks, and each of these processes run with the minimal privileges required for the task.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Tasks requiring elevated privileges are handled by processes with the minimal privilege necessary</em></span> — By leveraging compatibilities found in the <code class="filename">libcap</code> library, tasks that usually require full root privileges can be executed more safely from a less privileged process.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Most processes run in a <code class="command">chroot</code> jail</em></span> — Whenever possible, processes are change-rooted to the directory being shared; this directory is then considered a <code class="command">chroot</code> jail. For example, if the directory <code class="command">/var/ftp/</code> is the primary shared directory, <code class="command">vsftpd</code> reassigns <code class="command">/var/ftp/</code> to the new root directory, known as <code class="command">/</code>. This disallows any potential malicious hacker activities for any directories not contained below the new root directory.
+ </div></li></ul></div><div class="para">
+ Use of these security practices has the following effect on how <code class="command">vsftpd</code> deals with requests:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>The parent process runs with the least privileges required</em></span> — The parent process dynamically calculates the level of privileges it requires to minimize the level of risk. Child processes handle direct interaction with the FTP clients and run with as close to no privileges as possible.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>All operations requiring elevated privileges are handled by a small parent process</em></span> — Much like the Apache HTTP Server, <code class="command">vsftpd</code> launches unprivileged child processes to handle incoming connections. This allows the privileged, parent process to be as small as possible and handle relatively few tasks.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>All requests from unprivileged child processes are distrusted by the parent process</em></span> — Communication with child processes are received over a socket, and the validity of any information from child processes is checked before being acted on.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Most interaction with FTP clients is handled by unprivileged child processes in a <code class="command">chroot</code> jail</em></span> — Because these child processes are unprivileged and only have access to the directory being shared, any crashed processes only allows the attacker access to the shared files.
+ </div></li></ul></div></div></div><div class="section" title="12.3. Files Installed with vsftpd" id="s2-ftp-vsftpd-conf"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s2-ftp-vsftpd-conf">12.3. Files Installed with <code class="command">vsftpd</code> </h2></div></div></div><a id="id718741" class="indexterm"></a><div class="para">
+ The <code class="filename">vsftpd</code> RPM installs the daemon (<code class="filename">/usr/sbin/vsftpd</code>), its configuration and related files, as well as FTP directories onto the system. The following lists the files and directories related to <code class="command">vsftpd</code> configuration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/etc/rc.d/init.d/vsftpd</code> — The <span class="emphasis"><em>initialization script</em></span> (<em class="firstterm">initscript</em>) used by the <code class="command">/sbin/service</code> command to start, stop, or reload <code class="command">vsftpd</code>. Refer to <a class="xref" href="#s1-ftp-vsftpd-start" title="12.4. Starting and Stopping vsftpd">Section 12.4, “Starting and Stopping <code class="command">vsftpd</code> ”</a> for more information about using this script.
+ </div></li><li xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN" class="listitem" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"><div class="para">
+ <code class="filename">/etc/pam.d/vsftpd</code> — The Pluggable Authentication Modules (PAM) configuration file for <code class="command">vsftpd</code>. This file specifies the requirements a user must meet to login to the FTP server. For more information on PAM, refer to the <em class="citetitle">Pluggable Authentication Modules (PAM)</em> chapter of the Fedora 13 <em class="citetitle">Security Guide</em>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/vsftpd/vsftpd.conf</code> — The configuration file for <code class="command">vsftpd</code>. Refer to <a class="xref" href="#s1-ftp-vsftpd-conf" title="12.5. vsftpd Configuration Options">Section 12.5, “ <code class="command">vsftpd</code> Configuration Options”</a> for a list of important options contained within this file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/vsftpd.ftpusers</code> — A list of users not allowed to log into <code class="command">vsftpd</code>. By default, this list includes the <code class="command">root</code>, <code class="command">bin</code>, and <code class="command">daemon</code> users, among others.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/vsftpd.user_list</code> — This file can be configured to either deny or allow access to the users listed, depending on whether the <code class="command">userlist_deny</code> directive is set to <code class="command">YES</code> (default) or <code class="command">NO</code> in <code class="filename">/etc/vsftpd/vsftpd.conf</code>. If <code class="filename">/etc/vsftpd.user_list</code> is used to grant access to users, the usernames listed must <span class="emphasis"><em>not</em></span> appear in <code class="filename">/etc/vsftpd.ftpusers</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/var/ftp/</code> — The directory containing files served by <code class="command">vsftpd</code>. It also contains the <code class="filename">/var/ftp/pub/</code> directory for anonymous users. Both directories are world-readable, but writable only by the root user.
+ </div></li></ul></div></div><div class="section" title="12.4. Starting and Stopping vsftpd" id="s1-ftp-vsftpd-start"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ftp-vsftpd-start">12.4. Starting and Stopping <code class="command">vsftpd</code> </h2></div></div></div><a id="id739251" class="indexterm"></a><a id="id739269" class="indexterm"></a><a id="id739287" class="indexterm"></a><a id="id981697" class="indexterm"></a><a id="id981715" class="indexterm"></a><div class="para">
+ The <code class="filename">vsftpd</code> RPM installs the <code class="filename">/etc/rc.d/init.d/vsftpd</code> script, which can be accessed using the <code class="command">/sbin/service</code> command.
+ </div><div class="para">
+ To start the server, as root type:
+ </div><pre class="screen">
+<code class="command">/sbin/service vsftpd start</code>
+</pre><div class="para">
+ To stop the server, as root type:
+ </div><pre class="screen">
+<code class="command">/sbin/service vsftpd stop</code>
+</pre><div class="para">
+ The <code class="option">restart</code> option is a shorthand way of stopping and then starting <code class="command">vsftpd</code>. This is the most efficient way to make configuration changes take effect after editing the configuration file for <code class="command">vsftpd</code>.
+ </div><div class="para">
+ To restart the server, as root type:
+ </div><pre class="screen">
+<code class="command">/sbin/service vsftpd restart</code>
+</pre><div class="para">
+ The <code class="option">condrestart</code> (<em class="firstterm">conditional restart</em>) option only starts <code class="command">vsftpd</code> if it is currently running. This option is useful for scripts, because it does not start the daemon if it is not running.
+ </div><div class="para">
+ To conditionally restart the server, as root type:
+ </div><pre class="screen">
+<code class="command">/sbin/service vsftpd condrestart</code>
+</pre><div class="para">
+ By default, the <code class="command">vsftpd</code> service does <span class="emphasis"><em>not</em></span> start automatically at boot time. To configure the <code class="command">vsftpd</code> service to start at boot time, use an initscript utility, such as <code class="command">/sbin/chkconfig</code>, <span class="application"><strong>/usr/sbin/ntsysv</strong></span>, or the <span class="application"><strong>Services Configuration Tool</strong></span> program. Refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a> for more information regarding these tools.
+ </div><div class="section" title="12.4.1. Starting Multiple Copies of vsftpd" id="s2-ftp-vsftpd-start-multi"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-start-multi">12.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </h3></div></div></div><a id="id663847" class="indexterm"></a><a id="id663864" class="indexterm"></a><div class="para">
+ Sometimes one computer is used to serve multiple FTP domains. This is a technique called <em class="firstterm">multihoming</em>. One way to multihome using <code class="command">vsftpd</code> is by running multiple copies of the daemon, each with its own configuration file.
+ </div><div class="para">
+ To do this, first assign all relevant IP addresses to network devices or alias network devices on the system. Refer to <a class="xref" href="#ch-Network_Configuration" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a> for more information about configuring network devices and device aliases. Additional information can be found about network configuration scripts in <a class="xref" href="#ch-Network_Interfaces" title="Chapter 4. Network Interfaces">Chapter 4, <i>Network Interfaces</i></a>.
+ </div><div class="para">
+ Next, the DNS server for the FTP domains must be configured to reference the correct machine. For information about BIND and its configuration files, refer to <a class="xref" href="#ch-The_BIND_DNS_Server" title="Chapter 7. The BIND DNS Server">Chapter 7, <i>The BIND DNS Server</i></a>.
+ </div><div class="para">
+ For <code class="command">vsftpd</code> to answer requests on different IP addresses, multiple copies of the daemon must be running. The first copy must be run using the <code class="command">vsftpd</code> initscripts, as outlined in <a class="xref" href="#s1-ftp-vsftpd-start" title="12.4. Starting and Stopping vsftpd">Section 12.4, “Starting and Stopping <code class="command">vsftpd</code> ”</a>. This copy uses the standard configuration file, <code class="filename">/etc/vsftpd/vsftpd.conf</code>.
+ </div><div class="para">
+ Each additional FTP site must have a configuration file with a unique name in the <code class="filename">/etc/vsftpd/</code> directory, such as <code class="filename">/etc/vsftpd/vsftpd-site-2.conf</code>. Each configuration file must be readable and writable only by root. Within each configuration file for each FTP server listening on an IPv4 network, the following directive must be unique:
+ </div><pre class="screen">
+<code class="command">listen_address=<em class="replaceable"><code>N.N.N.N</code></em> </code>
+</pre><div class="para">
+ Replace <em class="replaceable"><code>N.N.N.N</code></em> with the <span class="emphasis"><em>unique</em></span> IP address for the FTP site being served. If the site is using IPv6, use the <code class="command">listen_address6</code> directive instead.
+ </div><div class="para">
+ Once each additional server has a configuration file, the <code class="command">vsftpd</code> daemon must be launched from a root shell prompt using the following command:
+ </div><pre class="screen">
+<code class="command">vsftpd /etc/vsftpd/<em class="replaceable"><code><configuration-file></code></em> </code> [amp ]
+</pre><div class="para">
+ In the above command, replace <em class="replaceable"><code><configuration-file></code></em> with the unique name for the server's configuration file, such as <code class="filename">/etc/vsftpd/vsftpd-site-2.conf</code>.
+ </div><div class="para">
+ Other directives to consider altering on a per-server basis are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">anon_root</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">local_root</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vsftpd_log_file</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">xferlog_file</code>
+ </div></li></ul></div><div class="para">
+ For a detailed list of directives available within <code class="command">vsftpd</code>'s configuration file, refer to <a class="xref" href="#s1-ftp-vsftpd-conf" title="12.5. vsftpd Configuration Options">Section 12.5, “ <code class="command">vsftpd</code> Configuration Options”</a>.
+ </div><div class="para">
+ To configure any additional servers to start automatically at boot time, add the above command to the end of the <code class="filename">/etc/rc.local</code> file.
+ </div></div></div><div class="section" title="12.5. vsftpd Configuration Options" id="s1-ftp-vsftpd-conf"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ftp-vsftpd-conf">12.5. <code class="command">vsftpd</code> Configuration Options</h2></div></div></div><a id="id609848" class="indexterm"></a><a id="id609870" class="indexterm"></a><div class="para">
+ Although <code class="command">vsftpd</code> may not offer the level of customization other widely available FTP servers have, it offers enough options to fill most administrator's needs. The fact that it is not overly feature-laden limits configuration and programmatic errors.
+ </div><div class="para">
+ All configuration of <code class="command">vsftpd</code> is handled by its configuration file, <code class="filename">/etc/vsftpd/vsftpd.conf</code>. Each directive is on its own line within the file and follows the following format:
+ </div><pre class="screen">
+<em class="replaceable"><code><directive></code></em>=<em class="replaceable"><code><value></code></em>
+</pre><div class="para">
+ For each directive, replace <em class="replaceable"><code><directive></code></em> with a valid directive and <em class="replaceable"><code><value></code></em> with a valid value.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ There must not be any spaces between the <em class="replaceable"><code><directive></code></em>, equal symbol, and the <em class="replaceable"><code><value></code></em> in a directive.
+ </div></div><div class="para">
+ Comment lines must be preceded by a hash mark (<code class="command">#</code>) and are ignored by the daemon.
+ </div><div class="para">
+ For a complete list of all directives available, refer to the man page for <code class="filename">vsftpd.conf</code>.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ For an overview of ways to secure <code class="command">vsftpd</code>, refer to the Fedora 13 <em class="citetitle">Security Guide</em>.
+ </div></div><div class="para">
+ The following is a list of some of the more important directives within <code class="filename">/etc/vsftpd/vsftpd.conf</code>. All directives not explicitly found within <code class="command">vsftpd</code>'s configuration file are set to their default value.
+ </div><div class="section" title="12.5.1. Daemon Options" id="s2-ftp-vsftpd-conf-opt-daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-daemon">12.5.1. Daemon Options</h3></div></div></div><a id="id814940" class="indexterm"></a><div class="para">
+ The following is a list of directives which control the overall behavior of the <code class="command">vsftpd</code> daemon.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">listen</code> — When enabled, <code class="command">vsftpd</code> runs in stand-alone mode. Fedora sets this value to <code class="command">YES</code>. This directive cannot be used in conjunction with the <code class="command">listen_ipv6</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">listen_ipv6</code> — When enabled, <code class="command">vsftpd</code> runs in stand-alone mode, but listens only to IPv6 sockets. This directive cannot be used in conjunction with the <code class="command">listen</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN" class="listitem" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"><div class="para">
+ <code class="command">session_support</code> — When enabled, <code class="command">vsftpd</code> attempts to maintain login sessions for each user through Pluggable Authentication Modules (PAM). Refer to for more information. If session logging is not necessary, disabling this option allows <code class="command">vsftpd</code> to run with less processes and lower privileges.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li></ul></div></div><div class="section" title="12.5.2. Log In Options and Access Controls" id="s2-ftp-vsftpd-conf-opt-login"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-login">12.5.2. Log In Options and Access Controls</h3></div></div></div><a id="id821375" class="indexterm"></a><a id="id877556" class="indexterm"></a><div class="para">
+ The following is a list of directives which control the login behavior and access control mechanisms.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">anonymous_enable</code> — When enabled, anonymous users are allowed to log in. The usernames <code class="computeroutput">anonymous</code> and <code class="computeroutput">ftp</code> are accepted.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div><div class="para">
+ Refer to <a class="xref" href="#s2-ftp-vsftpd-conf-opt-anon" title="12.5.3. Anonymous User Options">Section 12.5.3, “Anonymous User Options”</a> for a list of directives affecting anonymous users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">banned_email_file</code> — If the <code class="command">deny_email_enable</code> directive is set to <code class="command">YES</code>, this directive specifies the file containing a list of anonymous email passwords which are not permitted access to the server.
+ </div><div class="para">
+ The default value is <code class="filename">/etc/vsftpd.banned_emails</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">banner_file</code> — Specifies the file containing text displayed when a connection is established to the server. This option overrides any text specified in the <code class="command">ftpd_banner</code> directive.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">cmds_allowed</code> — Specifies a comma-delimited list of FTP commands allowed by the server. All other commands are rejected.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">deny_email_enable</code> — When enabled, any anonymous user utilizing email passwords specified in the <code class="filename">/etc/vsftpd.banned_emails</code> are denied access to the server. The name of the file referenced by this directive can be specified using the <code class="command">banned_email_file</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ftpd_banner</code> — When enabled, the string specified within this directive is displayed when a connection is established to the server. This option can be overridden by the <code class="command">banner_file</code> directive.
+ </div><div class="para">
+ By default <code class="command">vsftpd</code> displays its standard banner.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">local_enable</code> — When enabled, local users are allowed to log into the system.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div><div class="para">
+ Refer to <a class="xref" href="#s2-ftp-vsftpd-conf-opt-usr" title="12.5.4. Local User Options">Section 12.5.4, “Local User Options”</a> for a list of directives affecting local users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pam_service_name</code> — Specifies the PAM service name for <code class="command">vsftpd</code>.
+ </div><div class="para">
+ The default value is <code class="command">ftp</code>. Note, in Fedora, the value is set to <code class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ The default value is <code class="command">NO</code>. Note, in Fedora, the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">userlist_deny</code> — When used in conjunction with the <code class="command">userlist_enable</code> directive and set to <code class="command">NO</code>, all local users are denied access unless the username is listed in the file specified by the <code class="command">userlist_file</code> directive. Because access is denied before the client is asked for a password, setting this directive to <code class="command">NO</code> prevents local users from submitting unencrypted passwords over the network.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">userlist_enable</code> — When enabled, the users listed in the file specified by the <code class="command">userlist_file</code> directive are denied access. Because access is denied before the client is asked for a password, users are prevented from submitting unencrypted passwords over the network.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>, however under Fedora the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">userlist_file</code> — Specifies the file referenced by <code class="command">vsftpd</code> when the <code class="command">userlist_enable</code> directive is enabled.
+ </div><div class="para">
+ The default value is <code class="command">/etc/vsftpd.user_list</code> and is created during installation.
+ </div></li></ul></div></div><div class="section" title="12.5.3. Anonymous User Options" id="s2-ftp-vsftpd-conf-opt-anon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-anon">12.5.3. Anonymous User Options</h3></div></div></div><a id="id641522" class="indexterm"></a><div class="para">
+ The following lists directives which control anonymous user access to the server. To use these options, the <code class="command">anonymous_enable</code> directive must be set to <code class="command">YES</code>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">anon_mkdir_write_enable</code> — When enabled in conjunction with the <code class="command">write_enable</code> directive, anonymous users are allowed to create new directories within a parent directory which has write permissions.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">anon_root</code> — Specifies the directory <code class="command">vsftpd</code> changes to after an anonymous user logs in.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">anon_upload_enable</code> — When enabled in conjunction with the <code class="command">write_enable</code> directive, anonymous users are allowed to upload files within a parent directory which has write permissions.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">anon_world_readable_only</code> — When enabled, anonymous users are only allowed to download world-readable files.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ftp_username</code> — Specifies the local user account (listed in <code class="filename">/etc/passwd</code>) used for the anonymous FTP user. The home directory specified in <code class="filename">/etc/passwd</code> for the user is the root directory of the anonymous FTP user.
+ </div><div class="para">
+ The default value is <code class="command">ftp</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no_anon_password</code> — When enabled, the anonymous user is not asked for a password.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">secure_email_list_enable</code> — When enabled, only a specified list of email passwords for anonymous logins are accepted. This is a convenient way to offer limited security to public content without the need for virtual users.
+ </div><div class="para">
+ Anonymous logins are prevented unless the password provided is listed in <code class="command">/etc/vsftpd.email_passwords</code>. The file format is one password per line, with no trailing white spaces.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li></ul></div></div><div class="section" title="12.5.4. Local User Options" id="s2-ftp-vsftpd-conf-opt-usr"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-usr">12.5.4. Local User Options</h3></div></div></div><a id="id1127034" class="indexterm"></a><div class="para">
+ The following lists directives which characterize the way local users access the server. To use these options, the <code class="command">local_enable</code> directive must be set to <code class="command">YES</code>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">chmod_enable</code> — When enabled, the FTP command <code class="command">SITE CHMOD</code> is allowed for local users. This command allows the users to change the permissions on files.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">chroot_list_enable</code> — When enabled, the local users listed in the file specified in the <code class="command">chroot_list_file</code> directive are placed in a <code class="command">chroot</code> jail upon log in.
+ </div><div class="para">
+ If enabled in conjunction with the <code class="command">chroot_local_user</code> directive, the local users listed in the file specified in the <code class="command">chroot_list_file</code> directive are <span class="emphasis"><em>not</em></span> placed in a <code class="command">chroot</code> jail upon log in.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">chroot_list_file</code> — Specifies the file containing a list of local users referenced when the <code class="command">chroot_list_enable</code> directive is set to <code class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code class="command">/etc/vsftpd.chroot_list</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">chroot_local_user</code> — When enabled, local users are change-rooted to their home directories after logging in.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ Enabling <code class="command">chroot_local_user</code> opens up a number of security issues, especially for users with upload privileges. For this reason, it is <span class="emphasis"><em>not</em></span> recommended.
+ </div></div></li><li class="listitem"><div class="para">
+ <code class="command">guest_enable</code> — When enabled, all non-anonymous users are logged in as the user <code class="command">guest</code>, which is the local user specified in the <code class="command">guest_username</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">guest_username</code> — Specifies the username the <code class="command">guest</code> user is mapped to.
+ </div><div class="para">
+ The default value is <code class="command">ftp</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">local_root</code> — Specifies the directory <code class="command">vsftpd</code> changes to after a local user logs in.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">local_umask</code> — Specifies the umask value for file creation. Note that the default value is in octal form (a numerical system with a base of eight), which includes a "0" prefix. Otherwise the value is treated as a base-10 integer.
+ </div><div class="para">
+ The default value is <code class="command">022</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">passwd_chroot_enable</code> — When enabled in conjunction with the <code class="command">chroot_local_user</code> directive, <code class="command">vsftpd</code> change-roots local users based on the occurrence of the <code class="command">/./</code> in the home directory field within <code class="filename">/etc/passwd</code>.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">user_config_dir</code> — Specifies the path to a directory containing configuration files bearing the name of local system users that contain specific setting for that user. Any directive in the user's configuration file overrides those found in <code class="filename">/etc/vsftpd/vsftpd.conf</code>.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li></ul></div></div><div class="section" title="12.5.5. Directory Options" id="s2-ftp-vsftpd-conf-opt-dir"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-dir">12.5.5. Directory Options</h3></div></div></div><a id="id720333" class="indexterm"></a><div class="para">
+ The following lists directives which affect directories.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">dirlist_enable</code> — When enabled, users are allowed to view directory lists.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">dirmessage_enable</code> — When enabled, a message is displayed whenever a user enters a directory with a message file. This message resides within the current directory. The name of this file is specified in the <code class="command">message_file</code> directive and is <code class="filename">.message</code> by default.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>. Note, in Fedora, the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">force_dot_files</code> — When enabled, files beginning with a dot (<code class="computeroutput">.</code>) are listed in directory listings, with the exception of the <code class="filename">.</code> and <code class="filename">..</code> files.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">hide_ids</code> — When enabled, all directory listings show <code class="computeroutput">ftp</code> as the user and group for each file.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">message_file</code> — Specifies the name of the message file when using the <code class="command">dirmessage_enable</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">.message</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">text_userdb_names</code> — When enabled, test usernames and group names are used in place of UID and GID entries. Enabling this option may slow performance of the server.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">use_localtime</code> — When enabled, directory listings reveal the local time for the computer instead of GMT.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li></ul></div></div><div class="section" title="12.5.6. File Transfer Options" id="s2-ftp-vsftpd-conf-opt-file"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-file">12.5.6. File Transfer Options</h3></div></div></div><a id="id849894" class="indexterm"></a><div class="para">
+ The following lists directives which affect directories.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">download_enable</code> — When enabled, file downloads are permitted.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">chown_uploads</code> — When enabled, all files uploaded by anonymous users are owned by the user specified in the <code class="command">chown_username</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">chown_username</code> — Specifies the ownership of anonymously uploaded files if the <code class="command">chown_uploads</code> directive is enabled.
+ </div><div class="para">
+ The default value is <code class="command">root</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">write_enable</code> — When enabled, FTP commands which can change the file system are allowed, such as <code class="command">DELE</code>, <code class="command">RNFR</code>, and <code class="command">STOR</code>.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li></ul></div></div><div class="section" title="12.5.7. Logging Options" id="s2-ftp-vsftpd-conf-opt-log"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-log">12.5.7. Logging Options</h3></div></div></div><a id="id689492" class="indexterm"></a><div class="para">
+ The following lists directives which affect <code class="command">vsftpd</code>'s logging behavior.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">dual_log_enable</code> — When enabled in conjunction with <code class="command">xferlog_enable</code>, <code class="command">vsftpd</code> writes two files simultaneously: a <code class="command">wu-ftpd</code>-compatible log to the file specified in the <code class="command">xferlog_file</code> directive (<code class="filename">/var/log/xferlog</code> by default) and a standard <code class="command">vsftpd</code> log file specified in the <code class="command">vsftpd_log_file</code> directive (<code class="filename">/var/log/vsftpd.log</code> by default).
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">log_ftp_protocol</code> — When enabled in conjunction with <code class="command">xferlog_enable</code> and with <code class="command">xferlog_std_format</code> set to <code class="command">NO</code>, all FTP commands and responses are logged. This directive is useful for debugging.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">syslog_enable</code> — When enabled in conjunction with <code class="command">xferlog_enable</code>, all logging normally written to the standard <code class="command">vsftpd</code> log file specified in the <code class="command">vsftpd_log_file</code> directive (<code class="filename">/var/log/vsftpd.log</code> by default) is sent to the system logger instead under the FTPD facility.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vsftpd_log_file</code> — Specifies the <code class="command">vsftpd</code> log file. For this file to be used, <code class="command">xferlog_enable</code> must be enabled and <code class="command">xferlog_std_format</code> must either be set to <code class="command">NO</code> or, if <code class="command">xferlog_std_format</code> is set to <code class="command">YES</code>, <code class="command">dual_log_enable</code> must be enabled. It is important to note that if <code class="command">syslog_enable</code> is set to <code class="command">YES</code>, the system log is used instead of the file specified in this directive.
+ </div><div class="para">
+ The default value is <code class="filename">/var/log/vsftpd.log</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">xferlog_enable</code> — When enabled, <code class="command">vsftpd</code> logs connections (<code class="command">vsftpd</code> format only) and file transfer information to the log file specified in the <code class="command">vsftpd_log_file</code> directive (<code class="filename">/var/log/vsftpd.log</code> by default). If <code class="command">xferlog_std_format</code> is set to <code class="command">YES</code>, file transfer information is logged but connections are not, and the log file specified in <code class="command">xferlog_file</code> (<code class="filename">/var/log/xferlog</code> by default) is used instead. It is important to note that both log files and log formats are used if <code class="command">dual_log_enable</code> is set to <code class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>. Note, in Fedora, the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">xferlog_file</code> — Specifies the <code class="command">wu-ftpd</code>-compatible log file. For this file to be used, <code class="command">xferlog_enable</code> must be enabled and <code class="command">xferlog_std_format</code> must be set to <code class="command">YES</code>. It is also used if <code class="command">dual_log_enable</code> is set to <code class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code class="filename">/var/log/xferlog</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">xferlog_std_format</code> — When enabled in conjunction with <code class="command">xferlog_enable</code>, only a <code class="command">wu-ftpd</code>-compatible file transfer log is written to the file specified in the <code class="command">xferlog_file</code> directive (<code class="filename">/var/log/xferlog</code> by default). It is important to note that this file only logs file transfers and does not log connections to the server.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>. Note, in Fedora, the value is set to <code class="command">YES</code>.
+ </div></li></ul></div><div class="important"><h2>Important</h2><div class="para">
+ To maintain compatibility with log files written by the older <code class="command">wu-ftpd</code> FTP server, the <code class="command">xferlog_std_format</code> directive is set to <code class="command">YES</code> under Fedora. However, this setting means that connections to the server are not logged.
+ </div><div class="para">
+ To both log connections in <code class="command">vsftpd</code> format and maintain a <code class="command">wu-ftpd</code>-compatible file transfer log, set <code class="command">dual_log_enable</code> to <code class="command">YES</code>.
+ </div><div class="para">
+ If maintaining a <code class="command">wu-ftpd</code>-compatible file transfer log is not important, either set <code class="command">xferlog_std_format</code> to <code class="command">NO</code>, comment the line with a hash mark (<code class="command">#</code>), or delete the line entirely.
+ </div></div></div><div class="section" title="12.5.8. Network Options" id="s2-ftp-vsftpd-conf-opt-net"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-net">12.5.8. Network Options</h3></div></div></div><a id="id751875" class="indexterm"></a><div class="para">
+ The following lists directives which affect how <code class="command">vsftpd</code> interacts with the network.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">accept_timeout</code> — Specifies the amount of time for a client using passive mode to establish a connection.
+ </div><div class="para">
+ The default value is <code class="command">60</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">anon_max_rate</code> — Specifies the maximum data transfer rate for anonymous users in bytes per second.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit the transfer rate.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">connect_from_port_20</code> When enabled, <code class="command">vsftpd</code> runs with enough privileges to open port 20 on the server during active mode data transfers. Disabling this option allows <code class="command">vsftpd</code> to run with less privileges, but may be incompatible with some FTP clients.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>. Note, in Fedora, the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">connect_timeout</code> — Specifies the maximum amount of time a client using active mode has to respond to a data connection, in seconds.
+ </div><div class="para">
+ The default value is <code class="command">60</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">data_connection_timeout</code> — Specifies maximum amount of time data transfers are allowed to stall, in seconds. Once triggered, the connection to the remote client is closed.
+ </div><div class="para">
+ The default value is <code class="command">300</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ftp_data_port</code> — Specifies the port used for active data connections when <code class="command">connect_from_port_20</code> is set to <code class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code class="command">20</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">idle_session_timeout</code> — Specifies the maximum amount of time between commands from a remote client. Once triggered, the connection to the remote client is closed.
+ </div><div class="para">
+ The default value is <code class="command">300</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">listen_address</code> — Specifies the IP address on which <code class="command">vsftpd</code> listens for network connections.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div><div class="note"><h2>Tip</h2><div class="para">
+ If running multiple copies of <code class="command">vsftpd</code> serving different IP addresses, the configuration file for each copy of the <code class="command">vsftpd</code> daemon must have a different value for this directive. Refer to <a class="xref" href="#s2-ftp-vsftpd-start-multi" title="12.4.1. Starting Multiple Copies of vsftpd">Section 12.4.1, “Starting Multiple Copies of <code class="command">vsftpd</code> ”</a> for more information about multihomed FTP servers.
+ </div></div></li><li class="listitem"><div class="para">
+ <code class="command">listen_address6</code> — Specifies the IPv6 address on which <code class="command">vsftpd</code> listens for network connections when <code class="command">listen_ipv6</code> is set to <code class="command">YES</code>.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div><div class="note"><h2>Tip</h2><div class="para">
+ If running multiple copies of <code class="command">vsftpd</code> serving different IP addresses, the configuration file for each copy of the <code class="command">vsftpd</code> daemon must have a different value for this directive. Refer to <a class="xref" href="#s2-ftp-vsftpd-start-multi" title="12.4.1. Starting Multiple Copies of vsftpd">Section 12.4.1, “Starting Multiple Copies of <code class="command">vsftpd</code> ”</a> for more information about multihomed FTP servers.
+ </div></div></li><li class="listitem"><div class="para">
+ <code class="command">listen_port</code> — Specifies the port on which <code class="command">vsftpd</code> listens for network connections.
+ </div><div class="para">
+ The default value is <code class="command">21</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">local_max_rate</code> — Specifies the maximum rate data is transferred for local users logged into the server in bytes per second.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit the transfer rate.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">max_clients</code> — Specifies the maximum number of simultaneous clients allowed to connect to the server when it is running in standalone mode. Any additional client connections would result in an error message.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit connections.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">max_per_ip</code> — Specifies the maximum of clients allowed to connected from the same source IP address.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit connections.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pasv_address</code> — Specifies the IP address for the public facing IP address of the server for servers behind Network Address Translation (NAT) firewalls. This enables <code class="command">vsftpd</code> to hand out the correct return address for passive mode connections.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pasv_enable</code> — When enabled, passive mode connects are allowed.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pasv_max_port</code> — Specifies the highest possible port sent to the FTP clients for passive mode connections. This setting is used to limit the port range so that firewall rules are easier to create.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit the highest passive port range. The value must not exceed <code class="command">65535</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pasv_min_port</code> — Specifies the lowest possible port sent to the FTP clients for passive mode connections. This setting is used to limit the port range so that firewall rules are easier to create.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit the lowest passive port range. The value must not be lower <code class="command">1024</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pasv_promiscuous</code> — When enabled, data connections are not checked to make sure they are originating from the same IP address. This setting is only useful for certain types of tunneling.
+ </div><div class="warning"><h2>Caution</h2><div class="para">
+ Do not enable this option unless absolutely necessary as it disables an important security feature which verifies that passive mode connections originate from the same IP address as the control connection that initiates the data transfer.
+ </div></div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">port_enable</code> — When enabled, active mode connects are allowed.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li></ul></div></div></div><div class="section" title="12.6. Additional Resources" id="s1-ftp-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ftp-resources">12.6. Additional Resources</h2></div></div></div><a id="id707695" class="indexterm"></a><div class="para">
+ For more information about <code class="command">vsftpd</code>, refer to the following resources.
+ </div><div class="section" title="12.6.1. Installed Documentation" id="s2-ftp-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-installed-documentation">12.6.1. Installed Documentation</h3></div></div></div><a id="id707730" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="filename">/usr/share/doc/vsftpd-<em class="replaceable"><code><version-number></code></em>/</code> directory — Replace <em class="replaceable"><code><version-number></code></em> with the installed version of the <code class="filename">vsftpd</code> package. This directory contains a <code class="filename">README</code> with basic information about the software. The <code class="filename">TUNING</code> file contains basic performance tuning tips and the <code class="filename">SECURITY/</code> directory contains information about the security model employed by <code class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vsftpd</code> related man pages — There are a number of man pages for the daemon and configuration files. The following lists some of the more important man pages.
+ </div><div class="variablelist"><dl><dt><span class="term">Server Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man vsftpd</code> — Describes available command line options for <code class="command">vsftpd</code>.
+ </div></li></ul></div></dd><dt><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man vsftpd.conf</code> — Contains a detailed list of options available within the configuration file for <code class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man 5 hosts_access </code> — Describes the format and options available within the TCP wrappers configuration files: <code class="filename">hosts.allow</code> and <code class="filename">hosts.deny</code>.
+ </div></li></ul></div></dd></dl></div></li></ul></div></div><div class="section" title="12.6.2. Useful Websites" id="s2-ftp-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-useful-websites">12.6.2. Useful Websites</h3></div></div></div><a id="id932228" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://vsftpd.beasts.org/">http://vsftpd.beasts.org/</a> — The <code class="command">vsftpd</code> project page is a great place to locate the latest documentation and to contact the author of the software.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://slacksite.com/other/ftp.html">http://slacksite.com/other/ftp.html</a> — This website provides a concise explanation of the differences between active and passive mode FTP.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.ietf.org/rfc/rfc0959.txt">http://www.ietf.org/rfc/rfc0959.txt</a> — The original <em class="firstterm">Request for Comments</em> (<em class="firstterm">RFC</em>) of the FTP protocol from the IETF.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 13. Email" id="ch-email" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 13. Email</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-email-protocols">13.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-protocols-send">13.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">13.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">13.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-types-mta">13.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mda">13.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">13.2.3. Mail User Agent</a></span></dt></dl
></dd><dt><span class="section"><a href="#s1-email-mta">13.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-sendmail">13.3.1. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-postfix">13.3.2. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">13.3.3. Fetchmail</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-switchmail">13.4. Mail Transport Agent (MTA) Configuration</a></span></dt><dt><span class="section"><a href="#s1-email-mda">13.5. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">13.5.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="#s2-email-procmail-recipes">13.5.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">13.6. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">1
3.6.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">13.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">13.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">13.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-email-related-books">13.7.3. Related Books</a></span></dt></dl></dd></dl></div><a id="id815026" 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="13.1. Email Protocols" id="s1-email-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-protocols">13.1. Email Protocols</h2></div></div></div><a id="id635873" 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="13.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">13.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="13.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">13.1.1.1. SMTP</h4></div></div></div><a id="id590972" 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="13.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">13.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="13.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">13.1.2.1. POP</h4></div></div></div><a id="id610617" class="indexterm"></a><div class="para">
+ The default POP server under Fedora is <code class="command">/usr/bin/dovecot</code> and is provided by the <span class="package">dovecot</span> package. When using a POP server, email messages are downloaded by email client applications. By default, most POP 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">
+ POP 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">
+ POP 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, POP 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 POP protocol is POP3.
+ </div><div class="para">
+ There are, however, a variety of lesser-used POP protocol variants:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>APOP</em></span> — POP3 with MDS 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 xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,pt-BR" class="listitem" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,pt-BR"><div class="para">
+ <span class="emphasis"><em>KPOP</em></span> — POP3 with Kerberos authentication.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>RPOP</em></span> — POP3 with RPOP authentication. This uses a per-user ID, similar to a password, to authenticate POP requests. However, this ID is not encrypted, so RPOP is no more secure than standard POP.
+ </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">ipop3s</code> service or by using the <code class="command">/usr/sbin/stunnel</code> program. Refer to <a class="xref" href="#s2-email-security" title="13.6.1. Securing Communication">Section 13.6.1, “Securing Communication”</a> for more information.
+ </div></div><div class="section" title="13.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">13.1.2.2. IMAP</h4></div></div></div><a id="id786759" class="indexterm"></a><div class="para">
+ The default IMAP server under Fedora is <code class="command">/usr/bin/dovecot</code> and is provided by the <code class="filename">dovecot</code> package. When using an IMAP mail server, email messages remain on the server where users can read or delete them. IMAP also allows client applications to create, rename, or delete mail directories on the server to organize and store email.
+ </div><div class="para">
+ IMAP is particularly useful for those 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, IMAP client applications are capable of caching copies of messages locally, so the user can browse previously read messages when not directly connected to the IMAP server.
+ </div><div class="para">
+ IMAP, like POP, 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 <em class="firstterm">SSL</em> 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. Refer to <a class="xref" href="#s2-email-security" title="13.6.1. Securing Communication">Section 13.6.1, “Securing Communication”</a> for more information.
+ </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. A comprehensive list can be found online at <a href="http://en.wikipedia.org/wiki/List_of_mail_servers">http://en.wikipedia.org/wiki/List_of_mail_servers</a>.
+ </div></div><div class="section" title="13.1.2.3. Dovecot" id="s3-email-protocols-dovecot"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-protocols-dovecot">13.1.2.3. Dovecot</h4></div></div></div><a id="id1026562" class="indexterm"></a><div class="para">
+ The <code class="command">imap-login</code> and <code class="command">pop3-login</code> processes which implement the IMAP and POP3 protocols are spawned by the master <code class="command">dovecot</code> daemon included in the <span class="package">dovecot</span> package. The use of IMAP and POP is configured through <code class="filename">dovecot.conf</code>; by default <code class="command">dovecot</code> runs IMAP and POP3 together with their secure versions using SSL. To configure <code class="command">dovecot</code> to use POP:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Edit <code class="filename">/etc/dovecot/dovecot.conf</code> to make sure protocols variable contains pop3. For example:
+ </div><pre class="screen">protocols = imap imaps pop3 pop3s
+</pre></li><li class="listitem"><div class="para">
+ Make that change operational for the current session by running the command:
+ </div><pre class="screen">/sbin/service dovecot restart
+</pre></li><li class="listitem"><div class="para">
+ Make that change operational after the next reboot by running the command:
+ </div><pre class="screen">chkconfig dovecot on
+</pre><div class="para">
+ Please note that <code class="filename">dovecot</code> only reports that it started the IMAP server, but also starts the POP3 server.
+ </div></li></ol></div><div class="para">
+ Unlike SMTP, both of these protocols 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 SSL on dovecot:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Edit the <code class="filename">dovecot</code> configuration file <code class="filename">/etc/pki/dovecot/dovecot-openssl.conf</code> 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 dovecot self signed certificates. The 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="filename">dovecot</code> (<code class="command">/sbin/service dovecot restart</code>).
+ </div></li></ul></div>
+ More details on <code class="filename">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="13.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">13.2. Email Program Classifications</h2></div></div></div><a id="id992276" 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="13.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">13.2.1. Mail Transport Agent</h3></div></div></div><a id="id992306" class="indexterm"></a><a id="id992323" class="indexterm"></a><a id="id847992" 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 SMTP. 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 installs two MTAs—Sendmail and Postfix—email client programs are often not required to act as an MTA. Fedora also includes a special purpose MTA called Fetchmail.
+ </div><div class="para">
+ For more information on Sendmail, Postfix, and Fetchmail, refer to <a class="xref" href="#s1-email-mta" title="13.3. Mail Transport Agents">Section 13.3, “Mail Transport Agents”</a>.
+ </div></div><div class="section" title="13.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">13.2.2. Mail Delivery Agent</h3></div></div></div><a id="id795942" class="indexterm"></a><a id="id795959" class="indexterm"></a><a id="id795973" 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="13.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">13.2.3. Mail User Agent</h3></div></div></div><a id="id1772621" class="indexterm"></a><a id="id1116918" class="indexterm"></a><a id="id1116932" 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 POP or IMAP protocols, setting up mailboxes to store messages, and sending outbound messages to an MTA.
+ </div><div class="para">
+ MUAs may be graphical, such as Evolution, or have simple text-based interfaces, such as <code class="command">pine</code>.
+ </div></div></div><div class="section" title="13.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">13.3. Mail Transport Agents</h2></div></div></div><div class="para">
+ Fedora includes two primary MTAs: Sendmail and Postfix. Postfix is configured as the default MTA, although it is easy to switch the default MTA to Sendmail.
+ </div><div class="section" title="13.3.1. Sendmail" id="s2-email-mta-sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-mta-sendmail">13.3.1. Sendmail</h3></div></div></div><a id="id756468" class="indexterm"></a><a id="id756481" class="indexterm"></a><div class="para">
+ Sendmail's core purpose, like other MTAs, is to safely transfer email among hosts, usually using the SMTP 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="13.3.1.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">13.3.1.1. Purpose and Limitations</h4></div></div></div><a id="id865345" class="indexterm"></a><a id="id865358" 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 POP or IMAP, 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="13.7. Additional Resources">Section 13.7, “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="13.3.1.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">13.3.1.2. The Default Sendmail Installation</h4></div></div></div><a id="id886047" class="indexterm"></a><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 the root user:
+ </div><pre class="screen">yum install m4</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="13.3.1.3. Common Sendmail Configuration Changes">Section 13.3.1.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. Restarting the <span class="application"><strong>sendmail</strong></span> service will cause the configuration changes to take effect:
+ </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">service sendmail restart</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="13.3.1.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">13.3.1.3. Common Sendmail Configuration Changes</h4></div></div></div><a id="id929805" class="indexterm"></a><a id="id929818" 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"><h2>Caution</h2><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 class="para">
+ To add the desired functionality to Sendmail, edit the <code class="filename">/etc/mail/sendmail.mc</code> file as the root user. Once you are finished, restart the <span class="application"><strong>Sendmail</strong></span> service and, if the <span class="package">m4</span> package is installed, the m4 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"><h2>Important</h2><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 class="para">
+ The default configuration which ships with Fedora works for most SMTP-only sites. However, it does not work for UUCP (UNIX to UNIX Copy) 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> 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 <code class="filename">/etc/mail/sendmail.cf</code> files.
+ </div></div><div class="section" title="13.3.1.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">13.3.1.4. Masquerading</h4></div></div></div><a id="id717924" class="indexterm"></a><a id="id717938" 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 <code class="command">m4</code>, 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="13.3.1.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">13.3.1.5. Stopping Spam</h4></div></div></div><a id="id1127836" 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, relaying denial (default from version 8.9), access database and sender information checks.</em>
+ </div><div class="para">
+ For example, forwarding of SMTP 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><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 <code class="filename">/etc/mail/access.db</code> is a database, use <code class="command">makemap</code> to activate 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. SMTP servers store information about an emails journey in the message header. As the message travels from one MTA to another, each puts in a "Received" header above all the other Received headers. It is however 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="13.5.2.6. Spam Filters">Section 13.5.2.6, “Spam Filters”</a> for more about using SpamAssassin.
+ </div></div><div class="section" title="13.3.1.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">13.3.1.6. Using Sendmail with LDAP</h4></div></div></div><a id="id738967" class="indexterm"></a><div class="para">
+ Using the <em class="firstterm">Lightweight Directory Access Protocol (LDAP)</em> is a very quick and powerful way to find specific information about a particular user from a much larger group. For example, an LDAP 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, LDAP is largely separate from Sendmail, with LDAP storing the hierarchical user information and Sendmail only being given the result of LDAP queries in pre-addressed email messages.
+ </div><div class="para">
+ However, Sendmail supports a much greater integration with LDAP, where it uses LDAP to replace separately maintained files, such as <code class="filename">aliases</code> and <code class="filename">virtusertables</code>, on different mail servers that work together to support a medium- to enterprise-level organization. In short, LDAP abstracts the mail routing level from Sendmail and its separate configuration files to a powerful LDAP cluster that can be leveraged by many different applications.
+ </div><div class="para">
+ The current version of Sendmail contains support for LDAP. To extend the Sendmail server using LDAP, first get an LDAP 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"><h2>Note</h2><div class="para">
+ This is only for a very basic configuration of Sendmail with LDAP. The configuration can differ greatly from this depending on the implementation of LDAP, especially when configuring several Sendmail machines to use a common LDAP server.
+ </div><div class="para">
+ Consult <code class="filename">/usr/share/sendmail-cf/README</code> for detailed LDAP routing configuration instructions and examples.
+ </div></div><div class="para">
+ Next, recreate the <code class="filename">/etc/mail/sendmail.cf</code> file by running <code class="command">m4</code> and again restarting Sendmail. Refer to <a class="xref" href="#s3-email-mta-sendmail-changes" title="13.3.1.3. Common Sendmail Configuration Changes">Section 13.3.1.3, “Common Sendmail Configuration Changes”</a> for instructions.
+ </div><div class="para">
+ For more information on LDAP, refer to <a class="xref" href="#ch-Lightweight_Directory_Access_Protocol_LDAP" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)">Chapter 14, <i>Lightweight Directory Access Protocol (LDAP)</i></a>.
+ </div></div></div><div class="section" title="13.3.2. Postfix" id="s2-email-mta-postfix"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-mta-postfix">13.3.2. Postfix</h3></div></div></div><a id="id1744281" class="indexterm"></a><a id="id1744295" 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="13.3.2.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">13.3.2.1. The Default Postfix Installation</h4></div></div></div><a id="id1685133" 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">aliases</code> — A configurable list required by the mail protocol.
+ </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="important"><h2>Important</h2><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="13.3.2.2. Basic Postfix Configuration">Section 13.3.2.2, “Basic Postfix Configuration”</a>.
+ </div></div><div class="para">
+ When changing some options within files in the <code class="filename">/etc/postfix/</code> directory, it may be necessary to restart the <code class="command">postfix</code> service for the changes to take effect. The easiest way to do this is to type the following command:
+ </div><pre class="screen">
+<code class="command">/sbin/service postfix restart</code>
+</pre></div><div class="section" title="13.3.2.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">13.3.2.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 mark (<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 <code class="filename">/etc/postfix/main.cf</code>. Additional resources including information about LDAP and SpamAssassin integration are available online at <a href="http://www.postfix.org/">http://www.postfix.org/</a>.
+ </div></div></div><div class="section" title="13.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">13.3.3. Fetchmail</h3></div></div></div><a id="id589067" class="indexterm"></a><a id="id690627" 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 POP3 and IMAP. It can even forward email messages to an SMTP server, if necessary.
+ </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.
+ </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 25 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="13.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">13.3.3.1. Fetchmail Configuration Options</h4></div></div></div><a id="id655710" class="indexterm"></a><a id="id655724" 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 <code class="filename">.fetchmailrc</code> because it only checks skipped servers when specifically invoked, and does not affect any currently working configurations.
+ </div><div class="para">
+ A sample <code class="filename">.fetchmailrc</code> file looks similar to the following example:
+ </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 POP3, 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"><h2>Note</h2><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 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 here.
+ </div></div><div class="section" title="13.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">13.3.3.2. Global Options</h4></div></div></div><a id="id763002" class="indexterm"></a><a id="id1711773" 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="13.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">13.3.3.3. Server Options</h4></div></div></div><a id="id850921" class="indexterm"></a><a id="id1026183" 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="13.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">13.3.3.4. User Options</h4></div></div></div><a id="id771117" class="indexterm"></a><a id="id771136" 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="13.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">13.3.3.5. Fetchmail Command Options</h4></div></div></div><a id="id703024" 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="13.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">13.3.3.6. Informational or Debugging Options</h4></div></div></div><a id="id703080" 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="13.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">13.3.3.7. Special Options</h4></div></div></div><a id="id705373" 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><div class="section" title="13.4. Mail Transport Agent (MTA) Configuration" id="s1-email-switchmail"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-switchmail">13.4. Mail Transport Agent (MTA) Configuration</h2></div></div></div><a id="id1755904" class="indexterm"></a><a id="id1755918" class="indexterm"></a><a id="id844207" class="indexterm"></a><a id="id844225" class="indexterm"></a><a id="id844249" class="indexterm"></a><a id="id844259" 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="id1000466" class="indexterm"></a><a id="id1000476" class="indexterm"></a><div class="para">
+ Fedora 13 provides two MTAs: Sendmail and Postfix. If both are installed, <code class="command">postfix</code> is the default MTA.
+ </div></div><div class="section" title="13.5. Mail Delivery Agents" id="s1-email-mda"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-mda">13.5. 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.
+ </div><a id="id1535248" class="indexterm"></a><a id="id1535261" 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">
+ 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 <code class="filename">/etc/procmailrc</code> 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="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="section" title="13.5.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">13.5.1. Procmail Configuration</h3></div></div></div><a id="id891995" class="indexterm"></a><a id="id892009" 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 <code class="filename">.procmailrc</code> 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">
+ If the user wants to turn off Procmail filtering of their email lists but leave spam control in place, they would comment out the first <code class="command">INCLUDERC</code> line with a hash mark character (<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 eight 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 1024 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="13.5.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">13.5.2. Procmail Recipes</h3></div></div></div><a id="id845093" 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="13.5.2.5. Recipe Examples">Section 13.5.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 <code class="command">*</code> character can further control the condition.
+ </div><div class="para">
+ The <code class="command"><em class="replaceable"><code><action-to-perform></code></em> </code> 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="13.5.2.4. Special Conditions and Actions">Section 13.5.2.4, “Special Conditions and Actions”</a> for more information.
+ </div><div class="section" title="13.5.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">13.5.2.1. Delivering vs. Non-Delivering Recipes</h4></div></div></div><a id="id699017" class="indexterm"></a><a id="id699036" 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="13.5.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">13.5.2.2. Flags</h4></div></div></div><a id="id871801" 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 occurs by default.
+ </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="13.5.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">13.5.2.3. Specifying a Local Lockfile</h4></div></div></div><a id="id871649" 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="13.5.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">13.5.2.4. Special Conditions and Actions</h4></div></div></div><a id="id852322" class="indexterm"></a><a id="id852340" 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 <code class="command">*</code> character 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="13.5.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">13.5.2.5. Recipe Examples</h4></div></div></div><a id="id643862" 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"><h2>Caution</h2><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 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="13.7. Additional Resources">Section 13.7, “Additional Resources”</a> for more detailed and powerful recipes.
+ </div></div><div class="section" title="13.5.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">13.5.2.6. Spam Filters</h4></div></div></div><a id="id888375" class="indexterm"></a><a id="id888394" class="indexterm"></a><a id="id827553" 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="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="command">spamd</code>) and client application (<code class="command">spamc</code>). Configuring SpamAssassin this way, however, requires root access to the host.
+ </div><div class="para">
+ To start the <code class="command">spamd</code> daemon, type the following command as root:
+ </div><pre class="screen">
+<code class="command">/sbin/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 6. Controlling Access to Services">Chapter 6, <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="13.6. Mail User Agents" id="s1-email-mua"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-mua">13.6. Mail User Agents</h2></div></div></div><div class="para">
+ There are scores of mail programs available under Fedora. There are full-featured, graphical email client programs, such as <span class="application"><strong>Evolution</strong></span>, as well as 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 the client and server.
+ </div><div class="section" title="13.6.1. Securing Communication" id="s2-email-security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-security">13.6.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="id807537" 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 POP and IMAP 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="13.6.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">13.6.1.1. Secure Email Clients</h4></div></div></div><a id="id807568" 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 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 IMAP and POP have known port numbers (993 and 995, respectively) that the MUA uses to authenticate and download messages.
+ </div></div><div class="section" title="13.6.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">13.6.1.2. Securing Email Client Communications</h4></div></div></div><a id="id711064" class="indexterm"></a><a id="id711083" class="indexterm"></a><div class="para">
+ Offering SSL encryption to IMAP and POP users on the email server is a simple matter.
+ </div><div class="para">
+ First, create an SSL certificate. This can be done 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"><h2>Caution</h2><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 class="para">
+ To create a self-signed SSL certificate for IMAP, change to the <code class="filename">/etc/pki/tls/certs/</code> directory and type the following commands as root:
+ </div><pre class="screen">
+<code class="command">rm -f cyrus-imapd.pem make cyrus-imapd.pem</code>
+</pre><div class="para">
+ Answer all of the questions to complete the process.
+ </div><div class="para">
+ To create a self-signed SSL certificate for POP, change to the <code class="filename">/etc/pki/tls/certs/</code> directory, and type the following commands as root:
+ </div><pre class="screen">
+<code class="command">rm -f ipop3d.pem make ipop3d.pem</code>
+</pre><div class="para">
+ Again, answer all of the questions to complete the process.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Please be sure to remove the default <code class="filename">imapd.pem</code> and <code class="filename">ipop3d.pem</code> files before issuing each <code class="command">make</code> command.
+ </div></div><div class="para">
+ Once finished, execute the <code class="command">/sbin/service xinetd restart</code> command to restart the <code class="command">xinetd</code> daemon which controls <code class="command">imapd</code> and <code class="command">ipop3d</code>.
+ </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 daemons, <code class="command">imapd</code> or <code class="command">pop3d</code>.
+ </div><div class="para">
+ The <code class="command">stunnel</code> program uses external OpenSSL libraries included with Fedora to provide strong cryptography and protect the connections. It is best to apply to a CA to obtain an SSL certificate, but it is also possible to create a self-signed certificate.
+ </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">
+<code class="command">make stunnel.pem</code>
+</pre><div class="para">
+ Again, answer all of the questions to complete the process.
+ </div><div class="para">
+ Once the certificate is generated, it is possible to use the <code class="command">stunnel</code> command to start the <code class="command">imapd</code> mail daemon using the following command:
+ </div><pre class="screen">
+<code class="command">/usr/sbin/stunnel -d 993 -l /usr/sbin/imapd imapd</code>
+</pre><div class="para">
+ Once this command is issued, it is possible to open an IMAP email client and connect to the email server using SSL encryption.
+ </div><div class="para">
+ To start the <code class="command">pop3d</code> using the <code class="command">stunnel</code> command, type the following command:
+ </div><pre class="screen">
+<code class="command">/usr/sbin/stunnel -d 995 -l /usr/sbin/pop3d pop3d</code>
+</pre><div class="para">
+ For more information about how to use <code class="command">stunnel</code>, read the <code class="command">stunnel</code> man page or refer to 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 for <code class="command">stunnel</code>.
+ </div></div></div></div><div class="section" title="13.7. 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">13.7. Additional Resources</h2></div></div></div><a id="id986595" class="indexterm"></a><a id="id986610" class="indexterm"></a><a id="id698260" class="indexterm"></a><a id="id698274" class="indexterm"></a><div class="para">
+ The following is a list of additional documentation about email applications.
+ </div><div class="section" title="13.7.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">13.7.1. Installed Documentation</h3></div></div></div><a id="id698303" 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 <code class="command">m4</code>, 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="13.7.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">13.7.2. Useful Websites</h3></div></div></div><a id="id839798" 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="13.7.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">13.7.3. Related Books</h3></div></div></div><a id="id778248" 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 xml:lang="en-US" class="chapter" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" id="ch-Lightweight_Directory_Access_Protocol_LDAP" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 14. Lightweight Directory Access Protocol (LDAP)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-ldap-adv">14.1. Why Use LDAP?</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ldap-v3">14.1.1. OpenLDAP Features</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ldap-terminology">14.2. LDAP Terminology</a></span></dt><dt><span class="section"><a href="#s1-ldap-daemonsutils">14.3. OpenLDAP Daemons and Utilities</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-pam-nss">14.3.1. NSS, PAM, and LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-other-apps">14.3.2. PHP4, LDAP, and the Apache HTTP Server</a></span></dt><dt><
span class="section"><a href="#s2-ldap-applications">14.3.3. LDAP Client Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ldap-files">14.4. OpenLDAP Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-ldap-files-schemas">14.5. The <code class="filename">/etc/openldap/schema/</code> Directory</a></span></dt><dt><span class="section"><a href="#s1-ldap-quickstart">14.6. OpenLDAP Setup Overview</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-files-slapd-conf">14.6.1. Editing <code class="filename">/etc/openldap/slapd.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ldap-pam">14.7. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-pamd">14.7.1. PAM and LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-migrate">14.7.2. Migrating Old Authentication Information to LDAP Format</a></span></dt></dl></dd><dt><
span class="section"><a href="#s1-ldap-migrate">14.8. Migrating Directories from Earlier Releases</a></span></dt><dt><span class="section"><a href="#s1-ldap-additional-resources">14.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-installed-docs">14.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-ldap-additional-resources-web">14.9.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-ldap-related-books">14.9.3. Related Books</a></span></dt></dl></dd></dl></div><a id="id622644" class="indexterm"></a><a id="id1774540" class="indexterm"></a><a id="id894909" class="indexterm"></a><a id="id882131" class="indexterm"></a><a id="id936483" class="indexterm"></a><a id="id780901" class="indexterm"></a><a id="id936464" class="indexterm"></a><div class="para">
+ The <em class="firstterm">Lightweight Directory Access Protocol</em> (<em class="firstterm">LDAP</em>) is a set of open protocols used to access centrally stored information over a network. It is based on the <em class="firstterm">X.500</em> standard for directory sharing, but is less complex and resource-intensive. For this reason, LDAP is sometimes referred to as "<em class="firstterm">X.500 Lite</em>." The X.500 standard is a directory that contains hierarchical and categorized information, which could include information such as names, addresses, and phone numbers.
+ </div><div class="para">
+ Like X.500, LDAP organizes information in a hierarchal manner using directories. These directories can store a variety of information and can even be used in a manner similar to the Network Information Service (NIS), enabling anyone to access their account from any machine on the LDAP enabled network.
+ </div><div class="para">
+ In many cases, LDAP is used as a virtual phone directory, allowing users to easily access contact information for other users. But LDAP is more flexible than a traditional phone directory, as it is capable of referring a querent to other LDAP servers throughout the world, providing an ad-hoc global repository of information. Currently, however, LDAP is more commonly used within individual organizations, like universities, government departments, and private companies.
+ </div><div class="para">
+ LDAP is a client/server system. The server can use a variety of databases to store a directory, each optimized for quick and copious read operations. When an LDAP client application connects to an LDAP server, it can either query a directory or attempt to modify it. In the event of a query, the server either answers the query locally, or it can refer the querent to an LDAP server which does have the answer. If the client application is attempting to modify information within an LDAP directory, the server verifies that the user has permission to make the change and then adds or updates the information.
+ </div><div class="para">
+ This chapter refers to the configuration and use of OpenLDAP 2.0, an open source implementation of the LDAPv2 and LDAPv3 protocols.
+ </div><div class="section" title="14.1. Why Use LDAP?" id="s1-ldap-adv"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-adv">14.1. Why Use LDAP?</h2></div></div></div><a id="id993375" class="indexterm"></a><div class="para">
+ The main benefit of using LDAP is that information for an entire organization can be consolidated into a central repository. For example, rather than managing user lists for each group within an organization, LDAP can be used as a central directory accessible from anywhere on the network. And because LDAP supports Secure Sockets Layer (SSL) and Transport Layer Security (TLS), sensitive data can be protected from prying eyes.
+ </div><div class="para">
+ LDAP also supports a number of back-end databases in which to store directories. This allows administrators the flexibility to deploy the database best suited for the type of information the server is to disseminate. Because LDAP also has a well-defined client Application Programming Interface (API), the number of LDAP-enabled applications are numerous and increasing in quantity and quality.
+ </div><div class="section" title="14.1.1. OpenLDAP Features" id="s1-ldap-v3"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-ldap-v3">14.1.1. OpenLDAP Features</h3></div></div></div><a id="id627534" class="indexterm"></a><div class="para">
+ OpenLDAP includes a number of important features.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>LDAPv3 Support</em></span> — OpenLDAP supports Simple Authentication and Security Layer (SASL), Transport Layer Security (TLS), and Secure Sockets Layer (SSL), among other improvements. Many of the changes in the protocol since LDAPv2 are designed to make LDAP more secure.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>IPv6 Support</em></span> — OpenLDAP supports the next generation Internet Protocol version 6.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>LDAP Over IPC</em></span> — OpenLDAP can communicate within a system using interprocess communication (IPC). This enhances security by eliminating the need to communicate over a network.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Updated C API</em></span> — Improves the way programmers can connect to and use LDAP directory servers.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>LDIFv1 Support</em></span> — Provides full compliance with the LDAP Data Interchange Format (LDIF) version 1.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Enhanced Stand-Alone LDAP Server</em></span> — Includes an updated access control system, thread pooling, better tools, and much more.
+ </div></li></ul></div></div></div><div class="section" title="14.2. LDAP Terminology" id="s1-ldap-terminology"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-terminology">14.2. LDAP Terminology</h2></div></div></div><a id="id578126" class="indexterm"></a><a id="id578139" class="indexterm"></a><div class="para">
+ Any discussion of LDAP requires a basic understanding of a set of LDAP-specific terms:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="firstterm">entry</em> — A single unit within an LDAP directory. Each entry is identified by its unique <em class="firstterm">Distinguished Name (DN)</em>.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">attributes</em> — Information directly associated with an entry. For example, an organization could be represented as an LDAP entry. Attributes associated with the organization might include a fax number, an address, and so on. People can also be represented as entries in an LDAP directory, with common attributes such as the person's telephone number and email address.
+ </div><div class="para">
+ Some attributes are required, while other attributes are optional. An <em class="firstterm">objectclass</em> definition sets which attributes are required for each entry. Objectclass definitions are found in various schema files, located in the <code class="filename">/etc/openldap/schema/</code> directory. For more information, refer to <a class="xref" href="#s1-ldap-files-schemas" title="14.5. The /etc/openldap/schema/ Directory">Section 14.5, “The <code class="filename">/etc/openldap/schema/</code> Directory”</a>.
+ </div><div class="para">
+ The assertion of an attribute and its corresponding value is also referred to as a <em class="firstterm">Relative Distinguished Name</em> (RDN). An RDN is only unique per entry, whereas a DN is globally unique.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">LDIF</em> — The <em class="firstterm">LDAP Data Interchange Format</em> (LDIF) is an ASCII text representation of LDAP entries. Files used for importing data to LDAP servers must be in LDIF format. An LDIF entry looks similar to the following example:
+ </div><pre class="screen">
+[<<em class="replaceable"><code>id</code></em>>] dn: <<em class="replaceable"><code>distinguished name</code></em>>
+<<em class="replaceable"><code>attrtype</code></em>>: <<em class="replaceable"><code>attrvalue</code></em>>
+<<em class="replaceable"><code>attrtype</code></em>>: <<em class="replaceable"><code>attrvalue</code></em>>
+<<em class="replaceable"><code>attrtype</code></em>>: <<em class="replaceable"><code>attrvalue</code></em>>
+</pre><div class="para">
+ Each entry can contain as many <code class="command"><<em class="replaceable"><code>attrtype</code></em>>: <<em class="replaceable"><code>attrvalue</code></em>></code> pairs as needed. A blank line indicates the end of an entry.
+ </div><div class="warning"><h2>Caution</h2><div class="para">
+ All <code class="command"><<em class="replaceable"><code>attrtype</code></em>></code> and <code class="command"><<em class="replaceable"><code>attrvalue</code></em>></code> pairs <span class="emphasis"><em>must</em></span> be defined in a corresponding schema file to use this information.
+ </div></div><div class="para">
+ Any value enclosed within a <code class="command"><</code> and a <code class="command">></code> is a variable and can be set whenever a new LDAP entry is created. This rule does not apply, however, to <code class="command"><<em class="replaceable"><code>id</code></em>></code>. The <code class="command"><<em class="replaceable"><code>id</code></em>></code> is a number determined by the application used to edit the entry.
+ </div></li></ul></div></div><div class="section" title="14.3. OpenLDAP Daemons and Utilities" id="s1-ldap-daemonsutils"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-daemonsutils">14.3. OpenLDAP Daemons and Utilities</h2></div></div></div><a id="id958405" class="indexterm"></a><a id="id958418" class="indexterm"></a><a id="id945757" class="indexterm"></a><a id="id945775" class="indexterm"></a><a id="id945793" class="indexterm"></a><a id="id1286057" class="indexterm"></a><a id="id1286075" class="indexterm"></a><a id="id1286097" class="indexterm"></a><a id="id922147" class="indexterm"></a><a id="id922168" class="indexterm"></a><a id="id922186" class="indexterm"></a><a id="id990820" class="indexterm"></a><a id="id990837" class="indexterm"></a><a id="id990859" class="indexterm"></a><a id="id620309" class="indexterm"></a><a id="id620331" class="indexterm"></a><a id="id620348" class="indexterm"></a><a id="id695557" class="
indexterm"></a><a id="id695575" class="indexterm"></a><a id="id734909" class="indexterm"></a><a id="id734927" class="indexterm"></a><a id="id734948" class="indexterm"></a><a id="id1125682" class="indexterm"></a><a id="id1125703" class="indexterm"></a><a id="id1125721" class="indexterm"></a><div class="para">
+ The suite of OpenLDAP libraries and tools are included within the following packages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">openldap</code> — Contains the libraries necessary to run the OpenLDAP server and client applications.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">openldap-clients</code> — Contains command line tools for viewing and modifying directories on an LDAP server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">openldap-servers</code> — Contains the servers and other utilities necessary to configure and run an LDAP server.
+ </div></li></ul></div><div class="para">
+ There are two servers contained in the <code class="filename">openldap-servers</code> package: the <em class="firstterm">Standalone LDAP Daemon</em> (<code class="command">/usr/sbin/slapd</code>) and the <em class="firstterm">Standalone LDAP Update Replication Daemon</em> (<code class="command">/usr/sbin/slurpd</code>).
+ </div><div class="para">
+ The <code class="command">slapd</code> daemon is the standalone LDAP server while the <code class="command">slurpd</code> daemon is used to synchronize changes from one LDAP server to other LDAP servers on the network. The <code class="command">slurpd</code> daemon is only used when dealing with multiple LDAP servers.
+ </div><div class="para">
+ To perform administrative tasks, the <code class="filename">openldap-servers</code> package installs the following utilities into the <code class="filename">/usr/sbin/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">slapadd</code> — Adds entries from an LDIF file to an LDAP directory. For example, the command <code class="command">/usr/sbin/slapadd -l <em class="replaceable"><code>ldif-input</code></em> </code> reads in the LDIF file, <code class="filename"><em class="replaceable"><code>ldif-input</code></em> </code>, containing the new entries.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Only the root user may use <code class="command">/usr/sbin/slapadd</code>. However, the directory server runs as the <code class="filename">ldap</code> user. Therefore the directory server is unable to modify any files created by <code class="command">slapadd</code>. To correct this issue, after using <code class="command">slapadd</code>, type the following command:
+ </div><pre class="screen">chown -R ldap /var/lib/ldap</pre></div></li><li class="listitem"><div class="para">
+ <code class="command">slapcat</code> — Pulls entries from an LDAP directory in the default format, <em class="firstterm">Sleepycat Software's Berkeley DB</em> system, and saves them in an LDIF file. For example, the command <code class="command">/usr/sbin/slapcat -l <em class="replaceable"><code>ldif-output</code></em> </code> outputs an LDIF file called <code class="filename"><em class="replaceable"><code>ldif-output</code></em> </code> containing the entries from the LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">slapindex</code> — Re-indexes the <code class="command">slapd</code> directory based on the current content. This tool should be run whenever indexing options within <code class="filename">/etc/openldap/slapd.conf</code> are changed.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">slappasswd</code> — Generates an encrypted user password value for use with <code class="command">ldapmodify</code> or the <code class="command">rootpw</code> value in the <code class="command">slapd</code> configuration file, <code class="filename">/etc/openldap/slapd.conf</code>. Execute the <code class="command">/usr/sbin/slappasswd</code> command to create the password.
+ </div></li></ul></div><div class="warning"><h2>Warning</h2><div class="para">
+ You must stop <code class="command">slapd</code> by issuing the <code class="command">/sbin/service ldap stop</code> command before using <code class="command">slapadd</code>, <code class="command">slapcat</code> or <code class="command">slapindex</code>. Otherwise, the integrity of the LDAP directory is at risk.
+ </div></div><div class="para">
+ For more information on using these utilities, refer to their respective man pages.
+ </div><div class="para">
+ The <code class="filename">openldap-clients</code> package installs tools into <code class="filename">/usr/bin/</code> which are used to add, modify, and delete entries in an LDAP directory. These tools include the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">ldapadd</code> — Adds entries to an LDAP directory by accepting input via a file or standard input; <code class="command">ldapadd</code> is actually a hard link to <code class="command">ldapmodify -a</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapdelete</code> — Deletes entries from an LDAP directory by accepting user input at a shell prompt or via a file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapmodify</code> — Modifies entries in an LDAP directory, accepting input via a file or standard input.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldappasswd</code> — Sets the password for an LDAP user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapsearch</code> — Searches for entries in an LDAP directory using a shell prompt.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapcompare</code> — Opens a connection to an LDAP server, binds, and performs a comparison using specified parameters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapwhoami</code> — Opens a connection to an LDAP server, binds, and performs a <code class="command">whoami</code> operation.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapmodrdn</code> — Opens a connection to an LDAP server, binds, and modifies the RDNs of entries.
+ </div></li></ul></div><div class="para">
+ With the exception of <code class="command">ldapsearch</code>, each of these utilities is more easily used by referencing a file containing the changes to be made rather than typing a command for each entry to be changed within an LDAP directory. The format of such a file is outlined in the man page for each utility.
+ </div><div class="section" title="14.3.1. NSS, PAM, and LDAP" id="s2-ldap-pam-nss"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-pam-nss">14.3.1. NSS, PAM, and LDAP</h3></div></div></div><a id="id654964" class="indexterm"></a><a id="id654977" class="indexterm"></a><div class="para">
+ In addition to the OpenLDAP packages, Fedora includes a package called <code class="filename">nss_ldap</code>, which enhances LDAP's ability to integrate into both Linux and other UNIX environments.
+ </div><div class="para">
+ The <code class="filename">nss_ldap</code> package provides the following modules (where <em class="replaceable"><code><version></code></em> refers to the version of <code class="filename">libnss_ldap</code> in use):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/lib/libnss_ldap-<em class="replaceable"><code><version></code></em>.so</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/lib/security/pam_ldap.so</code>
+ </div></li></ul></div><div class="para">
+ The <code class="filename">nss_ldap</code> package provides the following modules for 64-bit architectures:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/lib64/libnss_ldap-<em class="replaceable"><code><version></code></em>.so</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/lib64/security/pam_ldap.so</code>
+ </div></li></ul></div><div class="para">
+ The <code class="filename">libnss_ldap-<em class="replaceable"><code><version></code></em>.so</code> module allows applications to look up users, groups, hosts, and other information using an LDAP directory via the <em class="firstterm">Nameservice Switch</em> (NSS) interface of <code class="command">glibc</code>. NSS allows applications to authenticate using LDAP in conjunction with the NIS name service and flat authentication files.
+ </div><div class="para">
+ The <code class="filename">pam_ldap</code> module allows PAM-aware applications to authenticate users using information stored in an LDAP directory. PAM-aware applications include console login, POP and IMAP mail servers, and Samba. By deploying an LDAP server on a network, all of these applications can authenticate using the same user ID and password combination, greatly simplifying administration.
+ </div><div class="para">
+ For more information about configuring PAM, refer to refer to the <em class="citetitle">Pluggable Authentication Modules (PAM)</em> chapter of the Fedora 13 6 <em class="citetitle">Security Guide</em> and the PAM man pages.
+ </div></div><div class="section" title="14.3.2. PHP4, LDAP, and the Apache HTTP Server" id="s2-ldap-other-apps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-other-apps">14.3.2. PHP4, LDAP, and the Apache HTTP Server</h3></div></div></div><a id="id883822" class="indexterm"></a><a id="id1778510" class="indexterm"></a><div class="para">
+ Fedora includes a package containing an LDAP module for the PHP server-side scripting language.
+ </div><div class="para">
+ The <code class="filename">php-ldap</code> package adds LDAP support to the PHP4 HTML-embedded scripting language via the <code class="filename">/usr/lib/php4/ldap.so</code> module. This module allows PHP4 scripts to access information stored in an LDAP directory.
+ </div><div class="para">
+ Fedora ships with the <code class="filename">mod_authz_ldap</code> module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. The <code class="filename">mod_ssl</code> module is required when using the <code class="filename">mod_authz_ldap</code> module.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ The <code class="filename">mod_authz_ldap</code> module does not authenticate a user to an LDAP directory using an encrypted password hash. This functionality is provided by the experimental <code class="filename">mod_auth_ldap</code> module, which is not included with Fedora. Refer to the Apache Software Foundation website online at <a href="http://www.apache.org/">http://www.apache.org/</a> for details on the status of this module.
+ </div></div></div><div class="section" title="14.3.3. LDAP Client Applications" id="s2-ldap-applications"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-applications">14.3.3. LDAP Client Applications</h3></div></div></div><a id="id812970" class="indexterm"></a><div class="para">
+ There are graphical LDAP clients available which support creating and modifying directories, but they are <span class="emphasis"><em>not</em></span> included with Fedora.
+ </div><div class="para">
+ Other LDAP clients access directories as read-only, using them to reference, but not alter, organization-wide information. Some examples of such applications are Sendmail, <span class="application"><strong>Mozilla</strong></span>, <span class="application"><strong>Ekiga</strong></span>, and <span class="application"><strong>Evolution</strong></span>.
+ </div></div></div><div class="section" title="14.4. OpenLDAP Configuration Files" id="s1-ldap-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-files">14.4. OpenLDAP Configuration Files</h2></div></div></div><a id="id1487208" class="indexterm"></a><a id="id1487231" class="indexterm"></a><a id="id891824" class="indexterm"></a><a id="id891847" class="indexterm"></a><div class="para">
+ OpenLDAP configuration files are installed into the <code class="filename">/etc/openldap/</code> directory. The following is a brief list highlighting the most important directories and files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/etc/openldap/ldap.conf</code> — This is the configuration file for all <span class="emphasis"><em>client</em></span> applications which use the OpenLDAP libraries such as <code class="command">ldapsearch</code>, <code class="command">ldapadd</code>, Sendmail, <span class="application"><strong>Evolution</strong></span>, and <span class="application"><strong>Ekiga</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/openldap/slapd.conf</code> — This is the configuration file for the <code class="command">slapd</code> daemon. Refer to <a class="xref" href="#s2-ldap-files-slapd-conf" title="14.6.1. Editing /etc/openldap/slapd.conf">Section 14.6.1, “Editing <code class="filename">/etc/openldap/slapd.conf</code> ”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/openldap/schema/</code> directory — This subdirectory contains the schema used by the <code class="command">slapd</code> daemon. Refer to <a class="xref" href="#s1-ldap-files-schemas" title="14.5. The /etc/openldap/schema/ Directory">Section 14.5, “The <code class="filename">/etc/openldap/schema/</code> Directory”</a> for more information.
+ </div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
+ If the <code class="filename">nss_ldap</code> package is installed, it creates a file named <code class="filename">/etc/ldap.conf</code>. This file is used by the PAM and NSS modules supplied by the <code class="filename">nss_ldap</code> package. Refer to <a class="xref" href="#s1-ldap-pam" title="14.7. Configuring a System to Authenticate Using OpenLDAP">Section 14.7, “Configuring a System to Authenticate Using OpenLDAP”</a> for more information.
+ </div></div></div><div class="section" title="14.5. The /etc/openldap/schema/ Directory" id="s1-ldap-files-schemas"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-files-schemas">14.5. The <code class="filename">/etc/openldap/schema/</code> Directory</h2></div></div></div><a id="id683175" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/openldap/schema/</code> directory holds LDAP definitions, previously located in the <code class="filename">slapd.at.conf</code> and <code class="filename">slapd.oc.conf</code> files. The <code class="filename">/etc/openldap/schema/redhat/</code> directory holds customized schemas distributed by Red Hat for Fedora.
+ </div><div class="para">
+ All <em class="firstterm">attribute syntax definitions</em> and <em class="firstterm">objectclass definitions</em> are now located in the different schema files. The various schema files are referenced in <code class="filename">/etc/openldap/slapd.conf</code> using <code class="filename">include</code> lines, as shown in this example:
+ </div><pre class="screen">
+include /etc/openldap/schema/core.schema
+include /etc/openldap/schema/cosine.schema
+include /etc/openldap/schema/inetorgperson.schema
+include /etc/openldap/schema/nis.schema
+include /etc/openldap/schema/rfc822-MailMember.schema
+include /etc/openldap/schema/redhat/autofs.schema
+</pre><div class="warning"><h2>Caution</h2><div class="para">
+ Do not modify schema items defined in the schema files installed by OpenLDAP.
+ </div></div><div class="para">
+ It is possible to extend the schema used by OpenLDAP to support additional attribute types and object classes using the default schema files as a guide. To do this, create a <code class="filename">local.schema</code> file in the <code class="filename">/etc/openldap/schema/</code> directory. Reference this new schema within <code class="filename">slapd.conf</code> by adding the following line below the default <code class="filename">include</code> schema lines:
+ </div><pre class="screen">include /etc/openldap/schema/local.schema</pre><div class="para">
+ Next, define new attribute types and object classes within the <code class="filename">local.schema</code> file. Many organizations use existing attribute types from the schema files installed by default and add new object classes to the <code class="filename">local.schema</code> file.
+ </div><div class="para">
+ Extending the schema to match certain specialized requirements is quite involved and beyond the scope of this chapter. Refer to <a href="http://www.openldap.org/doc/admin/schema.html">http://www.openldap.org/doc/admin/schema.html</a> for information.
+ </div></div><div class="section" title="14.6. OpenLDAP Setup Overview" id="s1-ldap-quickstart"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-quickstart">14.6. OpenLDAP Setup Overview</h2></div></div></div><a id="id2006570" class="indexterm"></a><div class="para">
+ This section provides a quick overview for installing and configuring an OpenLDAP directory. For more details, refer to the following URLs:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.openldap.org/doc/admin/quickstart.html">http://www.openldap.org/doc/admin/quickstart.html</a> — The <em class="citetitle">Quick-Start Guide</em> on the OpenLDAP website.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.tldp.org/HOWTO/LDAP-HOWTO/index.html">http://www.tldp.org/HOWTO/LDAP-HOWTO/index.html</a> — The <em class="citetitle">LDAP Linux HOWTO</em> from the Linux Documentation Project.
+ </div></li></ul></div><div class="para">
+ The basic steps for creating an LDAP server are as follows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Install the <code class="filename">openldap</code>, <code class="filename">openldap-servers</code>, and <code class="filename">openldap-clients</code> RPMs.
+ </div></li><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/openldap/slapd.conf</code> file to specify the LDAP domain and server. Refer to <a class="xref" href="#s2-ldap-files-slapd-conf" title="14.6.1. Editing /etc/openldap/slapd.conf">Section 14.6.1, “Editing <code class="filename">/etc/openldap/slapd.conf</code> ”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ Start <code class="command">slapd</code> with the command:
+ </div><pre class="screen">/sbin/service ldap start</pre><div class="para">
+ After configuring LDAP, use <code class="command">chkconfig</code>, <code class="command">/usr/sbin/ntsysv</code>, or the <span class="application"><strong>Services Configuration Tool</strong></span> to configure LDAP to start at boot time. For more information about configuring services, refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a>.
+ </div></li><li class="listitem"><div class="para">
+ Add entries to an LDAP directory with <code class="command">ldapadd</code>.
+ </div></li><li class="listitem"><div class="para">
+ Use <code class="command">ldapsearch</code> to determine if <code class="command">slapd</code> is accessing the information correctly.
+ </div></li><li class="listitem"><div class="para">
+ At this point, the LDAP directory should be functioning properly and can be configured with LDAP-enabled applications.
+ </div></li></ol></div><div class="section" title="14.6.1. Editing /etc/openldap/slapd.conf" id="s2-ldap-files-slapd-conf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-files-slapd-conf">14.6.1. Editing <code class="filename">/etc/openldap/slapd.conf</code> </h3></div></div></div><a id="id875754" class="indexterm"></a><div class="para">
+ To use the <code class="command">slapd</code> LDAP server, modify its configuration file, <code class="filename">/etc/openldap/slapd.conf</code>, to specify the correct domain and server.
+ </div><div class="para">
+ The <code class="command">suffix</code> line names the domain for which the LDAP server provides information and should be changed from:
+ </div><pre class="screen">suffix "dc=your-domain,dc=com"</pre><div class="para">
+ Edit it accordingly so that it reflects a fully qualified domain name. For example:
+ </div><pre class="screen">suffix "dc=example,dc=com"</pre><div class="para">
+ The <code class="command">rootdn</code> entry is the Distinguished Name (DN) for a user who is unrestricted by access controls or administrative limit parameters set for operations on the LDAP directory. The <code class="command">rootdn</code> user can be thought of as the root user for the LDAP directory. In the configuration file, change the <code class="command">rootdn</code> line from its default value as in the following example:
+ </div><pre class="screen">rootdn "cn=root,dc=example,dc=com"</pre><div class="para">
+ When populating an LDAP directory over a network, change the <code class="command">rootpw</code> line — replacing the default value with an encrypted password string. To create an encrypted password string, type the following command:
+ </div><pre class="screen">slappasswd</pre><div class="para">
+ When prompted, type and then re-type a password. The program prints the resulting encrypted password to the shell prompt.
+ </div><div class="para">
+ Next, copy the newly created encrypted password into the <code class="filename">/etc/openldap/slapd.conf</code> on one of the <code class="command">rootpw</code> lines and remove the hash mark (<code class="command">#</code>).
+ </div><div class="para">
+ When finished, the line should look similar to the following example:
+ </div><pre class="screen">rootpw {SSHA}vv2y+i6V6esazrIv70xSSnNAJE18bb2u</pre><div class="warning"><h2>Warning</h2><div class="para">
+ LDAP passwords, including the <code class="command">rootpw</code> directive specified in <code class="filename">/etc/openldap/slapd.conf</code>, are sent over the network <span class="emphasis"><em>unencrypted</em></span>, unless TLS encryption is enabled.
+ </div><div class="para">
+ To enable TLS encryption, review the comments in <code class="filename">/etc/openldap/slapd.conf</code> and refer to the man page for <code class="filename">slapd.conf</code>.
+ </div></div><div class="para">
+ For added security, the <code class="command">rootpw</code> directive should be commented out after populating the LDAP directory by preceding it with a hash mark (<code class="command">#</code>).
+ </div><div class="para">
+ When using the <code class="command">/usr/sbin/slapadd</code> command line tool locally to populate the LDAP directory, use of the <code class="command">rootpw</code> directive is not necessary.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Only the root user can use <code class="command">/usr/sbin/slapadd</code>. However, the directory server runs as the <code class="filename">ldap</code> user. Therefore, the directory server is unable to modify any files created by <code class="command">slapadd</code>. To correct this issue, after using <code class="command">slapadd</code>, type the following command:
+ </div><pre class="screen">chown -R ldap /var/lib/ldap</pre></div></div></div><div class="section" title="14.7. Configuring a System to Authenticate Using OpenLDAP" id="s1-ldap-pam"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-pam">14.7. Configuring a System to Authenticate Using OpenLDAP</h2></div></div></div><a id="id886107" class="indexterm"></a><div class="para">
+ This section provides a brief overview of how to configure OpenLDAP user authentication. Unless you are an OpenLDAP expert, more documentation than is provided here is necessary. Refer to the references provided in <a class="xref" href="#s1-ldap-additional-resources" title="14.9. Additional Resources">Section 14.9, “Additional Resources”</a> for more information.
+ </div><a id="id886132" class="indexterm"></a><a id="id886151" class="indexterm"></a><a id="id778509" class="indexterm"></a><a id="id778527" class="indexterm"></a><a id="id778549" class="indexterm"></a><a id="id869708" class="indexterm"></a><a id="id869730" class="indexterm"></a><a id="id869748" class="indexterm"></a><div class="formalpara"><h5 class="formalpara" id="id838749">Install the Necessary LDAP Packages.</h5>
+ First, make sure that the appropriate packages are installed on both the LDAP server and the LDAP client machines. The LDAP server needs the <code class="filename">openldap-servers</code> package.
+ </div><div class="para">
+ The <code class="filename">openldap</code>, <code class="filename">openldap-clients</code>, and <code class="filename">nss_ldap</code> packages need to be installed on all LDAP client machines.
+ </div><h3>Edit the Configuration Files</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On the server, edit the <code class="filename">/etc/openldap/slapd.conf</code> file on the LDAP server to make sure it matches the specifics of the organization. Refer to <a class="xref" href="#s2-ldap-files-slapd-conf" title="14.6.1. Editing /etc/openldap/slapd.conf">Section 14.6.1, “Editing <code class="filename">/etc/openldap/slapd.conf</code> ”</a> for instructions about editing <code class="filename">slapd.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ On the client machines, both <code class="filename">/etc/ldap.conf</code> and <code class="filename">/etc/openldap/ldap.conf</code> need to contain the proper server and search base information for the organization.
+ </div><div class="para">
+ To do this, run the graphical <span class="application"><strong>Authentication Configuration Tool</strong></span> (<code class="command">system-config-authentication</code>) and select <span class="guilabel"><strong>Enable LDAP Support</strong></span> under the <span class="guilabel"><strong>User Information</strong></span> tab.
+ </div><div class="para">
+ It is also possible to edit these files by hand.
+ </div></li><li class="listitem"><div class="para">
+ On the client machines, the <code class="filename">/etc/nsswitch.conf</code> must be edited to use LDAP.
+ </div><div class="para">
+ To do this, run the <span class="application"><strong>Authentication Configuration Tool</strong></span> (<code class="command">system-config-authentication</code>) and select <span class="guilabel"><strong>Enable LDAP Support</strong></span> under the <span class="guilabel"><strong>User Information</strong></span> tab.
+ </div><div class="para">
+ If editing <code class="filename">/etc/nsswitch.conf</code> by hand, add <code class="command">ldap</code> to the appropriate lines.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+passwd: files ldap
+shadow: files ldap
+group: files ldap
+</pre></li></ul></div><div class="section" title="14.7.1. PAM and LDAP" id="s2-ldap-pamd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-pamd">14.7.1. PAM and LDAP</h3></div></div></div><a id="id1704485" class="indexterm"></a><a id="id1704503" class="indexterm"></a><div class="para">
+ To have standard PAM-enabled applications use LDAP for authentication, run the <span class="application"><strong>Authentication Configuration Tool</strong></span> (<code class="command">system-config-authentication</code>) and select <span class="guilabel"><strong>Enable LDAP Support</strong></span> under the the <span class="guilabel"><strong>Authentication</strong></span> tab. For more information about configuring PAM, refer to the <em class="citetitle">Pluggable Authentication Modules (PAM)</em> chapter of the Fedora 13 <em class="citetitle">Security Guide</em> and the PAM man pages.
+ </div></div><div class="section" title="14.7.2. Migrating Old Authentication Information to LDAP Format" id="s2-ldap-migrate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-migrate">14.7.2. Migrating Old Authentication Information to LDAP Format</h3></div></div></div><div class="para">
+ The <code class="filename">/usr/share/openldap/migration/</code> directory contains a set of shell and Perl scripts for migrating authentication information into an LDAP format.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ Perl must be installed on the system to use these scripts.
+ </div></div><div class="para">
+ First, modify the <code class="filename">migrate_common.ph</code> file so that it reflects the correct domain. The default DNS domain should be changed from its default value to something like:
+ </div><pre class="screen">
+<code class="command">$DEFAULT_MAIL_DOMAIN = "<em class="replaceable"><code>example</code></em>";</code>
+</pre><div class="para">
+ The default base should also be changed to something like:
+ </div><pre class="screen">
+<code class="command">$DEFAULT_BASE = "dc=<em class="replaceable"><code>example</code></em>,dc=<em class="replaceable"><code>com</code></em>";</code>
+</pre><div class="para">
+ The job of migrating a user database into a format that is LDAP readable falls to a group of migration scripts installed in the same directory. Using <a class="xref" href="#tb-ldap-migratescripts" title="Table 14.1. LDAP Migration Scripts">Table 14.1, “LDAP Migration Scripts”</a>, decide which script to run to migrate the user database.
+ </div><div class="para">
+ Run the appropriate script based on the existing name service.
+ </div><div class="para">
+ The <code class="filename">README</code> and the <code class="filename">migration-tools.txt</code> files in the <code class="filename">/usr/share/openldap/migration/</code> directory provide more details on how to migrate the information.
+ </div><div class="table" title="Table 14.1. LDAP Migration Scripts" id="tb-ldap-migratescripts"><div class="table-contents"><table summary="LDAP Migration Scripts" border="1"><colgroup><col width="30%" /><col width="20%" /><col width="50%" /></colgroup><thead><tr><th>
+ Existing name service
+ </th><th>
+ Is LDAP running?
+ </th><th>
+ Script to Use
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc</code> flat files
+ </td><td>
+ yes
+ </td><td>
+ <code class="filename">migrate_all_online.sh</code>
+ </td></tr><tr><td>
+ <code class="filename">/etc</code> flat files
+ </td><td>
+ no
+ </td><td>
+ <code class="filename">migrate_all_offline.sh</code>
+ </td></tr><tr><td>
+ NetInfo
+ </td><td>
+ yes
+ </td><td>
+ <code class="filename">migrate_all_netinfo_online.sh</code>
+ </td></tr><tr><td>
+ NetInfo
+ </td><td>
+ no
+ </td><td>
+ <code class="filename">migrate_all_netinfo_offline.sh</code>
+ </td></tr><tr><td>
+ NIS (YP)
+ </td><td>
+ yes
+ </td><td>
+ <code class="filename">migrate_all_nis_online.sh</code>
+ </td></tr><tr><td>
+ NIS (YP)
+ </td><td>
+ no
+ </td><td>
+ <code class="filename">migrate_all_nis_offline.sh</code>
+ </td></tr></tbody></table></div><h6>Table 14.1. LDAP Migration Scripts</h6></div><br class="table-break" /></div></div><div class="section" title="14.8. Migrating Directories from Earlier Releases" id="s1-ldap-migrate"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-migrate">14.8. Migrating Directories from Earlier Releases</h2></div></div></div><a id="id799671" class="indexterm"></a><a id="id799690" class="indexterm"></a><div class="para">
+ With Fedora, OpenLDAP uses Sleepycat Software's Berkeley DB system as its on-disk storage format for directories. Earlier versions of OpenLDAP used <em class="firstterm">GNU Database Manager</em> (<em class="firstterm">gdbm</em>). For this reason, before upgrading an LDAP implementation to Fedora 5.2, original LDAP data should first be exported before the upgrade, and then reimported afterwards. This can be achieved by performing the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Before upgrading the operating system, run the command <code class="command">/usr/sbin/slapcat -l <em class="replaceable"><code>ldif-output</code></em> </code>. This outputs an LDIF file called <code class="filename"><em class="replaceable"><code>ldif-output</code></em> </code> containing the entries from the LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ Upgrade the operating system, being careful not to reformat the partition containing the LDIF file.
+ </div></li><li class="listitem"><div class="para">
+ Re-import the LDAP directory to the upgraded Berkeley DB format by executing the command <code class="command">/usr/sbin/slapadd -l <em class="replaceable"><code>ldif-output</code></em> </code>.
+ </div></li></ol></div></div><div class="section" title="14.9. Additional Resources" id="s1-ldap-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-additional-resources">14.9. Additional Resources</h2></div></div></div><a id="id834770" class="indexterm"></a><div class="para">
+ The following resources offer additional information on LDAP. It is highly recommended that you review these, especially the OpenLDAP website and the LDAP HOWTO, before configuring LDAP on your system(s).
+ </div><div class="section" title="14.9.1. Installed Documentation" id="s2-ldap-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-installed-docs">14.9.1. Installed Documentation</h3></div></div></div><a id="id876488" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/docs/openldap-<em class="replaceable"><code><versionnumber></code></em>/</code> directory — Contains a general <code class="filename">README</code> document and miscellaneous information.
+ </div></li><li class="listitem"><div class="para">
+ LDAP related man pages — There are a number of man pages for the various applications and configuration files involved with LDAP. The following is a list of some of the more important man pages.
+ </div><div class="variablelist"><dl><dt><span class="term">Client Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man ldapadd</code> — Describes how to add entries to an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapdelete</code> — Describes how to delete entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapmodify</code> — Describes how to modify entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapsearch</code> — Describes how to search for entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldappasswd</code> — Describes how to set or change the password of an LDAP user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapcompare</code> — Describes how to use the <code class="command">ldapcompare</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapwhoami</code> — Describes how to use the <code class="command">ldapwhoami</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapmodrdn</code> — Describes how to modify the RDNs of entries.
+ </div></li></ul></div></dd><dt><span class="term">Server Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man slapd</code> — Describes command line options for the LDAP server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slurpd</code> — Describes command line options for the LDAP replication server.
+ </div></li></ul></div></dd><dt><span class="term">Administrative Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man slapadd</code> — Describes command line options used to add entries to a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slapcat</code> — Describes command line options used to generate an LDIF file from a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slapindex</code> — Describes command line options used to regenerate an index based upon the contents of a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slappasswd</code> — Describes command line options used to generate user passwords for LDAP directories.
+ </div></li></ul></div></dd><dt><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man ldap.conf</code> — Describes the format and options available within the configuration file for LDAP clients.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slapd.conf</code> — Describes the format and options available within the configuration file referenced by both the LDAP server applications (<code class="command">slapd</code> and <code class="command">slurpd</code>) and the LDAP administrative tools (<code class="command">slapadd</code>, <code class="command">slapcat</code>, and <code class="command">slapindex</code>).
+ </div></li></ul></div></dd></dl></div></li></ul></div></div><div class="section" title="14.9.2. Useful Websites" id="s2-ldap-additional-resources-web"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-additional-resources-web">14.9.2. Useful Websites</h3></div></div></div><a id="id713386" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.openldap.org">http://www.openldap.org/</a> — Home of the OpenLDAP Project. This website contains a wealth of information about configuring OpenLDAP as well as a future roadmap and version changes.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.padl.com">http://www.padl.com/</a> — Developers of <code class="filename">nss_ldap</code> and <code class="filename">pam_ldap</code>, among other useful LDAP tools.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.kingsmountain.com/ldapRoadmap.shtml">http://www.kingsmountain.com/ldapRoadmap.shtml</a> — Jeff Hodges' LDAP Road Map contains links to several useful FAQs and emerging news concerning the LDAP protocol.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.ldapman.org/articles/">http://www.ldapman.org/articles/</a> — Articles that offer a good introduction to LDAP, including methods to design a directory tree and customizing directory structures.
+ </div></li></ul></div></div><div class="section" title="14.9.3. Related Books" id="s2-ldap-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-related-books">14.9.3. Related Books</h3></div></div></div><a id="id735250" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">OpenLDAP by Example</em> by John Terpstra and Benjamin Coles; Prentice Hall.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Implementing LDAP</em> by Mark Wilcox; Wrox Press, Inc.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Understanding and Deploying LDAP Directory Services</em> by Tim Howes et al.; Macmillan Technical Publishing.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 15. Authentication Configuration" id="ch-Authentication_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Authentication Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool">15.1. The Authentication Configuration Tool</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">15.1.1. Identity & Authentication</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">15.1.2. Advanced Options</a></span></dt><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool-Command_Line_Version">15.1.3. Command Line Version</a></span></dt></dl></dd><dt><span class="section"><a href="#chap-SSSD_User_Guide-Introductio
n">15.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introduction-What_is_SSSD">15.2.1. What is SSSD?</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Introduction-SSSD_Features">15.2.2. SSSD Features</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Setting_Up_SSSD">15.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Services">15.2.4. Configuring Services</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Configuring_Domains">15.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">15.2.6. Setting up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Troubleshooting">15.2.7. Troubleshooting</a></span></dt><dt><span class="section"><a h
ref="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">15.2.8. SSSD Configuration File Format</a></span></dt></dl></dd></dl></div><div class="section" title="15.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">15.1. The Authentication Configuration Tool</h2></div></div></div><a id="id610679" class="indexterm"></a><a id="id685618" 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"><h2>Note</h2><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 section <em class="citetitle">Firewalls</em> of the <em class="citetitle">Security Guide</em>
+ </div></div><a id="id837056" class="indexterm"></a><a id="id837041" 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"><h2>Important</h2><div class="para">
+ After exiting the authentication program, any changes you made take effect immediately.
+ </div></div><div class="section" title="15.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">15.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 15.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 15.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>LDAP</h4><a id="id685560" 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"><h2>Important</h2><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 class="para">
+ For more information about CA Certificates, refer to <a class="xref" href="#s2-secureserver-overview-certs" title="11.8.2. An Overview of Certificates and Security">Section 11.8.2, “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">
+ For more information about LDAP, refer to <a class="xref" href="#ch-Lightweight_Directory_Access_Protocol_LDAP" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)">Chapter 14, <i>Lightweight Directory Access Protocol (LDAP)</i></a>
+ </div><div class="para">
+ LDAP provides the following methods of authentication:
+ </div><div class="itemizedlist"><ul><li class="listitem"><a id="id1478195" 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"> "Kerberos"</em> of the <em class="citetitle">Security Guide</em>.
+ </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"><h2>Note</h2><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="15.2. The System Security Services Daemon (SSSD)">Section 15.2, “The System Security Services Daemon (SSSD)”</a>
+ </div></div><h4>NIS</h4><a id="id1204806" 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 section <em class="citetitle">"Securing NIS"</em> of the <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="id936318" 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>Winbind</h4><a id="id959459" 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. For more information about domain controllers, please refer to <a class="xref" href="#s2-samba-domain-controller" title="9.6.3. Domain Controller">Section 9.6.3, “Domain Controller”</a>.
+ </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><div class="para">
+ For more information about the <code class="command">winbindd</code> service, refer to <a class="xref" href="#s1-samba-daemons" title="9.2. Samba Daemons and Related Services">Section 9.2, “Samba Daemons and Related Services”</a>.
+ </div><a id="id747433" 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="15.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">15.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 15.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 15.2. <span class="guilabel">Advanced Options</span></h6></div><br class="figure-break" /><h4>Local Authentication Options</h4><div class="itemizedlist"><ul><li class="listitem"><a id="id969695" 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>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>Smart Card Authentication Options</h4><a id="id749004" 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 <em class="citetitle">Managing Smart Cards with the Enterprise Security Client</em> guide. <div class="note"><h2>Note</h2><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 class="section" title="15.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">15.1.3. Command Line Version</h3></div></div></div><a id="id600257" 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 15.1. Command Line Options">Table 15.1, “Command Line Options”</a>.
+ </div><div class="note"><h2>Tip</h2><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 class="table" title="Table 15.1. Command Line Options" id="tb-authconfig-cmd-line"><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><h6>Table 15.1. Command Line Options</h6></div><br class="table-break" /></div></div><div xml:lang="en-US" class="section" title="15.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">15.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="15.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">15.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.
+ </div></div><div class="section" title="15.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">15.2.2. SSSD Features</h3></div></div></div><div class="section" title="15.2.2.1. Performing Offline Authentication" id="sect-SSSD_User_Guide-SSSD_Features-Performing_Offline_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Performing_Offline_Authentication">15.2.2.1. Performing 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="15.2.2.2. Reducing Server Load" id="sect-SSSD_User_Guide-SSSD_Features-Reducing_Server_Load"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Reducing_Server_Load">15.2.2.2. Reducing Server Load</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="15.2.2.3. Specifying Multiple Domains" id="sect-SSSD_User_Guide-SSSD_Features-Specifying_Multiple_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Specifying_Multiple_Domains">15.2.2.3. Specifying Multiple Domains</h4></div></div></div><a id="id1016762" 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="id1016713">Considerations Associated with Deleting Cache Files</h5><a id="id1016708" 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 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><div class="section" title="15.2.2.4. 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">15.2.2.4. 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="15.2.2.5. Integrating with Other Products" id="sect-SSSD_User_Guide-SSSD_Features-Integrating_with_Other_Products"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Integrating_with_Other_Products">15.2.2.5. Integrating with Other Products</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 added functionality, including host-based access control, and password migration from an LDAP-only environment into the LDAP/Kerberos 5 environment employed by IPA.
+ </div></div></div><div class="section" title="15.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">15.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="15.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">15.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="15.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">15.2.3.1.1. Upgrading from a Previous Version</h5></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="15.2.8. SSSD Configuration File Format">Section 15.2.8, “SSSD Configuration File Format”</a>
+ </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="15.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">15.2.3.1.2. Starting and Stopping SSSD</h5></div></div></div><div class="note"><h2>Note</h2><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="15.2.5. Configuring Domains">Section 15.2.5, “Configuring Domains”</a> for information on how to configure an SSSD domain.
+ </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. You can use the <code class="command">chkconfig</code> command to change this behavior. For example, run the following command to configure SSSD to start when the machine boots:
+ </div><div class="para">
+ <code class="command"># chkconfig sssd on</code>
+ </div></div></div><div class="section" title="15.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">15.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"><h2>Note</h2><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 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="15.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">15.2.3.2.1. Configuring NSS</h5></div></div></div><div class="para">
+ SSSD provides a new NSS module, <code class="systemitem">nss_sss</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="15.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">15.2.3.2.2. Configuring PAM</h5></div></div></div><div class="warning"><h2>Warning</h2><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 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="formalpara" id="form-SSSD_User_Guide-Configuring_PAM-Using_include_Statements_in_PAM_Configurations"><h5 class="formalpara">Using include Statements in PAM Configurations</h5>
+ 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"><h2>Note</h2><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 class="section" title="15.2.3.2.3. Configuring Access Control"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id623093">15.2.3.2.3. Configuring Access Control</h5></div></div></div><a id="id870451" class="indexterm"></a><div class="para">
+ SSSD provides a rudimentary access control mechanism based on the implementation of access or deny lists of usernames. This mechanism is known as the <em class="firstterm">Simple Access Provider</em>, and is configured 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. 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="id972893">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="formalpara"><h5 class="formalpara" id="id661646">Access Control Rules</h5><a id="id734217" 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"><h2>Important</h2><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 when loading the back end and will fail to start.
+ </div></div>
+
+ </div></div><div class="section" title="15.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">15.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="15.2.3.2.4.1. Using SRV Records with Failover">Section 15.2.3.2.4.1, “Using SRV Records with Failover”</a> for more information on service discovery.
+ </div><div class="important"><h2>Important</h2><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 class="section" title="15.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">15.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="15.2.3.2.4.2. How the Failover Mechanism Works"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="id605132">15.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">
+ 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="15.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">15.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">nss_sss</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">pam_sss</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="15.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">15.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="15.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">15.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"><h2>Note</h2><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></li></ul></div></div><div class="section" title="15.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">15.2.4.1.2. NSS Configuration Options</h5></div></div></div><div class="para">
+ Use the following options to configure the Name Service Switch (NSS) 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">nss_sss</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">nss_sss</span> should return cached entries before initiating an out-of-band cache refresh (0 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 0-99 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">nss_sss</span> should cache negative cache hits (that is, queries for invalid database entries, like 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 TRUE, 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 FALSE, 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="15.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">15.2.4.1.3. PAM Configuration Options</h5></div></div></div><div class="para">
+ Use these options to configure the <code class="systemitem module">Pluggable Authentication Module</code> (<acronym class="acronym">PAM</acronym>) 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 we should allow cached log ins (in days). If not specified, defaults to <code class="literal">0</code> (no limit).
+ </div></li></ul></div></div></div></div><div class="section" title="15.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">15.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="15.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="15.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="15.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">15.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="15.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">15.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="important"><h2>Important</h2><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></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"><h2>Note</h2><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></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"><h2>Note</h2><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="15.2.5.4. Configuring a Proxy Domain">Section 15.2.5.4, “Configuring a Proxy Domain”</a> for information on this attribute.
+ </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"><h2>Note</h2><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></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="15.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">15.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="15.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">15.2.5.2. Configuring an LDAP Domain</h4></div></div></div><a id="id1846539" 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. 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_user_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="id1939730" 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 by default 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="id818224" 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"><h2>Note</h2><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></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 class="formalpara"><h5 class="formalpara" id="id923712">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 a native <acronym class="acronym">LDAP</acronym> domain.
+ </div></div><div class="section" title="15.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">15.2.5.3. Configuring a Microsoft Active Directory Domain</h4></div></div></div><a id="id1200158" 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 on the Active Directory machine. This requirement does not apply to Active Directory 2008.
+ </div><div class="section" title="15.2.5.3.1. Configuring Active Directory 2003 as an LDAP Back End"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id653654">15.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 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_user_search_base = cn=users,dc=example,dc=com
+ldap_group_search_base = cn=users,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></div><div class="section" title="15.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">15.2.5.4. Configuring a Proxy Domain</h4></div></div></div><a id="id1126426" 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></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="15.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">15.2.6. Setting up Kerberos Authentication</h3></div></div></div><a id="id667930" 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="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_user_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="15.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">15.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="15.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">15.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="15.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">15.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"><h2>Important</h2><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></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="15.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">15.2.7.3. Problems with SSSD Service Configuration</h4></div></div></div><div class="section" title="15.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">15.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="15.2.3.2.1. Configuring NSS">Section 15.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="15.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">15.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="15.2.3.2.2. Configuring PAM">Section 15.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><div class="section" title="15.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">15.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="15.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">15.2.7.5. Additional Resources</h4></div></div></div><div class="section" title="15.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">15.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="15.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">15.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="15.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">15.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_user_search_base = ou=users,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><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,de-DE,es-ES,fr-FR,it-IT,ja-JP" class="part" title="Part III. System Configuration" id="pt-sysconfig" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,de-DE,es-ES,fr-FR,it-IT,ja-JP"><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="id1012022"><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="#ch-Console_Access">16. Console Access</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-access-console-ctrlaltdel">16.1. Disabling Shutdown Via <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span></a></span></dt><dt><span class="section"><a href="#s1-access-console-program">16.2. Disabling Console Program Access</a></span></dt><dt><span class="section"><a href="#s1-access-console-define">16.3. Defining the Console</a></span></dt><dt><span class="section"><a href="#s1-access-console-files">16.4. Making Files Accessible From the Console</a></span></dt><dt><span class="section"><a href="#s1-access-console-enable">16.5. Enabling Console Access for Other Applications</a></span></dt><dt><span class="section"><a href="#s1-access-floppy">16.6. The <code class="filename">floppy</code
> Group</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-proc">17. The <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-proc-virtual">17.1. A Virtual File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-viewing">17.1.1. Viewing Virtual Files</a></span></dt><dt><span class="section"><a href="#s2-proc-change">17.1.2. Changing Virtual Files</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-topfiles">17.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-buddyinfo">17.2.1. <code class="filename">/proc/buddyinfo</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-cmdline">17.2.2. <code class="filename">/proc/cmdline</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-cpuinfo">17.2.3. <code class="filename">/proc/cpuinfo</code> </a></span><
/dt><dt><span class="section"><a href="#s2-proc-crypto">17.2.4. <code class="filename">/proc/crypto</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-devices">17.2.5. <code class="filename">/proc/devices</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dma">17.2.6. <code class="filename">/proc/dma</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-execdomains">17.2.7. <code class="filename">/proc/execdomains</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-fb">17.2.8. <code class="filename">/proc/fb</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-filesystems">17.2.9. <code class="filename">/proc/filesystems</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-interrupts">17.2.10. <code class="filename">/proc/interrupts</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-iomem">17.2.11. <code class="filename">/proc/iomem</code> </a></span></dt><dt><span
class="section"><a href="#s2-proc-ioports">17.2.12. <code class="filename">/proc/ioports</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-kcore">17.2.13. <code class="filename">/proc/kcore</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-kmsg">17.2.14. <code class="filename">/proc/kmsg</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-loadavg">17.2.15. <code class="filename">/proc/loadavg</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-locks">17.2.16. <code class="filename">/proc/locks</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-mdstat">17.2.17. <code class="filename">/proc/mdstat</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-meminfo">17.2.18. <code class="filename">/proc/meminfo</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-misc">17.2.19. <code class="filename">/proc/misc</code> </a></span></dt><dt><span class="section"><a href="#
s2-proc-modules">17.2.20. <code class="filename">/proc/modules</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-mounts">17.2.21. <code class="filename">/proc/mounts</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-mtrr">17.2.22. <code class="filename">/proc/mtrr</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-partitions">17.2.23. <code class="filename">/proc/partitions</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-pci">17.2.24. <code class="filename">/proc/pci</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-slabinfo">17.2.25. <code class="filename">/proc/slabinfo</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-stat">17.2.26. <code class="filename">/proc/stat</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-swaps">17.2.27. <code class="filename">/proc/swaps</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-sysrq-trigger">
17.2.28. <code class="filename">/proc/sysrq-trigger</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-uptime">17.2.29. <code class="filename">/proc/uptime</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-version">17.2.30. <code class="filename">/proc/version</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-directories">17.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-processdirs">17.3.1. Process Directories</a></span></dt><dt><span class="section"><a href="#s2-proc-dir-bus">17.3.2. <code class="filename">/proc/bus/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-driver">17.3.3. <code class="filename">/proc/driver/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-fs">17.3.4. <code class="filename">/proc/fs</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-irq">17.
3.5. <code class="filename">/proc/irq/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-net">17.3.6. <code class="filename">/proc/net/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-scsi">17.3.7. <code class="filename">/proc/scsi/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-sys">17.3.8. <code class="filename">/proc/sys/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-sysvipc">17.3.9. <code class="filename">/proc/sysvipc/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-tty">17.3.10. <code class="filename">/proc/tty/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-pid">17.3.11. <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-sysctl">17.4. Using the <code class="command">sysctl</code> Command</a></span></dt><dt><span class="section"><a
href="#s1-proc-additional-resources">17.5. References</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><dd><dl><dt><span class="section"><a href="#s2-sysconfig-arpwatch">18.1.1. <code class="filename">/etc/sysconfig/arpwatch</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-authconfig">18.1.2. <code class="filename">/etc/sysconfig/authconfig</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-autofs">18.1.3. <code class="filename">/etc/sysconfig/autofs</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-clock">18.1.4. <code class="filename">/etc/sysconfig/clock</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-desktop">18.1.5. <code class="filename">/etc/
sysconfig/desktop</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-dhcpd">18.1.6. <code class="filename">/etc/sysconfig/dhcpd</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-firewall">18.1.7. <code class="filename">/etc/sysconfig/firstboot</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-i18n">18.1.8. <code class="filename">/etc/sysconfig/i18n</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-init">18.1.9. <code class="filename">/etc/sysconfig/init</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-ip6tables">18.1.10. <code class="filename">/etc/sysconfig/ip6tables-config</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-kybd">18.1.11. <code class="filename">/etc/sysconfig/keyboard</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-named">18.1.12. <code class="filename">/etc/sysconfig/named</code> </a></span></dt><
dt><span class="section"><a href="#s2-sysconfig-network">18.1.13. <code class="filename">/etc/sysconfig/network</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-ntpd">18.1.14. <code class="filename">/etc/sysconfig/ntpd</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-radvd">18.1.15. <code class="filename">/etc/sysconfig/radvd</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-samba">18.1.16. <code class="filename">/etc/sysconfig/samba</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-selinux">18.1.17. <code class="filename">/etc/sysconfig/selinux</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-sendmail">18.1.18. <code class="filename">/etc/sysconfig/sendmail</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-spamd">18.1.19. <code class="filename">/etc/sysconfig/spamassassin</code> </a></span></dt><dt><span class="section"><a href="#s2-s
ysconfig-squid">18.1.20. <code class="filename">/etc/sysconfig/squid</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-rcu">18.1.21. <code class="filename">/etc/sysconfig/system-config-users</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-vncservers">18.1.22. <code class="filename">/etc/sysconfig/vncservers</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-xinetd">18.1.23. <code class="filename">/etc/sysconfig/xinetd</code> </a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#s2-sysconfig-installed-documentation">18.3.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap
-Date_and_Time_Configuration">19. 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">19.1. Date/Time Properties Tool</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Date_and_Time">19.1.1. Date and Time Properties</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Network_Time_Protocol">19.1.2. Network Time Protocol Properties</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Time_Zone">19.1.3. Time Zone Properties</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration">19.2. Command Line Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">19.2.1. Date and Time Setup</a></span></dt><dt><span class="section"><a
href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">19.2.2. Network Time Protocol Setup</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Keyboard_Configuration">20. Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-keyboard-layout">20.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="#s1-keyboard-indicator">20.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="#s1-keyboard-break">20.3. Setting Up a Typing Break</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-The_X_Window_System">21. The X Window System</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-x-server">21.1. The X11R7.1 Release</a></span></dt><dt><span class="section"><a href="#s1-x-clients">21.2. Desktop Environments and Window Managers</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-clients-desktop">21.2
.1. Desktop Environments</a></span></dt><dt><span class="section"><a href="#s2-x-clients-winmanagers">21.2.2. Window Managers</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-server-configuration">21.3. X Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-server-config-xorg.conf">21.3.1. <code class="filename">xorg.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-fonts">21.4. Fonts</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-fonts-fontconfig">21.4.1. Fontconfig</a></span></dt><dt><span class="section"><a href="#s2-x-fonts-core">21.4.2. Core X Font System</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-runlevels">21.5. Runlevels and X</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-runlevels-3">21.5.1. Runlevel 3</a></span></dt><dt><span class="section"><a href="#s2-x-runlevels-5">21.5.2. Runlevel 5</a></span></dt></dl></dd><dt><span cl
ass="section"><a href="#s1-x-additional-resources">21.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-installed-documentation">21.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-x-useful-websites">21.6.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ers_and_Groups">22. Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-users-configui">22.1. User and Group Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-users-user-new">22.1.1. Adding a New User</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-new">22.1.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-properties">22.1.3. Modifying Group Properties</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">22.2. User and Group Management Tools<
/a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-cmd-line">22.2.1. Command Line Configuration</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-process">22.2.2. Explaining the Process</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-standard-users">22.3. Standard Users</a></span></dt><dt><span class="section"><a href="#s1-users-groups-standard-groups">22.4. Standard Groups</a></span></dt><dt><span class="section"><a href="#s1-users-groups-private-groups">22.5. User Private Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-rationale">22.5.1. Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-shadow-utilities">22.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="#s1-users-groups-additional-resources">22.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-documentatio
n">22.7.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Printer_Configuration">23. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-printing-local-printer">23.1. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">23.2. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">23.3. Adding a Samba (SMB) Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-jetdirect-printer">23.4. Adding a JetDirect Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">23.5. Selecting the Printer Model and Finishing</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-printing-confirm">23.5.1. Confirming Printer Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-printing-test-page">23.6. Printing a Test Page</a></span></dt><dt><span clas
s="section"><a href="#s1-printing-edit">23.7. Modifying Existing Printers</a></span></dt><dd><dl><dt><span class="section"><a href="#id1520769">23.7.1. The <span class="guilabel"><strong>Settings</strong></span> Tab</a></span></dt><dt><span class="section"><a href="#id995216">23.7.2. The <span class="guilabel"><strong>Policies</strong></span> Tab</a></span></dt><dt><span class="section"><a href="#id881428">23.7.3. The <span class="guilabel"><strong>Access Control</strong></span> Tab</a></span></dt><dt><span class="section"><a href="#id1712276">23.7.4. The <span class="guilabel"><strong>Printer</strong></span> and <span class="guilabel"><strong>Job Options</strong></span>Tab</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-printing-managing">23.8. Managing Print Jobs</a></span></dt><dt><span class="section"><a href="#s1-printing-additional-resources">23.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-printing-installed-docs
">23.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-printing-useful-websites">23.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Automated_Tasks">24. Automated Tasks</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-autotasks-cron">24.1. Cron</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-cron-configuring">24.1.1. Configuring Cron Tasks</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">24.1.2. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-service">24.1.3. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-at-batch">24.2. At and Batch</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-at-configuring">24.2.1. Configuring At Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuri
ng">24.2.2. Configuring Batch Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">24.2.3. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">24.2.4. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">24.2.5. Controlling Access to At and Batch</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-service">24.2.6. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">24.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-installed-docs">24.3.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Log_Files">25. Log Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-logfiles-locating">25.1. Locating Log Files</a></span>
</dt><dt><span class="section"><a href="#s1-logfiles-viewing">25.2. Viewing Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-adding">25.3. Adding a Log File</a></span></dt><dt><span class="section"><a href="#s1-logfiles-examining">25.4. Monitoring Log Files</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" title="Chapter 16. Console Access" id="ch-Console_Access" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 16. Console Access</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-access-console-ctrlaltdel">16.1. Disabling Shutdown Via <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span></a></span></dt><dt><span class="section"><a href="#s1-access-console-program">16.2. Disabling Console Program Access</a></span></dt><dt><span class="section"><a href="#s1-access-console-de
fine">16.3. Defining the Console</a></span></dt><dt><span class="section"><a href="#s1-access-console-files">16.4. Making Files Accessible From the Console</a></span></dt><dt><span class="section"><a href="#s1-access-console-enable">16.5. Enabling Console Access for Other Applications</a></span></dt><dt><span class="section"><a href="#s1-access-floppy">16.6. The <code class="filename">floppy</code> Group</a></span></dt></dl></div><div class="para">
+ When non-root users log into a computer locally, they are given two types of special permissions:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="emphasis"><em>They can run certain commands that they would otherwise be unable to run.</em></span> By default, every user who logs in at the console is allowed to run selected commands that accomplish tasks normally restricted to the superuser only. These include <code class="command">halt</code>, <code class="command">poweroff</code>, and <code class="command">reboot</code>. In graphical user interface, these actions are accessible from the <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Shut Down...</strong></span> menu option.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>They can access certain files that they would othherwise be unable to access.</em></span> This usually means special device files located in <code class="filename">/dev</code> that are used to access CD-ROM drives, USB media, etc.
+ </div></li></ol></div><div class="para">
+ Note that in order to perform actions described in this chapter, you have to be logged in as a superuser:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="section" title="16.1. Disabling Shutdown Via Ctrl+Alt+Del" id="s1-access-console-ctrlaltdel"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-console-ctrlaltdel">16.1. Disabling Shutdown Via <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span></h2></div></div></div><div class="para">
+ By default, pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Delete</strong></span> at the console causes system to reboot immediately. To disable this behavior, open the <code class="filename">/etc/init/control-alt-delete.conf</code> configuration file in a text editor such as <code class="command">vi</code> or <code class="command">nano</code>:
+ </div><pre class="screen">~]# <code class="command">nano /etc/init/control-alt-delete.conf</code></pre><div class="para">
+ Then find a line containing the following text and add a hash mark at its very beginning like this:
+ </div><pre class="screen">#start on control-alt-delete</pre><div class="para">
+ Finally, save your changes, and exit the editor. The changes will take effect next time you reboot the computer.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Being part of the <span class="package">initscripts</span> package, <code class="filename">/etc/init/control-alt-delete.conf</code> will most likely be restored to its initial state the next time this package is upgraded. If that happens, repeat the process described in this section, or make a backup.
+ </div></div><div class="para">
+ Alternatively, you may want to allow certain non-root users the right to shutdown or reboot the system from the console using <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span> . You can restrict this privilege to certain users, by taking the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Add the <code class="command">-a</code> option to the <code class="filename">/etc/inittab</code> line shown above, so that it reads:
+ </div><pre class="screen">ca::ctrlaltdel:/sbin/shutdown -a -t3 -r now</pre><div class="para">
+ The <code class="command">-a</code> flag tells <code class="command">shutdown</code> to look for the <code class="filename">/etc/shutdown.allow</code> file.
+ </div></li><li class="listitem"><div class="para">
+ Create a file named <code class="filename">shutdown.allow</code> in <code class="filename">/etc</code>. The <code class="filename">shutdown.allow</code> file should list the usernames of any users who are allowed to shutdown the system using <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span> . The format of the <code class="filename">shutdown.allow</code> file is a list of usernames, one per line, like the following:
+ </div><pre class="screen">stephen jack sophie</pre></li></ol></div><div class="para">
+ According to this example <code class="filename">shutdown.allow</code> file, the users <code class="command">stephen</code>, <code class="command">jack</code>, and <code class="command">sophie</code> are allowed to shutdown the system from the console using <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span> . When that key combination is used, the <code class="filename">shutdown -a</code> command in <code class="filename">/etc/inittab</code> checks to see if any of the users in <code class="filename">/etc/shutdown.allow</code> (or root) are logged in on a virtual console. If one of them is, the shutdown of the system continues; if not, an error message is written to the system console instead.
+ </div><div class="para">
+ For more information on <code class="filename">shutdown.allow</code>, refer to the <code class="command">shutdown</code> man page.
+ </div></div><div class="section" title="16.2. Disabling Console Program Access" id="s1-access-console-program"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-console-program">16.2. Disabling Console Program Access</h2></div></div></div><div class="para">
+ To disable access by users to console programs, run the following command as root:
+ </div><pre class="screen">
+<code class="command">rm -f /etc/security/console.apps/*</code>
+</pre><div class="para">
+ In environments where the console is otherwise secured (BIOS and boot loader passwords are set, <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Delete</strong></span> is disabled, the power and reset switches are disabled, and so forth), you may not want to allow any user at the console to run <code class="command">poweroff</code>, <code class="command">halt</code>, and <code class="command">reboot</code>, which are accessible from the console by default.
+ </div><div class="para">
+ To disable these abilities, run the following commands as root:
+ </div><pre class="screen"><code class="command">rm -f /etc/security/console.apps/poweroff</code>
+<code class="command">rm -f /etc/security/console.apps/halt</code>
+<code class="command">rm -f /etc/security/console.apps/reboot</code></pre></div><div class="section" title="16.3. Defining the Console" id="s1-access-console-define"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-console-define">16.3. Defining the Console</h2></div></div></div><div class="para">
+ The <code class="filename">pam_console.so</code> module uses the <code class="filename">/etc/security/console.perms</code> file to determine the permissions for users at the system console. The syntax of the file is very flexible; you can edit the file so that these instructions no longer apply. However, the default file has a line that looks like this:
+ </div><pre class="screen">
+<code class="command"><console>=tty[0-9][0-9]* vc/[0-9][0-9]* :[0-9]\.[0-9] :[0-9]</code>
+</pre><div class="para">
+ When users log in, they are attached to some sort of named terminal, which can be either an X server with a name like <code class="command">:0</code> or <code class="command">mymachine.example.com:1.0</code>, or a device like <code class="filename">/dev/ttyS0</code> or <code class="filename">/dev/pts/2</code>. The default is to define that local virtual consoles and local X servers are considered local, but if you want to consider the serial terminal next to you on port <code class="filename">/dev/ttyS1</code> to also be local, you can change that line to read:
+ </div><pre class="screen">
+<code class="command"><console>=tty[0-9][0-9]* vc/[0-9][0-9]* :[0-9]\.[0-9] :[0-9] /dev/ttyS1</code>
+</pre></div><div class="section" title="16.4. Making Files Accessible From the Console" id="s1-access-console-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-console-files">16.4. Making Files Accessible From the Console</h2></div></div></div><div class="para">
+ The default settings for individual device classes and permission definitions are defined in <code class="filename">/etc/security/console.perms.d/50-default.perms</code>. To edit file and device permissions, it is advisable to create a new default file in <code class="filename">/etc/security/console.perms.d/</code> containing your preferred settings for a specified set of files or devices. The name of the new default file must begin with a number higher than 50 (for example, <code class="filename">51-default.perms</code>) in order to override <code class="filename">50-default.perms</code>.
+ </div><div class="para">
+ To do this, create a new file named <code class="filename">51-default.perms</code> in <code class="filename">/etc/security/console.perms.d/</code>:
+ </div><pre class="screen">
+<code class="command">touch /etc/security/console.perms.d/51-default.perms</code>
+</pre><div class="para">
+ Open the original default <code class="filename">perms</code> file, <code class="filename">50-default.perms</code>. The first section defines <em class="firstterm">device classes</em>, with lines similar to the following:
+ </div><pre class="screen"><floppy>=/dev/fd[0-1]* \ /dev/floppy/* /mnt/floppy* <sound>=/dev/dsp* /dev/audio* /dev/midi* \ /dev/mixer* /dev/sequencer \ /dev/sound/* /dev/beep \ /dev/snd/* <cdrom>=/dev/cdrom* /dev/cdroms/* /dev/cdwriter* /mnt/cdrom*</pre><div class="para">
+ Items enclosed in brackets name the device; in the above example, <code class="computeroutput"><cdrom></code> refers to the CD-ROM drive. To add a new device, do not define it in the default <code class="filename">50-default.perms</code> file; instead, define it in <code class="filename">51-default.perms</code>. For example, to define a scanner, add the following line to <code class="filename">51-default.perms</code>:
+ </div><pre class="screen"><scanner>=/dev/scanner /dev/usb/scanner*</pre><div class="para">
+ Of course, you must use the appropriate name for the device. Ensure that <code class="filename">/dev/scanner</code> is really your scanner and not some other device, such as your hard drive.
+ </div><div class="para">
+ Once you have properly defined a device or file, the second step is to specify its <em class="firstterm">permission definitions</em>. The second section of <code class="filename">/etc/security/console.perms.d/50-default.perms</code> defines this, with lines similar to the following:
+ </div><pre class="screen"><console> 0660 <floppy> 0660 root.floppy <console> 0600 <sound> 0640 root <console> 0600 <cdrom> 0600 root.disk</pre><div class="para">
+ To define permissions for a scanner, add a line similar to the following in <code class="filename">51-default.perms</code>:
+ </div><pre class="screen">
+<code class="command"><console> 0600 <scanner> 0600 root</code>
+</pre><div class="para">
+ Then, when you log in at the console, you are given ownership of the <code class="filename">/dev/scanner</code> device with the permissions of 0600 (readable and writable by you only). When you log out, the device is owned by root, and still has the permissions 0600 (now readable and writable by root only).
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ You must <span class="emphasis"><em>never</em></span> edit the default <code class="filename">50-default.perms</code> file. To edit permissions for a device already defined in <code class="filename">50-default.perms</code>, add the desired permission definition for that device in <code class="filename">51-default.perms</code>. This will override whatever permissions are defined in <code class="filename">50-default.perms</code>.
+ </div></div></div><div class="section" title="16.5. Enabling Console Access for Other Applications" id="s1-access-console-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-console-enable">16.5. Enabling Console Access for Other Applications</h2></div></div></div><div class="para">
+ To make other applications accessible to console users, a bit more work is required.
+ </div><div class="para">
+ First of all, console access <span class="emphasis"><em>only</em></span> works for applications which reside in <code class="filename">/sbin/</code> or <code class="filename">/usr/sbin/</code>, so the application that you wish to run must be there. After verifying that, perform the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Create a link from the name of your application, such as our sample <code class="filename">foo</code> program, to the <code class="command">/usr/bin/consolehelper</code> application:
+ </div><pre class="screen">
+<code class="command">cd /usr/bin ln -s consolehelper foo</code>
+</pre></li><li class="listitem"><div class="para">
+ Create the file <code class="filename">/etc/security/console.apps/foo</code>:
+ </div><pre class="screen">
+<code class="command">touch /etc/security/console.apps/foo</code>
+</pre></li><li class="listitem"><div class="para">
+ Create a PAM configuration file for the <code class="filename">foo</code> service in <code class="filename">/etc/pam.d/</code>. An easy way to do this is to copy the PAM configuration file of the <code class="command">halt</code> service, and then modify the copy if you want to change the behavior:
+ </div><pre class="screen">
+<code class="command">cp /etc/pam.d/halt /etc/pam.d/foo</code>
+</pre></li></ol></div><div class="para">
+ Now, when <code class="command">/usr/bin/<em class="replaceable"><code>foo</code></em> </code> is executed, <code class="command">consolehelper</code> is called, which authenticates the user with the help of <code class="command">/usr/sbin/userhelper</code>. To authenticate the user, <code class="command">consolehelper</code> asks for the user's password if <code class="filename">/etc/pam.d/<em class="replaceable"><code>foo</code></em> </code> is a copy of <code class="filename">/etc/pam.d/halt</code> (otherwise, it does precisely what is specified in <code class="filename">/etc/pam.d/<em class="replaceable"><code>foo</code></em> </code>) and then runs <code class="filename">/usr/sbin/<em class="replaceable"><code>foo</code></em> </code> with root permissions.
+ </div><div class="para">
+ In the PAM configuration file, an application can be configured to use the <em class="firstterm">pam_timestamp</em> module to remember (or cache) a successful authentication attempt. When an application is started and proper authentication is provided (the root password), a timestamp file is created. By default, a successful authentication is cached for five minutes. During this time, any other application that is configured to use <code class="filename">pam_timestamp</code> and run from the same session is automatically authenticated for the user — the user does not have to enter the root password again.
+ </div><div class="para">
+ This module is included in the <code class="filename">pam</code> package. To enable this feature, add the following lines to your PAM configuration file in <code class="filename">etc/pam.d/</code>:
+ </div><pre class="screen">auth include config-util account include config-util session include config-util</pre><div class="para">
+ These lines can be copied from any of the <code class="filename">/etc/pam.d/system-config-<em class="replaceable"><code>*</code></em> </code> configuration files. Note that these lines must be added <span class="emphasis"><em>below</em></span> any other <code class="computeroutput">auth sufficient</code> <code class="computeroutput">session optional</code> lines in your PAM configuration file.
+ </div><div class="para">
+ If an application configured to use <code class="filename">pam_timestamp</code> is successfully authenticated from the Applications (the main menu on the panel), the
+ <span class="inlinemediaobject"><img src="images/pam-icon.png" /></span>
+ icon is displayed in the notification area of the panel if you are running the <span class="application"><strong>GNOME</strong></span> or <span class="application"><strong>KDE</strong></span> desktop environment. After the authentication expires (the default is five minutes), the icon disappears.
+ </div><div class="para">
+ The user can select to forget the cached authentication by clicking on the icon and selecting the option to forget authentication.
+ </div></div><div class="section" title="16.6. The floppy Group" id="s1-access-floppy"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-floppy">16.6. The <code class="filename">floppy</code> Group</h2></div></div></div><div class="para">
+ If, for whatever reason, console access is not appropriate for you and your non-root users require access to your system's diskette drive, this can be done using the <code class="filename">floppy</code> group. Add the user(s) to the <code class="filename">floppy</code> group using the tool of your choice. For example, the <code class="command">gpasswd</code> command can be used to add user <code class="command">fred</code> to the <code class="filename">floppy</code> group:
+ </div><pre class="screen">
+<code class="command">gpasswd -a fred floppy</code>
+</pre><div class="para">
+ Now, user <code class="command">fred</code> is able to access the system's diskette drive from the console.
+ </div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 17. The proc File System" id="ch-proc" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 17. 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">17.1. A Virtual File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-viewing">17.1.1. Viewing Virtual Files</a></span></dt><dt><span class="section"><a href="#s2-proc-change">17.1.2. Changing Virtual Files</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-topfiles">17.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-buddyinfo">17.2.1. <code class="filename">/proc/buddyinfo</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-cmdline">17.2.2. <code class="filename">/proc/cmdline</code> </a>
</span></dt><dt><span class="section"><a href="#s2-proc-cpuinfo">17.2.3. <code class="filename">/proc/cpuinfo</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-crypto">17.2.4. <code class="filename">/proc/crypto</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-devices">17.2.5. <code class="filename">/proc/devices</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dma">17.2.6. <code class="filename">/proc/dma</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-execdomains">17.2.7. <code class="filename">/proc/execdomains</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-fb">17.2.8. <code class="filename">/proc/fb</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-filesystems">17.2.9. <code class="filename">/proc/filesystems</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-interrupts">17.2.10. <code class="filename">/proc/interrupts</code> </a></span></d
t><dt><span class="section"><a href="#s2-proc-iomem">17.2.11. <code class="filename">/proc/iomem</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-ioports">17.2.12. <code class="filename">/proc/ioports</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-kcore">17.2.13. <code class="filename">/proc/kcore</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-kmsg">17.2.14. <code class="filename">/proc/kmsg</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-loadavg">17.2.15. <code class="filename">/proc/loadavg</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-locks">17.2.16. <code class="filename">/proc/locks</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-mdstat">17.2.17. <code class="filename">/proc/mdstat</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-meminfo">17.2.18. <code class="filename">/proc/meminfo</code> </a></span></dt><dt><span class="sectio
n"><a href="#s2-proc-misc">17.2.19. <code class="filename">/proc/misc</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-modules">17.2.20. <code class="filename">/proc/modules</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-mounts">17.2.21. <code class="filename">/proc/mounts</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-mtrr">17.2.22. <code class="filename">/proc/mtrr</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-partitions">17.2.23. <code class="filename">/proc/partitions</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-pci">17.2.24. <code class="filename">/proc/pci</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-slabinfo">17.2.25. <code class="filename">/proc/slabinfo</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-stat">17.2.26. <code class="filename">/proc/stat</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-swap
s">17.2.27. <code class="filename">/proc/swaps</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-sysrq-trigger">17.2.28. <code class="filename">/proc/sysrq-trigger</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-uptime">17.2.29. <code class="filename">/proc/uptime</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-version">17.2.30. <code class="filename">/proc/version</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-proc-directories">17.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dd><dl><dt><span class="section"><a href="#s2-proc-processdirs">17.3.1. Process Directories</a></span></dt><dt><span class="section"><a href="#s2-proc-dir-bus">17.3.2. <code class="filename">/proc/bus/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-driver">17.3.3. <code class="filename">/proc/driver/</code> </a></span></dt><dt><span class="section"><a href="#s2-pro
c-dir-fs">17.3.4. <code class="filename">/proc/fs</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-irq">17.3.5. <code class="filename">/proc/irq/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-net">17.3.6. <code class="filename">/proc/net/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-scsi">17.3.7. <code class="filename">/proc/scsi/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-sys">17.3.8. <code class="filename">/proc/sys/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-dir-sysvipc">17.3.9. <code class="filename">/proc/sysvipc/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-tty">17.3.10. <code class="filename">/proc/tty/</code> </a></span></dt><dt><span class="section"><a href="#s2-proc-pid">17.3.11. <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> </a></span></dt></dl></dd><dt><span class="section">
<a href="#s1-proc-sysctl">17.4. Using the <code class="command">sysctl</code> Command</a></span></dt><dt><span class="section"><a href="#s1-proc-additional-resources">17.5. References</a></span></dt></dl></div><a id="id771662" class="indexterm"></a><a id="id582730" 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"><h2>Note</h2><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> 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 class="section" title="17.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">17.1. A Virtual File System</h2></div></div></div><a id="id858856" class="indexterm"></a><a id="id957591" class="indexterm"></a><a id="id839445" 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="17.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">17.1.1. Viewing Virtual Files</h3></div></div></div><a id="id1981915" class="indexterm"></a><a id="id1981928" 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"><h2>Note</h2><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 class="section" title="17.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">17.1.2. Changing Virtual Files</h3></div></div></div><a id="id994632" class="indexterm"></a><a id="id809790" 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"><h2>Tip</h2><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="17.4. Using the sysctl Command">Section 17.4, “Using the <code class="command">sysctl</code> Command”</a>
+ </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="17.3.8. /proc/sys/">Section 17.3.8, “ <code class="filename">/proc/sys/</code> ”</a>.
+ </div></div></div><div class="section" title="17.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">17.2. Top-level Files within the <code class="filename">proc</code> File System</h2></div></div></div><a id="id1681540" 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"><h2>Note</h2><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 class="section" title="17.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">17.2.1. <code class="filename">/proc/buddyinfo</code> </h3></div></div></div><a id="id806265" 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="17.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">17.2.2. <code class="filename">/proc/cmdline</code> </h3></div></div></div><a id="id849704" 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="17.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">17.2.3. <code class="filename">/proc/cpuinfo</code> </h3></div></div></div><a id="id845795" 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="17.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">17.2.4. <code class="filename">/proc/crypto</code> </h3></div></div></div><a id="id1691068" 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="17.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">17.2.5. <code class="filename">/proc/devices</code> </h3></div></div></div><a id="id733718" class="indexterm"></a><a id="id733744" class="indexterm"></a><a id="id699289" class="indexterm"></a><a id="id699303" class="indexterm"></a><a id="id699320" class="indexterm"></a><a id="id699338" 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>version</code></em>/Documentation/devices.txt
+</pre></div><div class="section" title="17.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">17.2.6. <code class="filename">/proc/dma</code> </h3></div></div></div><a id="id1116577" 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="17.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">17.2.7. <code class="filename">/proc/execdomains</code> </h3></div></div></div><a id="id1117104" class="indexterm"></a><a id="id1117126" class="indexterm"></a><a id="id1117143" 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="17.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">17.2.8. <code class="filename">/proc/fb</code> </h3></div></div></div><a id="id1870067" class="indexterm"></a><a id="id666119" 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="17.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">17.2.9. <code class="filename">/proc/filesystems</code> </h3></div></div></div><a id="id666164" 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="17.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">17.2.10. <code class="filename">/proc/interrupts</code> </h3></div></div></div><a id="id1020989" 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="17.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">17.2.11. <code class="filename">/proc/iomem</code> </h3></div></div></div><a id="id976607" 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="17.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">17.2.12. <code class="filename">/proc/ioports</code> </h3></div></div></div><a id="id749936" 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="17.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">17.2.13. <code class="filename">/proc/kcore</code> </h3></div></div></div><a id="id1703598" 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"><h2>Caution</h2><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 class="section" title="17.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">17.2.14. <code class="filename">/proc/kmsg</code> </h3></div></div></div><a id="id659252" 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="17.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">17.2.15. <code class="filename">/proc/loadavg</code> </h3></div></div></div><a id="id818194" 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="17.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">17.2.16. <code class="filename">/proc/locks</code> </h3></div></div></div><a id="id695774" 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="17.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">17.2.17. <code class="filename">/proc/mdstat</code> </h3></div></div></div><a id="id655611" 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="17.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">17.2.18. <code class="filename">/proc/meminfo</code> </h3></div></div></div><a id="id966128" 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="17.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">17.2.19. <code class="filename">/proc/misc</code> </h3></div></div></div><a id="id993631" 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="17.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">17.2.20. <code class="filename">/proc/modules</code> </h3></div></div></div><a id="id1939649" 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"><h2>Note</h2><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><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="17.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">17.2.21. <code class="filename">/proc/mounts</code> </h3></div></div></div><a id="id1022898" 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="17.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">17.2.22. <code class="filename">/proc/mtrr</code> </h3></div></div></div><a id="id1201034" 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>version</code></em>/Documentation/mtrr.txt
+</pre></div><div class="section" title="17.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">17.2.23. <code class="filename">/proc/partitions</code> </h3></div></div></div><a id="id753046" 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="17.2.24. /proc/pci" id="s2-proc-pci"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-pci">17.2.24. <code class="filename">/proc/pci</code> </h3></div></div></div><a id="id1757729" class="indexterm"></a><a id="id1757759" class="indexterm"></a><div class="para">
+ This file contains a full listing of every PCI device on the system. Depending on the number of PCI devices, <code class="filename">/proc/pci</code> can be rather long. A sampling of this file from a basic system looks similar to the following:
+ </div><pre class="screen">
+Bus 0, device 0, function 0: Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 3). Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe4000000 [0xe7ffffff].
+Bus 0, device 1, function 0: PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 3). Master Capable. Latency=64. Min Gnt=128.
+Bus 0, device 4, function 0: ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 2).
+Bus 0, device 4, function 1: IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 1). Master Capable. Latency=32. I/O at 0xd800 [0xd80f].
+Bus 0, device 4, function 2: USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 1). IRQ 5. Master Capable. Latency=32. I/O at 0xd400 [0xd41f].
+Bus 0, device 4, function 3: Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 2). IRQ 9.
+Bus 0, device 9, function 0: Ethernet controller: Lite-On Communications Inc LNE100TX (rev 33). IRQ 5. Master Capable. Latency=32. I/O at 0xd000 [0xd0ff].
+Bus 0, device 12, function 0: VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 1). IRQ 11. Master Capable. Latency=32. Min Gnt=4.Max Lat=255.
+</pre><div class="para">
+ This output shows a list of all PCI devices, sorted in the order of bus, device, and function. 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 class="note"><h2>Tip</h2><div class="para">
+ To get a more readable version of this information, type:
+ </div><pre class="screen">
+/sbin/lspci -vb
+</pre></div></div><div class="section" title="17.2.25. /proc/slabinfo" id="s2-proc-slabinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-slabinfo">17.2.25. <code class="filename">/proc/slabinfo</code> </h3></div></div></div><a id="id1209112" class="indexterm"></a><a id="id1209135" 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="17.2.26. /proc/stat" id="s2-proc-stat"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-stat">17.2.26. <code class="filename">/proc/stat</code> </h3></div></div></div><a id="id1979271" class="indexterm"></a><a id="id1979294" class="indexterm"></a><a id="id1979308" 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="17.2.27. /proc/swaps" id="s2-proc-swaps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-swaps">17.2.27. <code class="filename">/proc/swaps</code> </h3></div></div></div><a id="id707897" 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="17.2.28. /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">17.2.28. <code class="filename">/proc/sysrq-trigger</code> </h3></div></div></div><a id="id638152" 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="17.3.8.3. /proc/sys/kernel/">Section 17.3.8.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="17.2.29. /proc/uptime" id="s2-proc-uptime"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-uptime">17.2.29. <code class="filename">/proc/uptime</code> </h3></div></div></div><a id="id1708981" 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="17.2.30. /proc/version" id="s2-proc-version"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-version">17.2.30. <code class="filename">/proc/version</code> </h3></div></div></div><a id="id787692" 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="17.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">17.3. Directories within <code class="filename">/proc/</code> </h2></div></div></div><a id="id641001" 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="17.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">17.3.1. Process Directories</h3></div></div></div><a id="id641041" 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="17.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">17.3.1.1. <code class="filename">/proc/self/</code> </h4></div></div></div><a id="id885573" 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="17.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">17.3.2. <code class="filename">/proc/bus/</code> </h3></div></div></div><a id="id878980" 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="17.3.3. /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">17.3.3. <code class="filename">/proc/driver/</code> </h3></div></div></div><a id="id698856" 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>version</code></em>/Documentation/rtc.txt</code>.
+ </div></div><div class="section" title="17.3.4. /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">17.3.4. <code class="filename">/proc/fs</code> </h3></div></div></div><a id="id978624" 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="17.3.5. /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">17.3.5. <code class="filename">/proc/irq/</code> </h3></div></div></div><a id="id727203" 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>version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><div class="section" title="17.3.6. /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">17.3.6. <code class="filename">/proc/net/</code> </h3></div></div></div><a id="id659307" 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="17.3.7. /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">17.3.7. <code class="filename">/proc/scsi/</code> </h3></div></div></div><a id="id762945" 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="17.3.8. /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">17.3.8. <code class="filename">/proc/sys/</code> </h3></div></div></div><a id="id1710752" class="indexterm"></a><a id="id1710775" class="indexterm"></a><a id="id922270" class="indexterm"></a><a id="id922301" class="indexterm"></a><a id="id922320" class="indexterm"></a><a id="id922334" 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"><h2>Caution</h2><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 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"><h2>Note</h2><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="17.4. Using the sysctl Command">Section 17.4, “Using the <code class="command">sysctl</code> Command”</a>.
+ </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="17.3.8.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">17.3.8.1. <code class="filename">/proc/sys/dev/</code> </h4></div></div></div><a id="id659085" 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="17.3.8.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">17.3.8.2. <code class="filename">/proc/sys/fs/</code> </h4></div></div></div><a id="id958796" 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="17.3.8.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">17.3.8.3. <code class="filename">/proc/sys/kernel/</code> </h4></div></div></div><a id="id602014" class="indexterm"></a><a id="id964142" class="indexterm"></a><a id="id964157" class="indexterm"></a><a id="id964176" class="indexterm"></a><a id="id964194" 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"><h2>Important</h2><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></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">1990</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"><h2>Caution</h2><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 class="para">
+ Refer to <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>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="17.3.8.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">17.3.8.4. <code class="filename">/proc/sys/net/</code> </h4></div></div></div><a id="id838057" class="indexterm"></a><a id="id838087" class="indexterm"></a><a id="id838101" class="indexterm"></a><a id="id838116" 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"><h2>Caution</h2><div class="para">
+ An erroneous change to these files may affect remote connectivity to the system.
+ </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>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>version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><div class="section" title="17.3.8.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">17.3.8.5. <code class="filename">/proc/sys/vm/</code> </h4></div></div></div><a id="id1011154" class="indexterm"></a><a id="id712805" class="indexterm"></a><a id="id712820" 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"><h2>Tip</h2><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></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>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>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"><h2>Note</h2><div class="para">
+ This setting is only recommended for systems with swap areas larger than physical memory.
+ </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>version</code></em>/Documentation/</code>, which contains additional information.
+ </div></div></div><div class="section" title="17.3.9. /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">17.3.9. <code class="filename">/proc/sysvipc/</code> </h3></div></div></div><a id="id698818" 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="17.3.10. /proc/tty/" id="s2-proc-tty"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-tty">17.3.10. <code class="filename">/proc/tty/</code> </h3></div></div></div><a id="id1117776" 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="17.3.11. /proc/PID/" id="s2-proc-pid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-pid">17.3.11. <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> </h3></div></div></div><a id="id867950" 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="17.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">17.4. Using the <code class="command">sysctl</code> Command</h2></div></div></div><a id="id947873" class="indexterm"></a><a id="id947887" class="indexterm"></a><a id="id1709982" class="indexterm"></a><a id="id1710005" class="indexterm"></a><a id="id1710035" class="indexterm"></a><a id="id959577" 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="17.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">17.5. References</h2></div></div></div><a id="id2012044" 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="id2012079" 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>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>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>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>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="id719909" 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 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><dd><dl><dt><span class="section"><a href="#s2-sysconfig-arpwatch">18.1.1. <code class="filename">/etc/sysconfig/arpwatch</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-authconfig">18.1.2. <code class="filename">/etc/sysconfig/authconfig</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-autofs">18.1.3. <code class="filename">/etc/sysconfig/autofs</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-clock">18.1.4. <code class="filename">/etc/sysconfig/clock</code>
</a></span></dt><dt><span class="section"><a href="#s2-sysconfig-desktop">18.1.5. <code class="filename">/etc/sysconfig/desktop</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-dhcpd">18.1.6. <code class="filename">/etc/sysconfig/dhcpd</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-firewall">18.1.7. <code class="filename">/etc/sysconfig/firstboot</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-i18n">18.1.8. <code class="filename">/etc/sysconfig/i18n</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-init">18.1.9. <code class="filename">/etc/sysconfig/init</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-ip6tables">18.1.10. <code class="filename">/etc/sysconfig/ip6tables-config</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-kybd">18.1.11. <code class="filename">/etc/sysconfig/keyboard</code> </a></span></dt><dt><span class="sectio
n"><a href="#s2-sysconfig-named">18.1.12. <code class="filename">/etc/sysconfig/named</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-network">18.1.13. <code class="filename">/etc/sysconfig/network</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-ntpd">18.1.14. <code class="filename">/etc/sysconfig/ntpd</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-radvd">18.1.15. <code class="filename">/etc/sysconfig/radvd</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-samba">18.1.16. <code class="filename">/etc/sysconfig/samba</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-selinux">18.1.17. <code class="filename">/etc/sysconfig/selinux</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-sendmail">18.1.18. <code class="filename">/etc/sysconfig/sendmail</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-spamd">18.1.19. <co
de class="filename">/etc/sysconfig/spamassassin</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-squid">18.1.20. <code class="filename">/etc/sysconfig/squid</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-rcu">18.1.21. <code class="filename">/etc/sysconfig/system-config-users</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-vncservers">18.1.22. <code class="filename">/etc/sysconfig/vncservers</code> </a></span></dt><dt><span class="section"><a href="#s2-sysconfig-xinetd">18.1.23. <code class="filename">/etc/sysconfig/xinetd</code> </a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="#s2-sysconfig-installed-documentati
on">18.3.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id1774498" class="indexterm"></a><a id="id940148" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/</code> directory contains a variety of system configuration files for Fedora.
+ </div><div class="para">
+ This chapter outlines some of the files 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="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="id782326" class="indexterm"></a><div class="para">
+ The following sections offer descriptions of files normally found in the <code class="filename">/etc/sysconfig/</code> directory. Files not listed here, as well as extra file options, are found in the <code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code><version-number></code></em>/sysconfig.txt</code> file (replace <em class="replaceable"><code><version-number></code></em> with the version of the <code class="filename">initscripts</code> package). Alternatively, looking through the initscripts in the <code class="filename">/etc/rc.d/</code> directory can prove helpful.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ If some of the files listed here are not present in the <code class="filename">/etc/sysconfig/</code> directory, then the corresponding program may not be installed.
+ </div></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="id859544" 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. The <code class="command">arpwatch</code> daemon maintains a table of Ethernet MAC addresses and their IP address pairings. By default, this file sets the owner of the <code class="command">arpwatch</code> process to the user <code class="computeroutput">pcap</code> and sends any messages to the <code class="command">root</code> mail queue. For more information regarding available parameters for this file, refer to the <code class="command">arpwatch</code> man page.
+ </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="id1011220" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/authconfig</code> file sets the authorization to be used on the host. It contains one or more of the following lines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">PASSWORDALGORITHM=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">descrypt</code> — DESCRYPT is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">bigcrypt</code> — BIGCRYPT is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">md5</code> — MD5 is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sha256</code> — SHA256 is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sha512</code> — SHA512 is used for authentication.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">USEKERBEROS=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Kerberos is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Kerberos is not used for authentication.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">USELDAPAUTH=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — LDAP is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — LDAP is not used for authentication.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">FORCELEGACY=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — The implicit use of SSSD by the <span class="application"><strong>Authentication Configuration Tool</strong></span> is disabled.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — The implicit use of SSSD by the <span class="application"><strong>Authentication Configuration Tool</strong></span> is enabled.
+ </div></li></ul></div></li></ul></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="id1125343" 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-ROMs, diskettes, and other media.
+ </div><div class="para">
+ The <code class="filename">/etc/sysconfig/autofs</code> file may contain the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">LOCALOPTIONS="<em class="replaceable"><code><value></code></em>"</code>, where <em class="replaceable"><code><value></code></em> is a string for defining machine-specific automount rules. The default value is an empty string (<code class="command">""</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">DAEMONOPTIONS="<em class="replaceable"><code><value></code></em>"</code>, where <em class="replaceable"><code><value></code></em> is the timeout length in seconds before unmounting the device. The default value is 60 seconds (<code class="command">"--timeout=60"</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">UNDERSCORETODOT=<em class="replaceable"><code><value></code></em> </code>, where <em class="replaceable"><code><value></code></em> is a binary value that controls whether to convert underscores in file names into dots. For example, <code class="command">auto_home</code> to <code class="command">auto.home</code> and <code class="command">auto_mnt</code> to <code class="command">auto.mnt</code>. The default value is 1 (true).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">DISABLE_DIRECT=<em class="replaceable"><code><value></code></em> </code>, where <em class="replaceable"><code><value></code></em> is a binary value that controls whether to disable direct mount support, as the Linux implementation does not conform to the Sun Microsystems' automounter behavior. The default value is 1 (true), and allows for compatibility with the Sun automounter options specification syntax.
+ </div></li></ul></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="id917231" 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.
+ </div><div class="para">
+ The correct values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">UTC=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following boolean values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">true</code> or <code class="command">yes</code> — The hardware clock is set to Universal Time.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">false</code> or <code class="command">no</code> — The hardware clock is set to local time.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">ARC=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the following:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">false</code> or <code class="command">no</code> — This value indicates that the normal UNIX epoch is in use. Other values are used by systems not supported by Fedora.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SRM=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the following:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">false</code> or <code class="command">no</code> — This value indicates that the normal UNIX epoch is in use. Other values are used by systems not supported by Fedora.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ZONE=<code class="filename"><em class="replaceable"><code><filename></code></em> </code> </code> — The time zone file under <code class="filename">/usr/share/zoneinfo</code> that <code class="filename">/etc/localtime</code> is a copy of. The file contains information such as:
+ </div><pre class="screen">ZONE="America/New York"
+</pre><div class="para">
+ Note that the <code class="command">ZONE</code> parameter is read by the <span class="application"><strong>Time and Date Properties Tool</strong></span> (<code class="command">system-config-date</code>), and manually editing it does not change the system timezone.
+ </div></li></ul></div><div class="para">
+ Earlier releases of Fedora used the following values (which are deprecated):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">CLOCKMODE=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">GMT</code> — The clock is set to Universal Time (Greenwich Mean Time).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ARC</code> — The ARC console's 42-year time offset is in effect (for Alpha-based systems only).
+ </div></li></ul></div></li></ul></div></div><div class="section" title="18.1.5. /etc/sysconfig/desktop" id="s2-sysconfig-desktop"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-desktop">18.1.5. <code class="filename">/etc/sysconfig/desktop</code> </h3></div></div></div><a id="id611167" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/desktop</code> file specifies the desktop for new users and the display manager to run when entering runlevel 5.
+ </div><div class="para">
+ Correct values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">DESKTOP="<em class="replaceable"><code><value></code></em>"</code>, where <code class="command">"<em class="replaceable"><code><value></code></em>"</code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">GNOME</code> — Selects the <span class="application"><strong>GNOME</strong></span> desktop environment.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">KDE</code> — Selects the <span class="application"><strong>KDE</strong></span> desktop environment.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">DISPLAYMANAGER="<em class="replaceable"><code><value></code></em>"</code>, where <code class="command">"<em class="replaceable"><code><value></code></em>"</code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">GNOME</code> — Selects the <span class="application"><strong>GNOME Display Manager</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">KDE</code> — Selects the <span class="application"><strong>KDE Display Manager</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">XDM</code> — Selects the <span class="application"><strong>X Display Manager</strong></span>.
+ </div></li></ul></div></li></ul></div><div class="para">
+ For more information, refer to <a class="xref" href="#ch-The_X_Window_System" title="Chapter 21. The X Window System">Chapter 21, <i>The X Window System</i></a>.
+ </div></div><div class="section" title="18.1.6. /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.6. <code class="filename">/etc/sysconfig/dhcpd</code> </h3></div></div></div><a id="id1017461" 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. The <code class="command">dhcpd</code> daemon implements the Dynamic Host Configuration Protocol (DHCP) and the Internet Bootstrap Protocol (BOOTP). DHCP and BOOTP assign IP addresses and other configuration information to machines on the network. For more information about what parameters are available in this file, refer to the <code class="command">dhcpd</code> man page.
+ </div></div><div class="section" title="18.1.7. /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.7. <code class="filename">/etc/sysconfig/firstboot</code> </h3></div></div></div><a id="id761594" class="indexterm"></a><div class="para">
+ The first time the system boots, the <code class="command">/sbin/init</code> program calls the <code class="filename">etc/rc.d/init.d/firstboot</code> script, which in turn launches the <span class="application"><strong> Setup Agent</strong></span>. This application allows the user to install the latest updates as well as additional applications and documentation.
+ </div><div class="para">
+ The <code class="filename">/etc/sysconfig/firstboot</code> file tells the <span class="application"><strong> Setup Agent</strong></span> application not to run on subsequent reboots. To run it the next time the system boots, remove <code class="filename">/etc/sysconfig/firstboot</code> and execute <code class="command">chkconfig --level 5 firstboot on</code>.
+ </div></div><div class="section" title="18.1.8. /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.8. <code class="filename">/etc/sysconfig/i18n</code> </h3></div></div></div><div class="para">
+ The <code class="filename">/etc/sysconfig/i18n</code> file sets the default language, any supported languages, and the default system font. For example:
+ </div><pre class="screen">LANG="en_US.UTF-8"
+SUPPORTED="en_US.UTF-8:en_US:en"
+SYSFONT="latarcyrheb-sun16"
+</pre></div><div class="section" title="18.1.9. /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.9. <code class="filename">/etc/sysconfig/init</code> </h3></div></div></div><a id="id934395" 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.
+ </div><div class="para">
+ The following values may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">BOOTUP=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">color</code> — The standard color boot display, where the success or failure of devices and services starting up is shown in different colors.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">verbose</code> — An old style display which provides more information than purely a message of success or failure.
+ </div></li><li class="listitem"><div class="para">
+ Anything else means a new display, but without ANSI-formatting.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">RES_COL=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the number of the column of the screen to start status labels. The default is set to 60.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MOVE_TO_COL=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> moves the cursor to the value in the <code class="filename">RES_COL</code> line via the <code class="command">echo -en</code> command.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SETCOLOR_SUCCESS=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> sets the success color via the <code class="command">echo -en</code> command. The default color is set to green.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SETCOLOR_FAILURE=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> sets the failure color via the <code class="command">echo -en</code> command. The default color is set to red.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SETCOLOR_WARNING=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> sets the warning color via the <code class="command">echo -en</code> command. The default color is set to yellow.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SETCOLOR_NORMAL=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> resets the color to "normal" via the <code class="command">echo -en</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">LOGLEVEL=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> sets the initial console logging level for the kernel. The default is 3; 8 means everything (including debugging), while 1 means only kernel panics. The <code class="command">rsyslog</code> daemon overrides this setting once started.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">PROMPT=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following boolean values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Enables the key check for interactive mode.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Disables the key check for interactive mode.
+ </div></li></ul></div></li></ul></div></div><div class="section" title="18.1.10. /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.10. <code class="filename">/etc/sysconfig/ip6tables-config</code> </h3></div></div></div><a id="id886557" 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.
+ </div><div class="para">
+ Do not modify this file by hand unless familiar with how to construct <code class="command">ip6tables</code> rules. Rules also can be created manually using the <code class="command">/sbin/ip6tables</code> command. Once created, add the rules to the <code class="filename">/etc/sysconfig/ip6tables</code> file by typing the following command:
+ </div><pre class="screen">
+<code class="command">/sbin/service ip6tables save</code>
+</pre><div class="para">
+ Once this file exists, any firewall rules saved in it persists through a system reboot or a service restart.
+ </div><div class="para">
+ For more information on <code class="command">ip6tables</code>, refer to .
+ </div></div><div class="section" title="18.1.11. /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.11. <code class="filename">/etc/sysconfig/keyboard</code> </h3></div></div></div><a id="id721908" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/keyboard</code> file controls the behavior of the keyboard. The following values may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">KEYBOARDTYPE="sun|pc"</code> where <code class="command">sun</code> means a Sun keyboard is attached on <code class="filename">/dev/kbd</code>, or <code class="command">pc</code> means a PS/2 keyboard connected to a PS/2 port.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">KEYTABLE="<em class="replaceable"><code><file></code></em>"</code>, where <code class="command"><em class="replaceable"><code><file></code></em> </code> is the name of a keytable file.
+ </div><div class="para">
+ For example: <code class="command">KEYTABLE="us"</code>. The files that can be used as keytables start in <code class="filename">/lib/kbd/keymaps/i386</code> and branch into different keyboard layouts from there, all labeled <code class="filename"><em class="replaceable"><code><file></code></em>.kmap.gz</code>. The first file found beneath <code class="filename">/lib/kbd/keymaps/i386</code> that matches the <code class="command">KEYTABLE</code> setting is used.
+ </div></li></ul></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="id1019581" 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. The <code class="command">named</code> daemon is a <em class="firstterm">Domain Name System</em> (<em class="firstterm">DNS</em>) server which implements the <em class="firstterm">Berkeley Internet Name Domain</em> (<em class="firstterm">BIND</em>) version 9 distribution. This server maintains a table of which hostnames are associated with IP addresses on the network.
+ </div><div class="para">
+ Currently, only the following values may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">ROOTDIR=<em class="replaceable"><code>"</some/where>"</code></em> </code>, where <code class="command"><em class="replaceable"><code></some/where></code></em> </code> refers to the full directory path of a configured chroot environment under which <code class="command">named</code> runs. This chroot environment must first be configured. Type <code class="command">info chroot</code> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">OPTIONS=<em class="replaceable"><code>"<value>"</code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is any option listed in the man page for <code class="command">named</code> except <code class="option">-t</code>. In place of <code class="option">-t</code>, use the <code class="command">ROOTDIR</code> line above.
+ </div></li></ul></div><div class="para">
+ For more information about available parameters for this file, refer to the <code class="command">named</code> man page. For detailed information on how to configure a BIND DNS server, refer to <a class="xref" href="#ch-The_BIND_DNS_Server" title="Chapter 7. The BIND DNS Server">Chapter 7, <i>The BIND DNS Server</i></a>. By default, the file contains no parameters.
+ </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="id605155" 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. The following values may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">NETWORKING=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following boolean values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Networking should be configured.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Networking should not be configured.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">HOSTNAME=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> should be the <em class="firstterm">Fully Qualified Domain Name</em> (<em class="firstterm">FQDN</em>), such as <code class="filename">hostname.expample.com</code>, but can be whatever hostname is necessary.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">GATEWAY=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the IP address of the network's gateway.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">GATEWAYDEV=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the gateway device, such as <code class="filename">eth0</code>. Configure this option if you have multiple interfaces on the same subnet, and require one of those interfaces to be the preferred route to the default gateway.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">NISDOMAIN=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the NIS domain name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">NOZEROCONF=<em class="replaceable"><code><value></code></em> </code>, where setting <code class="command"><em class="replaceable"><code><value></code></em> </code> to <code class="command">true</code> disables the zeroconf route.
+ </div><div class="para">
+ By default, the zeroconf route (169.254.0.0) is enabled when the system boots. For more information about zeroconf, refer to <a href="http://www.zeroconf.org/">http://www.zeroconf.org/</a>.
+ </div></li></ul></div><div class="warning"><h2>Warning</h2><div class="para">
+ Do not use custom initscripts to configure network settings. When performing a post-boot network service restart, custom initscripts configuring network settings that are run outside of the network init script lead to unpredictable results.
+ </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="id924091" 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. The <code class="command">ntpd</code> daemon sets and maintains the system clock to synchronize with an Internet standard time server. It implements version 4 of the Network Time Protocol (NTP). For more information about what parameters are available for this file, use a Web browser to view the following file: <code class="filename">/usr/share/doc/ntp-<em class="replaceable"><code><version></code></em>/ntpd.htm</code> (where <em class="replaceable"><code><version></code></em> is the version number of <code class="command">ntpd</code>). By default, this file sets the owner of the <code class="command">ntpd</code> process to the user <code class="computeroutput">ntp</code>.
+ </div></div><div class="section" title="18.1.15. /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.15. <code class="filename">/etc/sysconfig/radvd</code> </h3></div></div></div><a id="id700258" 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. The <code class="command">radvd</code> daemon listens for router requests and sends router advertisements for the IP version 6 protocol. This service allows hosts on a network to dynamically change their default routers based on these router advertisements. For more information about available parameters for this file, refer to the <code class="command">radvd</code> man page. By default, this file sets the owner of the <code class="command">radvd</code> process to the user <code class="computeroutput">radvd</code>.
+ </div></div><div class="section" title="18.1.16. /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.16. <code class="filename">/etc/sysconfig/samba</code> </h3></div></div></div><a id="id577217" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/samba</code> file is used to pass arguments to the <code class="command">smbd</code> and the <code class="command">nmbd</code> daemons at boot time. The <code class="command">smbd</code> daemon offers file sharing connectivity for Windows clients on the network. The <code class="command">nmbd</code> daemon offers NetBIOS over IP naming services. For more information about what parameters are available for this file, refer to the <code class="command">smbd</code> man page. By default, this file sets <code class="command">smbd</code> and <code class="command">nmbd</code> to run in daemon mode.
+ </div></div><div class="section" title="18.1.17. /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.17. <code class="filename">/etc/sysconfig/selinux</code> </h3></div></div></div><a id="id1483854" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/selinux</code> file contains the basic configuration options for SELinux. This file is a symbolic link to <code class="filename">/etc/selinux/config</code>.
+ </div></div><div class="section" title="18.1.18. /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.18. <code class="filename">/etc/sysconfig/sendmail</code> </h3></div></div></div><a id="id644610" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/sendmail</code> file allows messages to be sent to one or more clients, routing the messages over whatever networks are necessary. The file sets the default values for the <span class="application"><strong>Sendmail</strong></span> application to run. Its default values are set to run as a background daemon and to check its queue each hour in case something has backed up.
+ </div><div class="para">
+ Values include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">DAEMON=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — <span class="application"><strong>Sendmail</strong></span> should be configured to listen to port 25 for incoming mail. <code class="command">yes</code> implies the use of <span class="application"><strong>Sendmail</strong></span>'s <code class="command">-bd</code> options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — <span class="application"><strong>Sendmail</strong></span> should not be configured to listen to port 25 for incoming mail.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">QUEUE=1h</code> which is given to <span class="application"><strong>Sendmail</strong></span> as <code class="command">-q$QUEUE</code>. The <code class="command">-q</code> option is not given to <span class="application"><strong>Sendmail</strong></span> if <code class="filename">/etc/sysconfig/sendmail</code> exists and <code class="filename">QUEUE</code> is empty or undefined.
+ </div></li></ul></div></div><div class="section" title="18.1.19. /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.19. <code class="filename">/etc/sysconfig/spamassassin</code> </h3></div></div></div><a id="id981912" 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. <span class="application"><strong>Spamassassin</strong></span> is an email spam filter application. For a list of available options, refer to the <code class="command">spamd</code> man page. By default, it configures <code class="command">spamd</code> to run in daemon mode, create user preferences, and auto-create whitelists (allowed bulk senders).
+ </div><div class="para">
+ For more information about <span class="application"><strong>Spamassassin</strong></span>, refer to <a class="xref" href="#s3-email-mda-spam" title="13.5.2.6. Spam Filters">Section 13.5.2.6, “Spam Filters”</a>.
+ </div></div><div class="section" title="18.1.20. /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.20. <code class="filename">/etc/sysconfig/squid</code> </h3></div></div></div><a id="id1778675" 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. The <code class="command">squid</code> daemon is a proxy caching server for Web client applications. For more information on configuring a <code class="command">squid</code> proxy server, use a Web browser to open the <code class="filename">/usr/share/doc/squid-<em class="replaceable"><code><version></code></em>/</code> directory (replace <em class="replaceable"><code><version></code></em> with the <code class="command">squid</code> version number installed on the system). By default, this file sets <code class="command">squid</code> to start in daemon mode and sets the amount of time before it shuts itself down.
+ </div></div><div class="section" title="18.1.21. /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.21. <code class="filename">/etc/sysconfig/system-config-users</code> </h3></div></div></div><a id="id901996" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/system-config-users</code> file is the configuration file for the graphical application, <span class="application"><strong> User Manager</strong></span>. This file is used to filter out system users such as <code class="command">root</code>, <code class="command">daemon</code>, or <code class="command">lp</code>. This file is edited by the <span class="guimenu"><strong>Preferences</strong></span> > <span class="guimenuitem"><strong>Filter system users and groups</strong></span> pull-down menu in the <span class="application"><strong> User Manager</strong></span> application and should never be edited by hand. For more information on using this application, refer to <a class="xref" href="#s1-users-configui" title="22.1. User and Group Configuration">Section 22.1, “User and Group Configuration”</a>.
+ </div></div><div class="section" title="18.1.22. /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.22. <code class="filename">/etc/sysconfig/vncservers</code> </h3></div></div></div><a id="id756217" 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.
+ </div><div class="para">
+ VNC is a remote display system which allows users to view the desktop environment not only on the machine where it is running but across different networks on a variety of architectures.
+ </div><div class="para">
+ It may contain the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">VNCSERVERS=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is set to something like <code class="command">"1:fred"</code>, to indicate that a VNC server should be started for user fred on display :1. User fred must have set a VNC password using the <code class="command">vncpasswd</code> command before attempting to connect to the remote VNC server.
+ </div></li></ul></div></div><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN" class="section" title="18.1.23. /etc/sysconfig/xinetd" id="s2-sysconfig-xinetd" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-xinetd">18.1.23. <code class="filename">/etc/sysconfig/xinetd</code> </h3></div></div></div><a id="id587970" 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. The <code class="command">xinetd</code> daemon starts programs that provide Internet services when a request to the port for that service is received. For more information about available parameters for this file, refer to the <code class="command">xinetd</code> man page. For more information on the <code class="command">xinetd</code> service, refer to .
+ </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="id1759743" class="indexterm"></a><div class="para">
+ The following directories are normally found in <code class="filename">/etc/sysconfig/</code>.
+ </div><a id="id763823" class="indexterm"></a><div class="variablelist"><dl><dt><span class="term"> <code class="filename">apm-scripts/</code> </span></dt><dd><div class="para">
+ This directory contains the APM suspend/resume script. Do not edit the files directly. If customization is necessary, create a file called <code class="filename">/etc/sysconfig/apm-scripts/apmcontinue</code> which is called at the end of the script. It is also possible to control the script by editing <code class="filename">/etc/sysconfig/apmd</code>.
+ </div></dd><dt><span class="term"> <code class="filename">cbq/</code> </span></dt><dd><div class="para">
+ <a id="id1529748" 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><span class="term"> <code class="filename">networking/</code> </span></dt><dd><div class="para">
+ <a id="id768157" 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><span class="term"> <code class="filename">network-scripts/</code> </span></dt><dd><div class="para">
+ <a id="id722215" 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="filename">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">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><span class="term"> <code class="filename">rhn/</code> </span></dt><dd><div class="para">
+ <a id="id785316" 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="id922234" 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="id922269" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code><version-number></code></em>/sysconfig.txt</code> — This file contains a more authoritative listing of the files found in the <code class="filename">/etc/sysconfig/</code> directory and the configuration options available for them. The <em class="replaceable"><code><version-number></code></em> in the path to this file corresponds to the version of the <code class="command">initscripts</code> package installed.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 19. Date and Time Configuration" id="chap-Date_and_Time_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. 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">19.1. Date/Time Properties Tool</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Date_and_Time">19.1.1. Date and Time Properties</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Network_Time_Protocol">19.1.2. Network Time Protocol Properties</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Time_Zone">19.1.3. Time Zone Properties</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration">19.
2. Command Line Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">19.2.1. Date and Time Setup</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">19.2.2. Network Time Protocol Setup</a></span></dt></dl></dd></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="19.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">19.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> (see <a class="xref" href="#ch-The_X_Window_System" title="Chapter 21. The X Window System">Chapter 21, <i>The X Window System</i></a> for more information on this topic).
+ </div><a id="id1003948" 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 19.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 19.1. Authentication Query</h6></div><br class="figure-break" /><div class="section" title="19.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">19.1.1. Date and Time Properties</h3></div></div></div><a id="id996746" class="indexterm"></a><a id="id860260" class="indexterm"></a><div class="para">
+ As shown in <a class="xref" href="#figu-Date_and_Time_Configuration-Date_and_Time" title="Figure 19.2. Date and Time Properties">Figure 19.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 19.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 19.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="19.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">19.1.2. Network Time Protocol Properties</h3></div></div></div><a id="id858713" class="indexterm"></a><a id="id814633" class="indexterm"></a><a id="id814646" class="indexterm"></a><a id="id814660" class="indexterm"></a><a id="id777683" 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 19.3. Network Time Protocol Properties">Figure 19.3, “Network Time Protocol Properties”</a>.
+ </div><div class="figure" title="Figure 19.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 19.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"><h2>Note</h2><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 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="19.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">19.1.3. Time Zone Properties</h3></div></div></div><a id="id997315" 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 19.4. Time Zone Properties">Figure 19.4, “Time Zone Properties”</a>.
+ </div><div class="figure" title="Figure 19.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 19.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="19.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">19.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="19.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">19.2.1. Date and Time Setup</h3></div></div></div><a id="id640735" class="indexterm"></a><a id="id640753" class="indexterm"></a><a id="id624520" 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 19.1. Displaying the current date and time" id="ex-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time"><div class="example-contents"><pre class="screen">~]$ <code class="command">date</code>
+Wed Jun 2 11:58:48 CEST 2010</pre></div><h6>Example 19.1. Displaying the current date and time</h6></div><br class="example-break" /></div><div class="section" title="19.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">19.2.2. Network Time Protocol Setup</h3></div></div></div><a id="id669056" class="indexterm"></a><a id="id690736" class="indexterm"></a><a id="id690749" class="indexterm"></a><a id="id690765" 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 adresses:
+ </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="19.2.1. Date and Time Setup">Section 19.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 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a>.
+ </div><div class="note"><h2>Note</h2><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></li></ol></div><a id="id1846429" class="indexterm"></a><a id="id1846442" class="indexterm"></a><a id="id1846460" 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 13, 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"><h2>Tip</h2><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></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 20. Keyboard Configuration" id="ch-Keyboard_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. Keyboard Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-keyboard-layout">20.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="#s1-keyboard-indicator">20.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="#s1-keyboard-break">20.3. Setting Up a Typing Break</a></span></dt></dl></div><a id="id1127271" 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="20.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">20.1. Changing the Keyboard Layout</h2></div></div></div><a id="id957721" class="indexterm"></a><a id="id622710" class="indexterm"></a><a id="id803307" 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 20.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 20.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 20.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 20.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 20.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 20.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 20.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 20.4. Testing the layout</h6></div><br class="figure-break" /><div class="note"><h2>Suggestion: Disable Separate Layout for Each Window</h2><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 20.3. Selecting the default layout">Figure 20.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 class="section" title="20.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">20.2. Adding the Keyboard Layout Indicator</h2></div></div></div><a id="id884086" class="indexterm"></a><a id="id884099" 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 20.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 20.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 20.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 20.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 20.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 20.7. The <span class="application">Keyboard Indicator</span> applet</h6></div><br class="figure-break" /></div><div class="section" title="20.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">20.3. Setting Up a Typing Break</h2></div></div></div><a id="id1476623" 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 20.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 20.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 20.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 20.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 21. The X Window System" id="ch-The_X_Window_System" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. The X Window System</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-x-server">21.1. The X11R7.1 Release</a></span></dt><dt><span class="section"><a href="#s1-x-clients">21.2. Desktop Environments and Window Managers</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-clients-desktop">21.2.1. Desktop Environments</a></span></dt><dt><span class="section"><a href="#s2-x-clients-winmanagers">21.2.2. Window Managers</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-server-configuration">21.3. X Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-server-config-xorg.conf">21.3.1. <code class="filename">xorg.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="
#s1-x-fonts">21.4. Fonts</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-fonts-fontconfig">21.4.1. Fontconfig</a></span></dt><dt><span class="section"><a href="#s2-x-fonts-core">21.4.2. Core X Font System</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-runlevels">21.5. Runlevels and X</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-runlevels-3">21.5.1. Runlevel 3</a></span></dt><dt><span class="section"><a href="#s2-x-runlevels-5">21.5.2. Runlevel 5</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-x-additional-resources">21.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-x-installed-documentation">21.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-x-useful-websites">21.6.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id589686" class="indexterm"></a><a id="id1016149" class="indexterm"></a><a id="id703478" class="indexterm"></
a><a id="id985533" class="indexterm"></a><a id="id828112" class="indexterm"></a><div class="para">
+ While the heart of Fedora is the kernel, for many users, the face of the operating system is the graphical environment provided by the <em class="firstterm">X Window System</em>, also called <em class="firstterm">X</em>.
+ </div><div class="para">
+ Other windowing environments have existed in the UNIX world, including some that predate the release of the X Window System in June 1984. Nonetheless, X has been the default graphical environment for most UNIX-like operating systems, including Fedora, for many years.
+ </div><div class="para">
+ The graphical environment for Fedora is supplied by the <em class="firstterm">X.Org Foundation</em>, an open source organization created to manage development and strategy for the X Window System and related technologies. X.Org is a large-scale, rapidly developing project with hundreds of developers around the world. It features a wide degree of support for a variety of hardware devices and architectures, and can run on a variety of different operating systems and platforms. This release for Fedora specifically includes the X11R7.1 release of the X Window System.
+ </div><div class="para">
+ The X Window System uses a client-server architecture. The <em class="firstterm">X server</em> (the <code class="command">Xorg</code> binary) listens for connections from <em class="firstterm">X client</em> applications via a network or local loopback interface. The server communicates with the hardware, such as the video card, monitor, keyboard, and mouse. X client applications exist in the user-space, creating a <em class="firstterm">graphical user interface</em> (<em class="firstterm">GUI</em>) for the user and passing user requests to the X server.
+ </div><div class="section" title="21.1. The X11R7.1 Release" id="s1-x-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-server">21.1. The X11R7.1 Release</h2></div></div></div><a id="id648273" class="indexterm"></a><div class="para">
+ Fedora 13 uses the X11R7.1 release as the base X Window System, which includes several video driver, EXA, and platform support enhancements over the previous release, among others. In addition, this release also includes several automatic configuration features for the X server.
+ </div><div class="para">
+ X11R7.1 is the first release to take specific advantage of the modularization of the X Window System. This modularization, which splits X into logically distinct modules, makes it easier for open source developers to contribute code to the system.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Fedora no longer provides the <span class="trademark">XFree86</span>™ server packages. Before upgrading a system to the latest version of Fedora, be sure that the system's video card is compatible with the X11R7.1 release by checking the Red Hat Hardware Compatibility List located online at <a href="http://hardware.redhat.com/">http://hardware.redhat.com/</a>.
+ </div></div><div class="para">
+ In the X11R7.1 release, all libraries, headers, and binaries now live under <code class="filename">/usr/</code> instead of <code class="filename">/usr/X11R6</code>. The <code class="filename">/etc/X11/</code> directory contains configuration files for X client and server applications. This includes configuration files for the X server itself, the <code class="command">xfs</code> font server, the X display managers, and many other base components.
+ </div><div class="para">
+ The configuration file for the newer Fontconfig-based font architecture is still <code class="filename">/etc/fonts/fonts.conf</code>. For more on configuring and adding fonts, refer to <a class="xref" href="#s1-x-fonts" title="21.4. Fonts">Section 21.4, “Fonts”</a>.
+ </div><div class="para">
+ Because the X server performs advanced tasks on a wide array of hardware, it requires detailed information about the hardware it works on. The X server automatically detects some of this information; other details must be configured.
+ </div><div class="para">
+ The installation program installs and configures X automatically, unless the X11R7.1 release packages are not selected for installation. However, if there are any changes to the monitor, video card or other devices managed by the X server, X must be reconfigured.
+ </div><div class="para">
+ In some situations, reconfiguring the X server may require manually editing its configuration file, <code class="filename">/etc/X11/xorg.conf</code>. For information about the structure of this file, refer to <a class="xref" href="#s1-x-server-configuration" title="21.3. X Server Configuration Files">Section 21.3, “X Server Configuration Files”</a>.
+ </div></div><div class="section" title="21.2. Desktop Environments and Window Managers" id="s1-x-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-clients">21.2. Desktop Environments and Window Managers</h2></div></div></div><a id="id742519" class="indexterm"></a><div class="para">
+ Once an X server is running, X client applications can connect to it and create a GUI for the user. A range of GUIs are possible with Fedora, from the rudimentary <em class="firstterm">Tab Window Manager</em> to the highly developed and interactive <em class="firstterm">GNOME</em> desktop environment that most Fedora users are familiar with.
+ </div><div class="para">
+ To create the latter, more comprehensive GUI, two main classes of X client application must connect to the X server: a <em class="firstterm">desktop environment</em> and a <em class="firstterm">window manager</em>.
+ </div><div class="section" title="21.2.1. Desktop Environments" id="s2-x-clients-desktop"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-clients-desktop">21.2.1. Desktop Environments</h3></div></div></div><a id="id742567" class="indexterm"></a><a id="id731608" class="indexterm"></a><a id="id731622" class="indexterm"></a><a id="id731636" class="indexterm"></a><a id="id731649" class="indexterm"></a><a id="id731667" class="indexterm"></a><div class="para">
+ A desktop environment integrates various X clients to create a common graphical user environment and development platform.
+ </div><div class="para">
+ Desktop environments have advanced features allowing X clients and other running processes to communicate with one another, while also allowing all applications written to work in that environment to perform advanced tasks, such as drag and drop operations.
+ </div><div class="para">
+ Fedora provides two desktop environments:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>GNOME</em></span> — The default desktop environment for Fedora based on the GTK+ 2 graphical toolkit.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em> <em class="firstterm">KDE</em> </em></span> — An alternative desktop environment based on the Qt 4 graphical toolkit.
+ </div></li></ul></div><div class="para">
+ Both GNOME and KDE have advanced productivity applications, such as word processors, spreadsheets, and Web browsers; both also provide tools to customize the look and feel of the GUI. Additionally, if both the GTK+ 2 and the Qt libraries are present, KDE applications can run in GNOME and vice-versa.
+ </div></div><div class="section" title="21.2.2. Window Managers" id="s2-x-clients-winmanagers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-clients-winmanagers">21.2.2. Window Managers</h3></div></div></div><a id="id788880" class="indexterm"></a><a id="id788894" class="indexterm"></a><a id="id788911" class="indexterm"></a><a id="id788933" class="indexterm"></a><a id="id1879155" class="indexterm"></a><a id="id1879177" class="indexterm"></a><a id="id1879199" class="indexterm"></a><a id="id1879216" class="indexterm"></a><a id="id956678" class="indexterm"></a><a id="id956696" class="indexterm"></a><div class="para">
+ <em class="firstterm">Window managers</em> are X client programs which are either part of a desktop environment or, in some cases, stand-alone. Their primary purpose is to control the way graphical windows are positioned, resized, or moved. Window managers also control title bars, window focus behavior, and user-specified key and mouse button bindings.
+ </div><div class="para">
+ Four window managers are included with Fedora:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">kwin</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">KWin</em> window manager is the default window manager for KDE. It is an efficient window manager which supports custom themes.
+ </div></dd><dt><span class="term"> <code class="command">metacity</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Metacity</em> window manager is the default window manager for GNOME. It is a simple and efficient window manager which also supports custom themes. To run this window manager, you need to install the <code class="filename">metacity</code> package.
+ </div></dd><dt><span class="term"> <code class="command">mwm</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Motif Window Manager</em> (<code class="command">mwm</code>) is a basic, stand-alone window manager. Since it is designed to be a stand-alone window manager, it should not be used in conjunction with GNOME or KDE. To run this window manager, you need to install the <code class="filename">openmotif</code> package.
+ </div></dd><dt><span class="term"> <code class="command">twm</code> </span></dt><dd><div class="para">
+ The minimalist <em class="firstterm">Tab Window Manager</em> (<code class="command">twm</code>, which provides the most basic tool set of any of the window managers, can be used either as a stand-alone or with a desktop environment. It is installed as part of the X11R7.1 release.
+ </div></dd></dl></div><div class="para">
+ To run any of the aforementioned window managers, you will first need to boot into Runlevel 3. For instructions on how to do this, refer to <a class="xref" href="#s1-services-runlevels" title="6.1. Configuring the Default Runlevel">Section 6.1, “Configuring the Default Runlevel”</a>.
+ </div><div class="para">
+ Once you are logged in to Runlevel 3, you will be presented with a terminal prompt, not a graphical environment. To start a window manager, type <code class="command">xinit -e <em class="replaceable"><code><path-to-window-manager></code></em> </code> at the prompt.
+ </div><div class="para">
+ <code class="command"> <em class="replaceable"><code><path-to-window-manager></code></em> </code> is the location of the window manager binary file. The binary file can be located by typing <code class="command">which <em class="replaceable"><code>window-manager-name</code></em> </code>, where <code class="command"><em class="replaceable"><code>window-manager-name</code></em> </code> is the name of the window manager you want to run.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">~]# <code class="command">which twm</code>
+/usr/bin/twm
+~]# <code class="command">xinit -e /usr/bin/twm</code></pre><div class="para">
+ The first command above returns the absolute path to the <code class="command">twm</code> window manager, the second command starts <code class="command">twm</code>.
+ </div><div class="para">
+ To exit a window manager, close the last window or press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Backspace</strong></span>. Once you have exited the window manager, you can log back into Runlevel 5 by typing <code class="command">startx</code> at the prompt.
+ </div></div></div><div class="section" title="21.3. X Server Configuration Files" id="s1-x-server-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-server-configuration">21.3. X Server Configuration Files</h2></div></div></div><a id="id819266" class="indexterm"></a><a id="id819288" class="indexterm"></a><div class="para">
+ The X server is a single binary executable (<code class="filename">/usr/bin/Xorg</code>). Associated configuration files are stored in the <code class="filename">/etc/X11/</code> directory (as is a symbolic link — X — which points to <code class="filename">/usr/bin/Xorg</code>). The configuration file for the X server is <code class="filename">/etc/X11/xorg.conf</code>.
+ </div><div class="para">
+ The directory <code class="filename">/usr/lib/xorg/modules/</code> contains X server modules that can be loaded dynamically at runtime. By default, only some modules in <code class="filename">/usr/lib/xorg/modules/</code> are automatically loaded by the X server.
+ </div><div class="para">
+ To load optional modules, they must be specified in the X server configuration file, <code class="filename">/etc/X11/xorg.conf</code>. For more information about loading modules, refer to <a class="xref" href="#s3-x-server-config-xorg.conf-modules" title="21.3.1.5. Module">Section 21.3.1.5, “ <code class="command">Module</code> ”</a>.
+ </div><div class="para">
+ When Fedora 13 is installed, the configuration files for X are created using information gathered about the system hardware during the installation process.
+ </div><div class="section" title="21.3.1. xorg.conf" id="s2-x-server-config-xorg.conf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-server-config-xorg.conf">21.3.1. <code class="filename">xorg.conf</code> </h3></div></div></div><a id="id944962" class="indexterm"></a><a id="id944984" class="indexterm"></a><a id="id804238" class="indexterm"></a><div class="para">
+ While there is rarely a need to manually edit the <code class="filename">/etc/X11/xorg.conf</code> file, it is useful to understand the various sections and optional parameters available, especially when troubleshooting.
+ </div><div class="section" title="21.3.1.1. The Structure" id="s3-x-server-config-xorg.conf-struct"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-struct">21.3.1.1. The Structure</h4></div></div></div><a id="id804276" class="indexterm"></a><a id="id2392400" class="indexterm"></a><a id="id2392426" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/X11/xorg.conf</code> file is comprised of many different sections which address specific aspects of the system hardware.
+ </div><div class="para">
+ Each section begins with a <code class="command">Section "<em class="replaceable"><code><section-name></code></em>"</code> line (where <em class="replaceable"><code><section-name></code></em> is the title for the section) and ends with an <code class="command">EndSection</code> line. Each section contains lines that include option names and one or more option values. These are sometimes enclosed in double quotes (<code class="command">"</code>).
+ </div><div class="para">
+ Lines beginning with a hash mark (<code class="command">#</code>) are not read by the X server and are used for human-readable comments.
+ </div><div class="para">
+ Some options within the <code class="filename">/etc/X11/xorg.conf</code> file accept a boolean switch which turns the feature on or off. Acceptable boolean values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">1</code>, <code class="command">on</code>, <code class="command">true</code>, or <code class="command">yes</code> — Turns the option on.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">0</code>, <code class="command">off</code>, <code class="command">false</code>, or <code class="command">no</code> — Turns the option off.
+ </div></li></ul></div><div class="para">
+ The following are some of the more important sections in the order in which they appear in a typical <code class="filename">/etc/X11/xorg.conf</code> file. More detailed information about the X server configuration file can be found in the <code class="filename">xorg.conf</code> man page.
+ </div></div><div class="section" title="21.3.1.2. ServerFlags" id="s3-x-server-config-xorg.conf-serverf"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-serverf">21.3.1.2. <code class="command">ServerFlags</code> </h4></div></div></div><a id="id1980898" class="indexterm"></a><div class="para">
+ The optional <code class="command">ServerFlags</code> section contains miscellaneous global X server settings. Any settings in this section may be overridden by options placed in the <code class="command">ServerLayout</code> section (refer to <a class="xref" href="#s3-x-server-config-xorg.conf-serverl" title="21.3.1.3. ServerLayout">Section 21.3.1.3, “ <code class="command">ServerLayout</code> ”</a> for details).
+ </div><div class="para">
+ Each entry within the <code class="command">ServerFlags</code> section is on its own line and begins with the term <code class="command">Option</code> followed by an option enclosed in double quotation marks (<code class="command">"</code>).
+ </div><div class="para">
+ The following is a sample <code class="command">ServerFlags</code> section:
+ </div><pre class="screen">Section "ServerFlags"
+ Option "DontZap" "true"
+EndSection</pre><div class="para">
+ The following lists some of the most useful options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">"DontZap" "<em class="replaceable"><code><boolean></code></em>"</code> — When the value of <em class="replaceable"><code><boolean></code></em> is set to true, this setting prevents the use of the <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Backspace</strong></span> key combination to immediately terminate the X server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">"DontZoom" "<em class="replaceable"><code><boolean></code></em>"</code> — When the value of <em class="replaceable"><code><boolean></code></em> is set to true, this setting prevents cycling through configured video resolutions using the <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Keypad-Plus</strong></span> and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Keypad-Minus</strong></span> key combinations.
+ </div></li></ul></div></div><div class="section" title="21.3.1.3. ServerLayout" id="s3-x-server-config-xorg.conf-serverl"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-serverl">21.3.1.3. <code class="command">ServerLayout</code> </h4></div></div></div><a id="id833656" class="indexterm"></a><div class="para">
+ The <code class="command">ServerLayout</code> section binds together the input and output devices controlled by the X server. At a minimum, this section must specify one output device and one input device. By default, a monitor (output device) and keyboard (input device) are specified.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">ServerLayout</code> section:
+ </div><pre class="screen">Section "ServerLayout"
+ Identifier "Default Layout"
+ Screen 0 "Screen0" 0 0
+ InputDevice "Mouse0" "CorePointer"
+ InputDevice "Keyboard0" "CoreKeyboard"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="command">ServerLayout</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Identifier</code> — Specifies a unique name for this <code class="command">ServerLayout</code> section.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Screen</code> — Specifies the name of a <code class="command">Screen</code> section to be used with the X server. More than one <code class="command">Screen</code> option may be present.
+ </div><div class="para">
+ The following is an example of a typical <code class="command">Screen</code> entry:
+ </div><pre class="screen">Screen 0 "Screen0" 0 0</pre><div class="para">
+ The first number in this example <code class="command">Screen</code> entry (<code class="command">0</code>) indicates that the first monitor connector or <em class="firstterm">head</em> on the video card uses the configuration specified in the <code class="command">Screen</code> section with the identifier <code class="command">"Screen0"</code>.
+ </div><div class="para">
+ An example of a <code class="command">Screen</code> section with the identifier <code class="command">"Screen0"</code> can be found in <a class="xref" href="#s3-x-server-config-xorg.conf-screen" title="21.3.1.9. Screen">Section 21.3.1.9, “ <code class="command">Screen</code> ”</a>.
+ </div><div class="para">
+ If the video card has more than one head, another <code class="command">Screen</code> entry with a different number and a different <code class="command">Screen</code> section identifier is necessary .
+ </div><div class="para">
+ The numbers to the right of <code class="command">"Screen0"</code> give the absolute X and Y coordinates for the upper-left corner of the screen (<code class="command">0 0</code> by default).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">InputDevice</code> — Specifies the name of an <code class="command">InputDevice</code> section to be used with the X server.
+ </div><div class="para">
+ It is advisable that there be at least two <code class="command">InputDevice</code> entries: one for the default mouse and one for the default keyboard. The options <code class="command">CorePointer</code> and <code class="command">CoreKeyboard</code> indicate that these are the primary mouse and keyboard.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Option "<em class="replaceable"><code><option-name></code></em>"</code> — An optional entry which specifies extra parameters for the section. Any options listed here override those listed in the <code class="command">ServerFlags</code> section.
+ </div><div class="para">
+ Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf</code> man page.
+ </div></li></ul></div><div class="para">
+ It is possible to put more than one <code class="command">ServerLayout</code> section in the <code class="filename">/etc/X11/xorg.conf</code> file. By default, the server only reads the first one it encounters, however.
+ </div><div class="para">
+ If there is an alternative <code class="command">ServerLayout</code> section, it can be specified as a command line argument when starting an X session.
+ </div></div><div class="section" title="21.3.1.4. Files" id="s3-x-server-config-xorg.conf-files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-files">21.3.1.4. <code class="command">Files</code> </h4></div></div></div><a id="id569370" class="indexterm"></a><div class="para">
+ The <code class="command">Files</code> section sets paths for services vital to the X server, such as the font path. This is an optional section, these paths are normally detected automatically. This section may be used to override any automatically detected defaults.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">Files</code> section:
+ </div><pre class="screen">Section "Files"
+ RgbPath "/usr/share/X11/rgb.txt"
+ FontPath "unix/:7100"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="command">Files</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">RgbPath</code> — Specifies the location of the RGB color database. This database defines all valid color names in X and ties them to specific RGB values.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">FontPath</code> — Specifies where the X server must connect to obtain fonts from the <code class="command">xfs</code> font server.
+ </div><div class="para">
+ By default, the <code class="command">FontPath</code> is <code class="command">unix/:7100</code>. This tells the X server to obtain font information using UNIX-domain sockets for inter-process communication (IPC) on port 7100.
+ </div><div class="para">
+ Refer to <a class="xref" href="#s1-x-fonts" title="21.4. Fonts">Section 21.4, “Fonts”</a> for more information concerning X and fonts.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ModulePath</code> — An optional parameter which specifies alternate directories which store X server modules.
+ </div></li></ul></div></div><div class="section" title="21.3.1.5. Module" id="s3-x-server-config-xorg.conf-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-modules">21.3.1.5. <code class="command">Module</code> </h4></div></div></div><a id="id955822" class="indexterm"></a><div class="para">
+ By default, the X server automatically loads the following modules from the <code class="filename">/usr/lib/xorg/modules/</code> directory:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">extmod</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dbe</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">glx</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">freetype</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">type1</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">record</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dri</code>
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The default directory for loading these modules can be changed by specifying a different directory with the optional <code class="command">ModulePath</code> parameter in the <code class="command">Files</code> section. Refer to <a class="xref" href="#s3-x-server-config-xorg.conf-files" title="21.3.1.4. Files">Section 21.3.1.4, “ <code class="command">Files</code> ”</a> for more information on this section.
+ </div><div class="para">
+ Adding a <code class="command">Module</code> section to <code class="filename">/etc/X11/xorg.conf</code> instructs the X server to load the modules listed in this section <span class="emphasis"><em>instead</em></span> of the default modules.
+ </div><div class="para">
+ For example, the following typical <code class="command">Module</code> section:
+ </div><pre class="screen">Section "Module"
+ Load "fbdevhw"
+EndSection</pre><div class="para">
+ instructs the X server to load the <code class="filename">fbdevhw</code> instead of the default modules.
+ </div><div class="para">
+ As such, if you add a <code class="command">Module</code> section to <code class="filename">/etc/X11/xorg.conf</code>, you will need to specify any default modules you want to load as well as any extra modules.
+ </div></div><div class="section" title="21.3.1.6. InputDevice" id="s3-x-server-config-xorg.conf-inputd"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-inputd">21.3.1.6. <code class="command">InputDevice</code> </h4></div></div></div><a id="id1939153" class="indexterm"></a><div class="para">
+ Each <code class="command">InputDevice</code> section configures one input device for the X server. Systems typically have at least one <code class="command">InputDevice</code> section for the keyboard. It is perfectly normal to have no entry for a mouse, as most mouse settings are automatically detected.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">InputDevice</code> section for a keyboard:
+ </div><pre class="screen">Section "InputDevice"
+ Identifier "Keyboard0"
+ Driver "kbd"
+ Option "XkbModel" "pc105"
+ Option "XkbLayout" "us"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="command">InputDevice</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Identifier</code> — Specifies a unique name for this <code class="command">InputDevice</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Driver</code> — Specifies the name of the device driver X must load for the device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Option</code> — Specifies necessary options pertaining to the device.
+ </div><div class="para">
+ A mouse may also be specified to override any autodetected defaults for the device. The following options are typically included when adding a mouse in the <code class="filename">xorg.conf</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Protocol</code> — Specifies the protocol used by the mouse, such as <code class="command">IMPS/2</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Device</code> — Specifies the location of the physical device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Emulate3Buttons</code> — Specifies whether to allow a two-button mouse to act like a three-button mouse when both mouse buttons are pressed simultaneously.
+ </div></li></ul></div><div class="para">
+ Consult the <code class="filename">xorg.conf</code> man page for a list of valid options for this section.
+ </div></li></ul></div></div><div class="section" title="21.3.1.7. Monitor" id="s3-x-server-config-xorg.conf-monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-monitor">21.3.1.7. <code class="command">Monitor</code> </h4></div></div></div><a id="id1529704" class="indexterm"></a><div class="para">
+ Each <code class="command">Monitor</code> section configures one type of monitor used by the system. This is an optional entry as well, as most monitors are now automatically detected.
+ </div><div class="para">
+ This example illustrates a typical <code class="command">Monitor</code> section for a monitor:
+ </div><pre class="screen">Section "Monitor"
+ Identifier "Monitor0"
+ VendorName "Monitor Vendor"
+ ModelName "DDC Probed Monitor - ViewSonic G773-2"
+ DisplaySize 320 240
+ HorizSync 30.0 - 70.0
+ VertRefresh 50.0 - 180.0
+EndSection</pre><div class="warning"><h2>Warning</h2><div class="para">
+ Be careful when manually editing values in the <code class="command">Monitor</code> section of <code class="filename">/etc/X11/xorg.conf</code>. Inappropriate values can damage or destroy a monitor. Consult the monitor's documentation for a listing of safe operating parameters.
+ </div></div><div class="para">
+ The following are commonly entries used in the <code class="command">Monitor</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Identifier</code> — Specifies a unique name for this <code class="command">Monitor</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">VendorName</code> — An optional parameter which specifies the vendor of the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ModelName</code> — An optional parameter which specifies the monitor's model name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">DisplaySize</code> — An optional parameter which specifies, in millimeters, the physical size of the monitor's picture area.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">HorizSync</code> — Specifies the range of horizontal sync frequencies compatible with the monitor in kHz. These values help the X server determine the validity of built-in or specified <code class="command">Modeline</code> entries for the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">VertRefresh</code> — Specifies the range of vertical refresh frequencies supported by the monitor, in kHz. These values help the X server determine the validity of built in or specified <code class="command">Modeline</code> entries for the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Modeline</code> — An optional parameter which specifies additional video modes for the monitor at particular resolutions, with certain horizontal sync and vertical refresh resolutions. Refer to the <code class="filename">xorg.conf</code> man page for a more detailed explanation of <code class="command">Modeline</code> entries.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Option "<em class="replaceable"><code><option-name></code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf</code> man page.
+ </div></li></ul></div></div><div class="section" title="21.3.1.8. Device" id="s3-x-server-config-xorg.conf-device"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-device">21.3.1.8. <code class="command">Device</code> </h4></div></div></div><a id="id2009301" class="indexterm"></a><div class="para">
+ Each <code class="command">Device</code> section configures one video card on the system. While one <code class="command">Device</code> section is the minimum, additional instances may occur for each video card installed on the machine.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">Device</code> section for a video card:
+ </div><pre class="screen">Section "Device"
+ Identifier "Videocard0"
+ Driver "mga"
+ VendorName "Videocard vendor"
+ BoardName "Matrox Millennium G200"
+ VideoRam 8192
+ Option "dpms"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="command">Device</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Identifier</code> — Specifies a unique name for this <code class="command">Device</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Driver</code> — Specifies which driver the X server must load to utilize the video card. A list of drivers can be found in <code class="filename">/usr/share/hwdata/videodrivers</code>, which is installed with the <code class="filename">hwdata</code> package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">VendorName</code> — An optional parameter which specifies the vendor of the video card.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">BoardName</code> — An optional parameter which specifies the name of the video card.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">VideoRam</code> — An optional parameter which specifies the amount of RAM available on the video card in kilobytes. This setting is only necessary for video cards the X server cannot probe to detect the amount of video RAM.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">BusID</code> — An entry which specifies the bus location of the video card. On systems with only one video card a <code class="command">BusID</code> entry is optional and may not even be present in the default <code class="filename">/etc/X11/xorg.conf</code> file. On systems with more than one video card, however, a <code class="command">BusID</code> entry must be present.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Screen</code> — An optional entry which specifies which monitor connector or head on the video card the <code class="command">Device</code> section configures. This option is only useful for video cards with multiple heads.
+ </div><div class="para">
+ If multiple monitors are connected to different heads on the same video card, separate <code class="command">Device</code> sections must exist and each of these sections must have a different <code class="command">Screen</code> value.
+ </div><div class="para">
+ Values for the <code class="command">Screen</code> entry must be an integer. The first head on the video card has a value of <code class="command">0</code>. The value for each additional head increments this value by one.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Option "<em class="replaceable"><code><option-name></code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf</code> man page.
+ </div><div class="para">
+ One of the more common options is <code class="command">"dpms"</code> (for Display Power Management Signaling, a VESA standard), which activates the Service Star energy compliance setting for the monitor.
+ </div></li></ul></div></div><div class="section" title="21.3.1.9. Screen" id="s3-x-server-config-xorg.conf-screen"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-screen">21.3.1.9. <code class="command">Screen</code> </h4></div></div></div><a id="id1193699" class="indexterm"></a><div class="para">
+ Each <code class="command">Screen</code> section binds one video card (or video card head) to one monitor by referencing the <code class="command">Device</code> section and the <code class="command">Monitor</code> section for each. While one <code class="command">Screen</code> section is the minimum, additional instances may occur for each video card and monitor combination present on the machine.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">Screen</code> section:
+ </div><pre class="screen">Section "Screen"
+ Identifier "Screen0"
+ Device "Videocard0"
+ Monitor "Monitor0"
+ DefaultDepth 16
+
+ SubSection "Display"
+ Depth 24
+ Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
+ EndSubSection
+
+ SubSection "Display"
+ Depth 16
+ Modes "1152x864" "1024x768" "800x600" "640x480"
+ EndSubSection
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="command">Screen</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Identifier</code> — Specifies a unique name for this <code class="command">Screen</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Device</code> — Specifies the unique name of a <code class="command">Device</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Monitor</code> — Specifies the unique name of a <code class="command">Monitor</code> section. This is only required if a specific <code class="command">Monitor</code> section is defined in the <code class="filename">xorg.conf</code> file. Normally, monitors are automatically detected.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">DefaultDepth</code> — Specifies the default color depth in bits. In the previous example, <code class="command">16</code> (which provides thousands of colors) is the default. Only one <code class="command">DefaultDepth</code> is permitted, although this can be overridden with the Xorg command line option <code class="command">-depth <em class="replaceable"><code><n></code></em> </code>,where <code class="command"><em class="replaceable"><code><n></code></em> </code> is any additional depth specified.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SubSection "Display"</code> — Specifies the screen modes available at a particular color depth. The <code class="command">Screen</code> section can have multiple <code class="command">Display</code> subsections, which are entirely optional since screen modes are automatically detected.
+ </div><div class="para">
+ This subsection is normally used to override autodetected modes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Option "<em class="replaceable"><code><option-name></code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf</code> man page.
+ </div></li></ul></div></div><div class="section" title="21.3.1.10. DRI" id="s3-x-server-config-xorg.conf-dri"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-dri">21.3.1.10. <code class="command">DRI</code> </h4></div></div></div><a id="id945676" class="indexterm"></a><div class="para">
+ The optional <code class="command">DRI</code> section specifies parameters for the <em class="firstterm">Direct Rendering Infrastructure</em> (<em class="firstterm">DRI</em>). DRI is an interface which allows 3D software applications to take advantage of 3D hardware acceleration capabilities built into most modern video hardware. In addition, DRI can improve 2D performance via hardware acceleration, if supported by the video card driver.
+ </div><div class="para">
+ This section rarely appears, as the DRI Group and Mode are automatically initialized to default values. If a different Group or Mode is desired, then adding this section to the <code class="filename">xorg.conf</code> file will override those defaults.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">DRI</code> section:
+ </div><pre class="screen">Section "DRI"
+ Group 0
+ Mode 0666
+EndSection</pre><div class="para">
+ Since different video cards use DRI in different ways, do not add to this section without first referring to <a href="http://dri.sourceforge.net/">http://dri.sourceforge.net/</a>.
+ </div></div></div></div><div class="section" title="21.4. Fonts" id="s1-x-fonts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-fonts">21.4. Fonts</h2></div></div></div><a id="id652029" class="indexterm"></a><div class="para">
+ Fedora uses two subsystems to manage and display fonts under X: <em class="firstterm">Fontconfig</em> and <code class="command">xfs</code>.
+ </div><div class="para">
+ The newer Fontconfig font subsystem simplifies font management and provides advanced display features, such as anti-aliasing. This system is used automatically for applications programmed using the Qt 3 or GTK+ 2 graphical toolkit.
+ </div><div class="para">
+ For compatibility, Fedora includes the original font subsystem, called the core X font subsystem. This system, which is over 15 years old, is based around the <em class="firstterm">X Font Server</em> (<em class="firstterm">xfs</em>).
+ </div><div class="para">
+ This section discusses how to configure fonts for X using both systems.
+ </div><div class="section" title="21.4.1. Fontconfig" id="s2-x-fonts-fontconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-fonts-fontconfig">21.4.1. Fontconfig</h3></div></div></div><a id="id942431" class="indexterm"></a><a id="id964500" class="indexterm"></a><a id="id964518" class="indexterm"></a><a id="id964537" class="indexterm"></a><div class="para">
+ The Fontconfig font subsystem allows applications to directly access fonts on the system and use Xft or other rendering mechanisms to render Fontconfig fonts with advanced anti-aliasing. Graphical applications can use the Xft library with Fontconfig to draw text to the screen.
+ </div><div class="para">
+ Over time, the Fontconfig/Xft font subsystem replaces the core X font subsystem.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ The Fontconfig font subsystem does not yet work for <span class="application"><strong>OpenOffice.org</strong></span>, which uses its own font rendering technology.
+ </div></div><div class="para">
+ It is important to note that Fontconfig uses the <code class="filename">/etc/fonts/fonts.conf</code> configuration file, which should not be edited by hand.
+ </div><div class="note"><h2>Tip</h2><div class="para">
+ Due to the transition to the new font system, GTK+ 1.2 applications are not affected by any changes made via the <span class="application"><strong>Font Preferences</strong></span> dialog (accessed by selecting System (on the panel) > <span class="guimenuitem"><strong>Preferences</strong></span> > <span class="guimenuitem"><strong>Fonts</strong></span>). For these applications, a font can be configured by adding the following lines to the file <code class="filename">~/.gtkrc.mine</code>:
+ </div><pre class="screen">style "user-font" {
+ fontset = "<em class="replaceable"><code><font-specification></code></em>"
+}
+
+widget_class "*" style "user-font"</pre><div class="para">
+ Replace <em class="replaceable"><code><font-specification></code></em> with a font specification in the style used by traditional X applications, such as <code class="command">-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</code>. A full list of core fonts can be obtained by running <code class="command">xlsfonts</code> or created interactively using the <code class="command">xfontsel</code> command.
+ </div></div><div class="section" title="21.4.1.1. Adding Fonts to Fontconfig" id="s3-x-fonts-fontconfig-add"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-fonts-fontconfig-add">21.4.1.1. Adding Fonts to Fontconfig</h4></div></div></div><a id="id905414" class="indexterm"></a><div class="para">
+ Adding new fonts to the Fontconfig subsystem is a straightforward process.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ To add fonts system-wide, copy the new fonts into the <code class="filename">/usr/share/fonts/</code> directory. It is a good idea to create a new subdirectory, such as <code class="filename">local/</code> or similar, to help distinguish between user-installed and default fonts.
+ </div><div class="para">
+ To add fonts for an individual user, copy the new fonts into the <code class="filename">.fonts/</code> directory in the user's home directory.
+ </div></li><li class="listitem"><div class="para">
+ Use the <code class="command">fc-cache</code> command to update the font information cache, as in the following example:
+ </div><pre class="screen"><code class="command">fc-cache <em class="replaceable"><code><path-to-font-directory></code></em></code></pre><div class="para">
+ In this command, replace <em class="replaceable"><code><path-to-font-directory></code></em> with the directory containing the new fonts (either <code class="filename">/usr/share/fonts/local/</code> or <code class="filename">/home/<em class="replaceable"><code><user></code></em>/.fonts/</code>).
+ </div></li></ol></div><div class="note"><h2>Tip</h2><div class="para">
+ Individual users may also install fonts graphically, by typing <code class="filename">fonts:///</code> into the <span class="application"><strong>Nautilus</strong></span> address bar, and dragging the new font files there.
+ </div></div><div class="important"><h2>Important</h2><div class="para">
+ If the font file name ends with a <code class="filename">.gz</code> extension, it is compressed and cannot be used until uncompressed. To do this, use the <code class="command">gunzip</code> command or double-click the file and drag the font to a directory in <span class="application"><strong>Nautilus</strong></span>.
+ </div></div></div></div><div class="section" title="21.4.2. Core X Font System" id="s2-x-fonts-core"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-fonts-core">21.4.2. Core X Font System</h3></div></div></div><a id="id864260" class="indexterm"></a><a id="id864282" class="indexterm"></a><a id="id864301" class="indexterm"></a><div class="para">
+ For compatibility, Fedora provides the core X font subsystem, which uses the X Font Server (<code class="command">xfs</code>) to provide fonts to X client applications.
+ </div><div class="para">
+ The X server looks for a font server specified in the <code class="command">FontPath</code> directive within the <code class="command">Files</code> section of the <code class="filename">/etc/X11/xorg.conf</code> configuration file. Refer to <a class="xref" href="#s3-x-server-config-xorg.conf-files" title="21.3.1.4. Files">Section 21.3.1.4, “ <code class="command">Files</code> ”</a> for more information about the <code class="command">FontPath</code> entry.
+ </div><div class="para">
+ The X server connects to the <code class="command">xfs</code> server on a specified port to acquire font information. For this reason, the <code class="command">xfs</code> service must be running for X to start. For more about configuring services for a particular runlevel, refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a>.
+ </div><div class="section" title="21.4.2.1. xfs Configuration" id="s3-x-fonts-xfs-config"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-fonts-xfs-config">21.4.2.1. <code class="command">xfs</code> Configuration</h4></div></div></div><a id="id638578" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/rc.d/init.d/xfs</code> script starts the <code class="command">xfs</code> server. Several options can be configured within its configuration file, <code class="filename">/etc/X11/fs/config</code>.
+ </div><div class="para">
+ The following lists common options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">alternate-servers</code> — Specifies a list of alternate font servers to be used if this font server is not available. A comma must separate each font server in a list.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">catalogue</code> — Specifies an ordered list of font paths to use. A comma must separate each font path in a list.
+ </div><div class="para">
+ Use the string <code class="command">:unscaled</code> immediately after the font path to make the unscaled fonts in that path load first. Then specify the entire path again, so that other scaled fonts are also loaded.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">client-limit</code> — Specifies the maximum number of clients the font server services. The default is <code class="command">10</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">clone-self</code> — Allows the font server to clone a new version of itself when the <code class="command">client-limit</code> is hit. By default, this option is <code class="command">on</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">default-point-size</code> — Specifies the default point size for any font that does not specify this value. The value for this option is set in decipoints. The default of <code class="command">120</code> corresponds to a 12 point font.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">default-resolutions</code> — Specifies a list of resolutions supported by the X server. Each resolution in the list must be separated by a comma.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">deferglyphs</code> — Specifies whether to defer loading <em class="firstterm">glyphs</em> (the graphic used to visually represent a font). To disable this feature use <code class="command">none</code>, to enable this feature for all fonts use <code class="command">all</code>, or to turn this feature on only for 16-bit fonts use <code class="command">16</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">error-file</code> — Specifies the path and file name of a location where <code class="command">xfs</code> errors are logged.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no-listen</code> — Prevents <code class="command">xfs</code> from listening to particular protocols. By default, this option is set to <code class="command">tcp</code> to prevent <code class="command">xfs</code> from listening on TCP ports for security reasons.
+ </div><div class="note"><h2>Tip</h2><div class="para">
+ If <code class="command">xfs</code> is used to serve fonts over the network, remove this line.
+ </div></div></li><li class="listitem"><div class="para">
+ <code class="command">port</code> — Specifies the TCP port that <code class="command">xfs</code> listens on if <code class="command">no-listen</code> does not exist or is commented out.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">use-syslog</code> — Specifies whether to use the system error log.
+ </div></li></ul></div></div><div class="section" title="21.4.2.2. Adding Fonts to xfs" id="s2-x-fonts-xfs-add"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-x-fonts-xfs-add">21.4.2.2. Adding Fonts to <code class="command">xfs</code> </h4></div></div></div><a id="id615442" class="indexterm"></a><div class="para">
+ To add fonts to the core X font subsystem (<code class="command">xfs</code>), follow these steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ If it does not already exist, create a directory called <code class="filename">/usr/share/fonts/local/</code> using the following command as root:
+ </div><pre class="screen">~]# <code class="command">mkdir /usr/share/fonts/local/</code></pre><div class="para">
+ If creating the <code class="filename">/usr/share/fonts/local/</code> directory is necessary, it must be added to the <code class="command">xfs</code> path using the following command as root:
+ </div><pre class="screen">~]# <code class="command">chkfontpath --add /usr/share/fonts/local/</code></pre></li><li class="listitem"><div class="para">
+ Copy the new font file into the <code class="filename">/usr/share/fonts/local/</code> directory
+ </div></li><li class="listitem"><div class="para">
+ Update the font information by issuing the following command as root:
+ </div><pre class="screen">~]# <code class="command">ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</code></pre></li><li class="listitem"><div class="para">
+ Reload the <code class="command">xfs</code> font server configuration file by issuing the following command as root:
+ </div><pre class="screen">~]# <code class="command">service xfs reload</code></pre></li></ol></div></div></div></div><div class="section" title="21.5. Runlevels and X" id="s1-x-runlevels"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-runlevels">21.5. Runlevels and X</h2></div></div></div><a id="id683612" class="indexterm"></a><div class="para">
+ In most cases, the Fedora installer configures a machine to boot into a graphical login environment, known as <em class="firstterm">Runlevel 5</em>. It is possible, however, to boot into a text-only multi-user mode called <em class="firstterm">Runlevel 3</em> and begin an X session from there.
+ </div><div class="para">
+ For more information about runlevels, refer to <a class="xref" href="#s1-services-runlevels" title="6.1. Configuring the Default Runlevel">Section 6.1, “Configuring the Default Runlevel”</a>.
+ </div><div class="para">
+ The following subsections review how X starts up in both runlevel 3 and runlevel 5.
+ </div><div class="section" title="21.5.1. Runlevel 3" id="s2-x-runlevels-3"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-runlevels-3">21.5.1. Runlevel 3</h3></div></div></div><a id="id683668" class="indexterm"></a><a id="id702244" class="indexterm"></a><a id="id702263" class="indexterm"></a><a id="id702285" class="indexterm"></a><a id="id702304" class="indexterm"></a><a id="id727081" class="indexterm"></a><div class="para">
+ When in runlevel 3, the best way to start an X session is to log in and type <code class="command">startx</code>. The <code class="command">startx</code> command is a front-end to the <code class="command">xinit</code> command, which launches the X server (<code class="filename">Xorg</code>) and connects X client applications to it. Because the user is already logged into the system at runlevel 3, <code class="command">startx</code> does not launch a display manager or authenticate users. Refer to <a class="xref" href="#s2-x-runlevels-5" title="21.5.2. Runlevel 5">Section 21.5.2, “Runlevel 5”</a> for more information about display managers.
+ </div><div class="para">
+ When the <code class="command">startx</code> command is executed, it searches for the <code class="filename">.xinitrc</code> file in the user's home directory to define the desktop environment and possibly other X client applications to run. If no <code class="filename">.xinitrc</code> file is present, it uses the system default <code class="filename">/etc/X11/xinit/xinitrc</code> file instead.
+ </div><div class="para">
+ The default <code class="command">xinitrc</code> script then searches for user-defined files and default system files, including <code class="filename">.Xresources</code>, <code class="filename">.Xmodmap</code>, and <code class="filename">.Xkbmap</code> in the user's home directory, and <code class="filename">Xresources</code>, <code class="filename">Xmodmap</code>, and <code class="filename">Xkbmap</code> in the <code class="filename">/etc/X11/</code> directory. The <code class="filename">Xmodmap</code> and <code class="filename">Xkbmap</code> files, if they exist, are used by the <code class="command">xmodmap</code> utility to configure the keyboard. The <code class="filename">Xresources</code> file is read to assign specific preference values to applications.
+ </div><div class="para">
+ After setting these options, the <code class="command">xinitrc</code> script executes all scripts located in the <code class="filename">/etc/X11/xinit/xinitrc.d/</code> directory. One important script in this directory is <code class="filename">xinput.sh</code>, which configures settings such as the default language.
+ </div><div class="para">
+ Next, the <code class="command">xinitrc</code> script attempts to execute <code class="filename">.Xclients</code> in the user's home directory and turns to <code class="filename">/etc/X11/xinit/Xclients</code> if it cannot be found. The purpose of the <code class="filename">Xclients</code> file is to start the desktop environment or, possibly, just a basic window manager. The <code class="filename">.Xclients</code> script in the user's home directory starts the user-specified desktop environment in the <code class="filename">.Xclients-default</code> file. If <code class="filename">.Xclients</code> does not exist in the user's home directory, the standard <code class="filename">/etc/X11/xinit/Xclients</code> script attempts to start another desktop environment, trying GNOME first and then KDE followed by <code class="command">twm</code>.
+ </div><div class="para">
+ When in runlevel 3, the user is returned to a text mode user session after ending an X session.
+ </div></div><div class="section" title="21.5.2. Runlevel 5" id="s2-x-runlevels-5"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-runlevels-5">21.5.2. Runlevel 5</h3></div></div></div><a id="id1017568" class="indexterm"></a><a id="id1520816" class="indexterm"></a><a id="id1520834" class="indexterm"></a><a id="id1520852" class="indexterm"></a><a id="id1520875" class="indexterm"></a><a id="id1689399" class="indexterm"></a><a id="id1689421" class="indexterm"></a><a id="id1689440" class="indexterm"></a><a id="id759265" class="indexterm"></a><div class="para">
+ When the system boots into runlevel 5, a special X client application called a <em class="firstterm">display manager</em> is launched. A user must authenticate using the display manager before any desktop environment or window managers are launched.
+ </div><div class="para">
+ Depending on the desktop environments installed on the system, three different display managers are available to handle user authentication.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">GNOME</code> — The default display manager for Fedora, <code class="command">GNOME</code> allows the user to configure language settings, shutdown, restart or log in to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">KDE</code> — KDE's display manager which allows the user to shutdown, restart or log in to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">xdm</code> — A very basic display manager which only lets the user log in to the system.
+ </div></li></ul></div><div class="para">
+ When booting into runlevel 5, the <code class="command">prefdm</code> script determines the preferred display manager by referencing the <code class="filename">/etc/sysconfig/desktop</code> file. A list of options for this file is available in this file:
+ </div><pre class="screen"><code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code><version-number></code></em>/sysconfig.txt</code></pre><div class="para">
+ where <em class="replaceable"><code><version-number></code></em> is the version number of the <code class="filename">initscripts</code> package.
+ </div><div class="para">
+ Each of the display managers reference the <code class="filename">/etc/X11/xdm/Xsetup_0</code> file to set up the login screen. Once the user logs into the system, the <code class="filename">/etc/X11/xdm/GiveConsole</code> script runs to assign ownership of the console to the user. Then, the <code class="filename">/etc/X11/xdm/Xsession</code> script runs to accomplish many of the tasks normally performed by the <code class="command">xinitrc</code> script when starting X from runlevel 3, including setting system and user resources, as well as running the scripts in the <code class="filename">/etc/X11/xinit/xinitrc.d/</code> directory.
+ </div><div class="para">
+ Users can specify which desktop environment they want to utilize when they authenticate using the <code class="command">GNOME</code> or <code class="command">KDE</code> display managers by selecting it from the <span class="guimenu"><strong>Sessions</strong></span> menu item (accessed by selecting System (on the panel) > <span class="guimenuitem"><strong>Preferences</strong></span> > <span class="guimenuitem"><strong>More Preferences</strong></span> > <span class="guimenuitem"><strong>Sessions</strong></span>). If the desktop environment is not specified in the display manager, the <code class="filename">/etc/X11/xdm/Xsession</code> script checks the <code class="filename">.xsession</code> and <code class="filename">.Xclients</code> files in the user's home directory to decide which desktop environment to load. As a last resort, the <code class="filename">/etc/X11/xinit/Xclients</code> file is used to select a desktop environment or window manager to use in the
same way as runlevel 3.
+ </div><div class="para">
+ When the user finishes an X session on the default display (<code class="computeroutput">:0</code>) and logs out, the <code class="filename">/etc/X11/xdm/TakeConsole</code> script runs and reassigns ownership of the console to the root user. The original display manager, which continues running after the user logged in, takes control by spawning a new display manager. This restarts the X server, displays a new login window, and starts the entire process over again.
+ </div><div class="para">
+ The user is returned to the display manager after logging out of X from runlevel 5.
+ </div><div class="para">
+ For more information on how display managers control user authentication, refer to the <code class="filename">/usr/share/doc/gdm-<em class="replaceable"><code><version-number></code></em>/README</code> (where <em class="replaceable"><code><version-number></code></em> is the version number for the <code class="filename">gdm</code> package installed) and the <code class="command">xdm</code> man page.
+ </div></div></div><div class="section" title="21.6. Additional Resources" id="s1-x-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-additional-resources">21.6. Additional Resources</h2></div></div></div><a id="id913733" class="indexterm"></a><div class="para">
+ There is a large amount of detailed information available about the X server, the clients that connect to it, and the assorted desktop environments and window managers.
+ </div><div class="section" title="21.6.1. Installed Documentation" id="s2-x-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-installed-documentation">21.6.1. Installed Documentation</h3></div></div></div><a id="id913762" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/X11/doc/</code> — contains detailed documentation on the X Window System architecture, as well as how to get additional information about the Xorg project as a new user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man xorg.conf</code> — Contains information about the <code class="filename">xorg.conf</code> configuration files, including the meaning and syntax for the different sections within the files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man Xorg</code> — Describes the <code class="command">Xorg</code> display server.
+ </div></li></ul></div></div><div class="section" title="21.6.2. Useful Websites" id="s2-x-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-useful-websites">21.6.2. Useful Websites</h3></div></div></div><a id="id780658" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.X.org/">http://www.X.org/</a> — Home page of the X.Org Foundation, which produces the X11R7.1 release of the X Window System. The X11R7.1 release is bundled with Fedora to control the necessary hardware and provide a GUI environment.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://dri.sourceforge.net/">http://dri.sourceforge.net/</a> — Home page of the DRI (Direct Rendering Infrastructure) project. The DRI is the core hardware 3D acceleration component of X.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.gnome.org">http://www.gnome.org/</a> — Home of the GNOME project.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.kde.org">http://www.kde.org/</a> — Home of the KDE desktop environment.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 22. Users and Groups" id="ers_and_Groups" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 22. Users and Groups</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-users-configui">22.1. User and Group Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-users-user-new">22.1.1. Adding a New User</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-new">22.1.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="#s2-redhat-config-users-group-properties">22.1.3. Modifying Group Properties</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">22.2. User and Group Management Tools</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-cmd-line">22.2.1. Command Line Configuration</a></span></dt><dt><span class="se
ction"><a href="#s2-redhat-config-users-process">22.2.2. Explaining the Process</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-standard-users">22.3. Standard Users</a></span></dt><dt><span class="section"><a href="#s1-users-groups-standard-groups">22.4. Standard Groups</a></span></dt><dt><span class="section"><a href="#s1-users-groups-private-groups">22.5. User Private Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-rationale">22.5.1. Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-shadow-utilities">22.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="#s1-users-groups-additional-resources">22.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-documentation">22.7.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id702199" class="indexterm"></a><a id="id984621" class="indexterm"></
a><a id="id741549" class="indexterm"></a><a id="id891679" 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. For more information about ACLs, refer to chapter<em class="citetitle">ACLS</em>.
+ </div><div class="section" title="22.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">22.1. User and Group Configuration</h2></div></div></div><a id="id556704" class="indexterm"></a><a id="id550744" class="indexterm"></a><a id="id894347" class="indexterm"></a><a id="id894365" class="indexterm"></a><a id="id861904" class="indexterm"></a><a id="id861917" 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 22.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 22.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="id834456" class="indexterm"></a><a id="id834469" 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="22.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">22.1.1. Adding a New User</h3></div></div></div><a id="id1014939" 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 22.2. Creating a new user">Figure 22.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"><h2>Tip</h2><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 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 22.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 22.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>Modifying User Properties</h4><a id="id1776690" class="indexterm"></a><a id="id1776703" 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 22.3. User Properties">Figure 22.3, “User Properties”</a> appears.
+ </div><div class="figure" title="Figure 22.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 22.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="id1019191" class="indexterm"></a><a id="id697139" class="indexterm"></a><a id="id697152" class="indexterm"></a><a id="id697166" 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="22.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">22.1.2. Adding a New Group</h3></div></div></div><a id="id1032533" 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 22.4. New Group">Figure 22.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 22.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 22.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="22.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">22.1.3. Modifying Group Properties</h3></div></div></div><a id="id1200756" 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 22.5. Group Properties">Figure 22.5, “Group Properties”</a> appears.
+ </div><div class="figure" title="Figure 22.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 22.5. Group Properties</h6></div><br class="figure-break" /><a id="id899046" 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="22.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">22.2. User and Group Management Tools</h2></div></div></div><a id="id899085" class="indexterm"></a><a id="id622485" class="indexterm"></a><a id="id622508" class="indexterm"></a><a id="id622530" 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="22.1. User and Group Configuration">Section 22.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="22.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">22.2.1. Command Line Configuration</h3></div></div></div><a id="id684752" class="indexterm"></a><a id="id684767" class="indexterm"></a><a id="id751470" 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>Adding a User</h4><div class="para">
+ To add a user to the system:
+ </div><a id="id751497" 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="id908050" 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 22.1. useradd Command Line Options">Table 22.1, “ <code class="command">useradd</code> Command Line Options”</a>.
+ </div><div class="table" title="Table 22.1. useradd Command Line Options" id="table-useradd-options"><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><h6>Table 22.1. <code class="command">useradd</code> Command Line Options</h6></div><br class="table-break" /><h4>Adding a Group</h4><a id="id851831" class="indexterm"></a><a id="id851850" 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 22.2. groupadd Command Line Options">Table 22.2, “<code class="command">groupadd</code> Command Line Options”</a>.
+ </div><div class="table" title="Table 22.2. groupadd Command Line Options" id="table-groupadd-options"><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><h6>Table 22.2. <code class="command">groupadd</code> Command Line Options</h6></div><br class="table-break" /><h4>Password Aging</h4><a id="id982124" class="indexterm"></a><a id="id982138" class="indexterm"></a><a id="id1809200" class="indexterm"></a><a id="id1809210" class="indexterm"></a><a id="id1809230" 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 22.3. chage Command Line Options">Table 22.3, “<code class="command">chage</code> Command Line Options”</a>, followed by the username.
+ </div><div class="important"><h2>Important</h2><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="22.6. Shadow Passwords">Section 22.6, “Shadow Passwords”</a>.
+ </div></div><div class="table" title="Table 22.3. chage Command Line Options" id="table-chage-options"><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><h6>Table 22.3. <code class="command">chage</code> Command Line Options</h6></div><br class="table-break" /><div class="note"><h2>Tip</h2><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 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"><h2>Caution</h2><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></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="22.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">22.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"><h2>Note</h2><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></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="22.1.1. Adding a New User">Section 22.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="22.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">22.3. Standard Users</h2></div></div></div><a id="id623455" class="indexterm"></a><a id="id623470" class="indexterm"></a><div class="para">
+ <a class="xref" href="#tb-users-groups-group-use" title="Table 22.4. Standard Users">Table 22.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="22.4. Standard Groups">Section 22.4, “Standard Groups”</a> for a listing of standard groups.
+ </div><div class="table" title="Table 22.4. Standard Users" id="tb-users-groups-group-use"><div class="table-contents"><table summary="Standard Users" border="1"><colgroup><col width="29%" /><col width="10%" /><col width="10%" /><col width="30%" /><col width="21%" /></colgroup><thead><tr><th>
+ User
+ </th><th>
+ UID
+ </th><th>
+ GID
+ </th><th>
+ Home Directory
+ </th><th>
+ Shell
+ </th></tr></thead><tbody><tr><td>
+ root
+ </td><td>
+ 0
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/root</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ bin
+ </td><td>
+ 1
+ </td><td>
+ 1
+ </td><td>
+ <code class="filename">/bin</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ daemon
+ </td><td>
+ 2
+ </td><td>
+ 2
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ adm
+ </td><td>
+ 3
+ </td><td>
+ 4
+ </td><td>
+ <code class="filename">/var/adm</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ lp
+ </td><td>
+ 4
+ </td><td>
+ 7
+ </td><td>
+ <code class="filename">/var/spool/lpd</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ sync
+ </td><td>
+ 5
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/bin/sync</code>
+ </td></tr><tr><td>
+ shutdown
+ </td><td>
+ 6
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/sbin/shutdown</code>
+ </td></tr><tr><td>
+ halt
+ </td><td>
+ 7
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/sbin/halt</code>
+ </td></tr><tr><td>
+ mail
+ </td><td>
+ 8
+ </td><td>
+ 12
+ </td><td>
+ <code class="filename">/var/spool/mail</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ news
+ </td><td>
+ 9
+ </td><td>
+ 13
+ </td><td>
+ <code class="filename">/etc/news</code>
+ </td><td>
+ </td></tr><tr><td>
+ uucp
+ </td><td>
+ 10
+ </td><td>
+ 14
+ </td><td>
+ <code class="filename">/var/spool/uucp</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ operator
+ </td><td>
+ 11
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/root</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ games
+ </td><td>
+ 12
+ </td><td>
+ 100
+ </td><td>
+ <code class="filename">/usr/games</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ gopher
+ </td><td>
+ 13
+ </td><td>
+ 30
+ </td><td>
+ <code class="filename">/var/gopher</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ ftp
+ </td><td>
+ 14
+ </td><td>
+ 50
+ </td><td>
+ <code class="filename">/var/ftp</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ nobody
+ </td><td>
+ 99
+ </td><td>
+ 99
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ rpm
+ </td><td>
+ 37
+ </td><td>
+ 37
+ </td><td>
+ <code class="filename">/var/lib/rpm</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ vcsa
+ </td><td>
+ 69
+ </td><td>
+ 69
+ </td><td>
+ <code class="filename">/dev</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ dbus
+ </td><td>
+ 81
+ </td><td>
+ 81
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ ntp
+ </td><td>
+ 38
+ </td><td>
+ 38
+ </td><td>
+ <code class="filename">/etc/ntp</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ canna
+ </td><td>
+ 39
+ </td><td>
+ 39
+ </td><td>
+ <code class="filename">/var/lib/canna</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ nscd
+ </td><td>
+ 28
+ </td><td>
+ 28
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ rpc
+ </td><td>
+ 32
+ </td><td>
+ 32
+ </td><td>
+ <code class="filename">/var/lib/rpcbind</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ postfix
+ </td><td>
+ 89
+ </td><td>
+ 89
+ </td><td>
+ <code class="filename">/var/spool/postfix</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ mailman
+ </td><td>
+ 41
+ </td><td>
+ 41
+ </td><td>
+ <code class="filename">/var/mailman</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ named
+ </td><td>
+ 25
+ </td><td>
+ 25
+ </td><td>
+ <code class="filename">/var/named</code>
+ </td><td>
+ <code class="command">/bin/false</code>
+ </td></tr><tr><td>
+ amanda
+ </td><td>
+ 33
+ </td><td>
+ 6
+ </td><td>
+ <code class="filename">var/lib/amanda/</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ postgres
+ </td><td>
+ 26
+ </td><td>
+ 26
+ </td><td>
+ <code class="filename">/var/lib/pgsql</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ exim
+ </td><td>
+ 93
+ </td><td>
+ 93
+ </td><td>
+ <code class="filename">/var/spool/exim</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ sshd
+ </td><td>
+ 74
+ </td><td>
+ 74
+ </td><td>
+ <code class="filename">/var/empty/sshd</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ rpcuser
+ </td><td>
+ 29
+ </td><td>
+ 29
+ </td><td>
+ <code class="filename">/var/lib/nfs</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ nsfnobody
+ </td><td>
+ 65534
+ </td><td>
+ 65534
+ </td><td>
+ <code class="filename">/var/lib/nfs</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td></tr><tr><td>
+ pvm
+ </td><td>
+ 24
+ </td><td>
+ 24
+ </td><td>
+ <code class="filename">/usr/share/pvm3</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ apache
+ </td><td>
+ 48
+ </td><td>
+ 48
+ </td><td>
+ <code class="filename">/var/www</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ xfs
+ </td><td>
+ 43
+ </td><td>
+ 43
+ </td><td>
+ <code class="filename">/etc/X11/fs</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ gdm
+ </td><td>
+ 42
+ </td><td>
+ 42
+ </td><td>
+ <code class="filename">/var/gdm</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ htt
+ </td><td>
+ 100
+ </td><td>
+ 101
+ </td><td>
+ <code class="filename">/usr/lib/im</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ mysql
+ </td><td>
+ 27
+ </td><td>
+ 27
+ </td><td>
+ <code class="filename">/var/lib/mysql</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ webalizer
+ </td><td>
+ 67
+ </td><td>
+ 67
+ </td><td>
+ <code class="filename">/var/www/usage</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ mailnull
+ </td><td>
+ 47
+ </td><td>
+ 47
+ </td><td>
+ <code class="filename">/var/spool/mqueue</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ smmsp
+ </td><td>
+ 51
+ </td><td>
+ 51
+ </td><td>
+ <code class="filename">/var/spool/mqueue</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ squid
+ </td><td>
+ 23
+ </td><td>
+ 23
+ </td><td>
+ <code class="filename">/var/spool/squid</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td></tr><tr><td>
+ ldap
+ </td><td>
+ 55
+ </td><td>
+ 55
+ </td><td>
+ <code class="filename">/var/lib/ldap</code>
+ </td><td>
+ <code class="command">/bin/false</code>
+ </td></tr><tr><td>
+ netdump
+ </td><td>
+ 34
+ </td><td>
+ 34
+ </td><td>
+ <code class="filename">/var/crash</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ pcap
+ </td><td>
+ 77
+ </td><td>
+ 77
+ </td><td>
+ <code class="filename">/var/arpwatch</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ radiusd
+ </td><td>
+ 95
+ </td><td>
+ 95
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="command">/bin/false</code>
+ </td></tr><tr><td>
+ radvd
+ </td><td>
+ 75
+ </td><td>
+ 75
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ quagga
+ </td><td>
+ 92
+ </td><td>
+ 92
+ </td><td>
+ <code class="filename">/var/run/quagga</code>
+ </td><td>
+ <code class="command">/sbin/login</code>
+ </td></tr><tr><td>
+ wnn
+ </td><td>
+ 49
+ </td><td>
+ 49
+ </td><td>
+ <code class="filename">/var/lib/wnn</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ dovecot
+ </td><td>
+ 97
+ </td><td>
+ 97
+ </td><td>
+ <code class="filename">/usr/libexec/dovecot</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr></tbody></table></div><h6>Table 22.4. Standard Users</h6></div><br class="table-break" /></div><div class="section" title="22.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">22.4. Standard Groups</h2></div></div></div><a id="id676637" class="indexterm"></a><div class="para">
+ <a class="xref" href="#tb-users-groups-group-etc" title="Table 22.5. Standard Groups">Table 22.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 22.5. Standard Groups" id="tb-users-groups-group-etc"><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, exim
+ </td></tr><tr><td>
+ news
+ </td><td>
+ 13
+ </td><td>
+ news
+ </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>
+ 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>
+ nobody
+ </td><td>
+ 99
+ </td><td>
+ </td></tr><tr><td>
+ users
+ </td><td>
+ 100
+ </td><td>
+ </td></tr><tr><td>
+ rpm
+ </td><td>
+ 37
+ </td><td>
+ </td></tr><tr><td>
+ utmp
+ </td><td>
+ 22
+ </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>
+ dbus
+ </td><td>
+ 81
+ </td><td>
+ </td></tr><tr><td>
+ ntp
+ </td><td>
+ 38
+ </td><td>
+ </td></tr><tr><td>
+ canna
+ </td><td>
+ 39
+ </td><td>
+ </td></tr><tr><td>
+ nscd
+ </td><td>
+ 28
+ </td><td>
+ </td></tr><tr><td>
+ rpc
+ </td><td>
+ 32
+ </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>
+ mailman
+ </td><td>
+ 41
+ </td><td>
+ </td></tr><tr><td>
+ exim
+ </td><td>
+ 93
+ </td><td>
+ </td></tr><tr><td>
+ named
+ </td><td>
+ 25
+ </td><td>
+ </td></tr><tr><td>
+ postgres
+ </td><td>
+ 26
+ </td><td>
+ </td></tr><tr><td>
+ sshd
+ </td><td>
+ 74
+ </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>
+ pvm
+ </td><td>
+ 24
+ </td><td>
+ </td></tr><tr><td>
+ apache
+ </td><td>
+ 48
+ </td><td>
+ </td></tr><tr><td>
+ xfs
+ </td><td>
+ 43
+ </td><td>
+ </td></tr><tr><td>
+ gdm
+ </td><td>
+ 42
+ </td><td>
+ </td></tr><tr><td>
+ htt
+ </td><td>
+ 101
+ </td><td>
+ </td></tr><tr><td>
+ mysql
+ </td><td>
+ 27
+ </td><td>
+ </td></tr><tr><td>
+ webalizer
+ </td><td>
+ 67
+ </td><td>
+ </td></tr><tr><td>
+ mailnull
+ </td><td>
+ 47
+ </td><td>
+ </td></tr><tr><td>
+ smmsp
+ </td><td>
+ 51
+ </td><td>
+ </td></tr><tr><td>
+ squid
+ </td><td>
+ 23
+ </td><td>
+ </td></tr><tr><td>
+ ldap
+ </td><td>
+ 55
+ </td><td>
+ </td></tr><tr><td>
+ netdump
+ </td><td>
+ 34
+ </td><td>
+ </td></tr><tr><td>
+ pcap
+ </td><td>
+ 77
+ </td><td>
+ </td></tr><tr><td>
+ quaggavt
+ </td><td>
+ 102
+ </td><td>
+ </td></tr><tr><td>
+ quagga
+ </td><td>
+ 92
+ </td><td>
+ </td></tr><tr><td>
+ radvd
+ </td><td>
+ 75
+ </td><td>
+ </td></tr><tr><td>
+ slocate
+ </td><td>
+ 21
+ </td><td>
+ </td></tr><tr><td>
+ wnn
+ </td><td>
+ 49
+ </td><td>
+ </td></tr><tr><td>
+ dovecot
+ </td><td>
+ 97
+ </td><td>
+ </td></tr><tr><td>
+ radiusd
+ </td><td>
+ 95
+ </td><td>
+ </td></tr></tbody></table></div><h6>Table 22.5. Standard Groups</h6></div><br class="table-break" /></div><div class="section" title="22.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">22.5. User Private Groups</h2></div></div></div><a id="id1983930" class="indexterm"></a><a id="id1983944" class="indexterm"></a><a id="id1983957" class="indexterm"></a><a id="id1983979" 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="22.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">22.5.1. Group Directories</h3></div></div></div><a id="id727667" class="indexterm"></a><a id="id727681" 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="22.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">22.6. Shadow Passwords</h2></div></div></div><a id="id808798" class="indexterm"></a><a id="id896757" 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="22.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">22.7. Additional Resources</h2></div></div></div><a id="id607297" class="indexterm"></a><a id="id607311" 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="22.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">22.7.1. Installed Documentation</h3></div></div></div><a id="id607340" class="indexterm"></a><a id="id607358" 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><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><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 23. Printer Configuration" id="ch-Printer_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 23. Printer Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-printing-local-printer">23.1. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">23.2. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">23.3. Adding a Samba (SMB) Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-jetdirect-printer">23.4. Adding a JetDirect Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">23.5. Selecting the Printer Model and Finishing</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-printing-confirm">23.5.1. Confirming Printe
r Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-printing-test-page">23.6. Printing a Test Page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">23.7. Modifying Existing Printers</a></span></dt><dd><dl><dt><span class="section"><a href="#id1520769">23.7.1. The <span class="guilabel"><strong>Settings</strong></span> Tab</a></span></dt><dt><span class="section"><a href="#id995216">23.7.2. The <span class="guilabel"><strong>Policies</strong></span> Tab</a></span></dt><dt><span class="section"><a href="#id881428">23.7.3. The <span class="guilabel"><strong>Access Control</strong></span> Tab</a></span></dt><dt><span class="section"><a href="#id1712276">23.7.4. The <span class="guilabel"><strong>Printer</strong></span> and <span class="guilabel"><strong>Job Options</strong></span>Tab</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-printing-managing">23.8. Managing Print Jobs</a></span></dt><dt><span class="section">
<a href="#s1-printing-additional-resources">23.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-printing-installed-docs">23.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-printing-useful-websites">23.9.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id957601" class="indexterm"></a><a id="id732043" class="indexterm"></a><a id="id764472" class="indexterm"></a><a id="id580336" class="indexterm"></a><a id="id869926" class="indexterm"></a><div class="para">
+ <span class="application"><strong>Printer Configuration Tool</strong></span> allows users to configure a printer. This tool helps maintain the printer configuration file, print spool directories, print filters, and printer classes.
+ </div><a id="id865652" class="indexterm"></a><a id="id781747" class="indexterm"></a><div class="para">
+ Fedora 13 uses the Common Unix Printing System (<acronym class="acronym">CUPS</acronym>). If a system was upgraded from a previous Fedora version that used CUPS, the upgrade process preserves the configured queues.
+ </div><div class="para">
+ Using <span class="application"><strong>Printer Configuration Tool</strong></span> requires root privileges. To start the application, select System (on the panel) > <span class="guimenu"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>Printing</strong></span>, or type the command <code class="command">system-config-printer</code> at a shell prompt.
+ </div><div class="figure" title="Figure 23.1. Printer Configuration Tool" id="fig-printconf-main"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-main.png" alt="Printer Configuration Tool" /><div class="longdesc"><div class="para">
+ Main window
+ </div></div></div></div><h6>Figure 23.1. <span class="application">Printer Configuration Tool</span> </h6></div><br class="figure-break" /><div class="para">
+ The following types of print queues can be configured:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guimenuitem"><strong>AppSocket/HP JetDirect</strong></span> — a printer connected directly to the network through HP JetDirect or Appsocket interface instead of a computer.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guimenuitem"><strong>Internet Printing Protocol (IPP)</strong></span> — a printer that can be accessed over a TCP/IP network via the Internet Printing Protocol (for example, a printer attached to another Fedora system running CUPS on the network).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guimenuitem"><strong>LPD/LPR Host or Printer</strong></span> — a printer attached to a different UNIX system that can be accessed over a TCP/IP network (for example, a printer attached to another Fedora system running LPD on the network).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guimenuitem"><strong>Networked Windows (SMB)</strong></span> — a printer attached to a different system which is sharing a printer over an SMB network (for example, a printer attached to a Microsoft <span class="trademark">Windows</span>™ machine).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guimenuitem"><strong>Networked JetDirect</strong></span> — a printer connected directly to the network through HP JetDirect instead of a computer.
+ </div></li></ul></div><div class="important"><h2>Important</h2><a id="id956631" class="indexterm"></a><div class="para">
+ If you add a new print queue or modify an existing one, you must apply the changes for them to take effect.
+ </div></div><div class="para">
+ Clicking the <span class="guibutton"><strong>Apply</strong></span> button prompts the printer daemon to restart with the changes you have configured.
+ </div><div class="para">
+ Clicking the <span class="guibutton"><strong>Revert</strong></span> button discards unapplied changes.
+ </div><div class="section" title="23.1. Adding a Local Printer" id="s1-printing-local-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-local-printer">23.1. Adding a Local Printer</h2></div></div></div><a id="id1012808" class="indexterm"></a><a id="id1012822" class="indexterm"></a><div class="para">
+ To add a local printer, such as one attached through a parallel port or USB port on your computer, click the <span class="guibutton"><strong>New Printer</strong></span> button in the main <span class="application"><strong>Printer Configuration Tool</strong></span> window to display the window in <a class="xref" href="#fig-printconf-add" title="Figure 23.2. Adding a Printer">Figure 23.2, “ <span class="application">Adding a Printer</span> ”</a>.
+ </div><div class="figure" title="Figure 23.2. Adding a Printer" id="fig-printconf-add"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-add-printer.png" width="444" alt="Adding a Printer" /><div class="longdesc"><div class="para">
+ Adding a printer
+ </div></div></div></div><h6>Figure 23.2. <span class="application">Adding a Printer</span> </h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to proceed.
+ </div><div class="para">
+ Enter a unique name for the printer in the <span class="guilabel"><strong>Printer Name</strong></span> field. The printer name can contain letters, numbers, dashes (-), and underscores (_); it <span class="emphasis"><em>must not</em></span> contain any spaces.
+ </div><div class="para">
+ You can also use the <span class="guilabel"><strong>Description</strong></span> and <span class="guilabel"><strong>Location</strong></span> fields to further distinguish this printer from others that may be configured on your system. Both of these fields are optional, and may contain spaces.
+ </div><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to open the <span class="guilabel"><strong>New Printer</strong></span> dialog (refer to <a class="xref" href="#fig-printconf-local" title="Figure 23.3. Adding a Local Printer">Figure 23.3, “Adding a Local Printer”</a>). If the printer has been automatically detected, the printer model appears in <span class="guilabel"><strong>Select Connection</strong></span>. Select the printer model and click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div><div class="para">
+ If the device does not automatically appear, select the device to which the printer is connected (such as <span class="guilabel"><strong>LPT #1</strong></span> or <span class="guilabel"><strong>Serial Port #1</strong></span>) in <span class="guilabel"><strong>Select Connection</strong></span>.
+ </div><div class="figure" title="Figure 23.3. Adding a Local Printer" id="fig-printconf-local"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-local.png" width="444" alt="Adding a Local Printer" /><div class="longdesc"><div class="para">
+ Adding a local printer
+ </div></div></div></div><h6>Figure 23.3. Adding a Local Printer</h6></div><br class="figure-break" /><div class="para">
+ Next, select the printer type. Refer to <a class="xref" href="#s1-printing-select-model" title="23.5. Selecting the Printer Model and Finishing">Section 23.5, “Selecting the Printer Model and Finishing”</a> for details.
+ </div></div><div class="section" title="23.2. Adding an IPP Printer" id="s1-printing-ipp-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-ipp-printer">23.2. Adding an IPP Printer</h2></div></div></div><a id="id822013" class="indexterm"></a><a id="id822026" class="indexterm"></a><a id="id972822" class="indexterm"></a><a id="id972840" class="indexterm"></a><div class="para">
+ An IPP printer is a printer attached to a different system on the same TCP/IP network. The system this printer is attached to may either be running CUPS or simply configured to use IPP.
+ </div><div class="para">
+ If a firewall is enabled on the printer server, then the firewall should be configured to allow send / receive connections on the incoming UDP port 631. If a firewall is enabled on the client (the system sending the print request) then the firewall should be configured to allow accept and create connections through port 631.
+ </div><div class="para">
+ You can add a networked IPP printer by clicking the <span class="guibutton"><strong>New Printer</strong></span> button in the main <span class="application"><strong> Printer Configuration Tool</strong></span> window to display the window in <a class="xref" href="#fig-printconf-add" title="Figure 23.2. Adding a Printer">Figure 23.2, “ <span class="application">Adding a Printer</span> ”</a>. Enter the <span class="guilabel"><strong>Printer Name</strong></span> (printer names cannot contain spaces and may contain letters, numbers, dashes (-), and underscores (_)), <span class="guilabel"><strong>Description</strong></span>, and <span class="guilabel"><strong>Location</strong></span> to distinguish this printer from others that you may configure on your system. Click <span class="guibutton"><strong>Forward</strong></span> to proceed.
+ </div><div class="para">
+ In the window shown in <a class="xref" href="#fig-printconf-ipp" title="Figure 23.4. Adding an IPP Printer">Figure 23.4, “Adding an IPP Printer”</a>, enter the hostname of the IPP printer in the <span class="guilabel"><strong>Hostname</strong></span> field as well as a unique name for the printer in the <span class="guilabel"><strong>Printername</strong></span> field.
+ </div><div class="figure" title="Figure 23.4. Adding an IPP Printer" id="fig-printconf-ipp"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-ipp.png" width="444" alt="Adding an IPP Printer" /><div class="longdesc"><div class="para">
+ Networked IPP Printer
+ </div></div></div></div><h6>Figure 23.4. Adding an IPP Printer</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div><div class="para">
+ Next, select the printer type. Refer to <a class="xref" href="#s1-printing-select-model" title="23.5. Selecting the Printer Model and Finishing">Section 23.5, “Selecting the Printer Model and Finishing”</a> for details.
+ </div></div><div class="section" title="23.3. Adding a Samba (SMB) Printer" id="s1-printing-smb-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-smb-printer">23.3. Adding a Samba (SMB) Printer</h2></div></div></div><a id="id886217" class="indexterm"></a><a id="id886230" class="indexterm"></a><div class="para">
+ You can add a Samba (SMB) based printer share by clicking the <span class="guibutton"><strong>New Printer</strong></span> button in the main <span class="application"><strong> Printer Configuration Tool</strong></span> window to display the window in <a class="xref" href="#fig-printconf-add" title="Figure 23.2. Adding a Printer">Figure 23.2, “ <span class="application">Adding a Printer</span> ”</a>. Enter a unique name for the printer in the <span class="guilabel"><strong>Printer Name</strong></span> field. The printer name can contain letters, numbers, dashes (-), and underscores (_); it <span class="emphasis"><em>must not</em></span> contain any spaces.
+ </div><div class="para">
+ You can also use the <span class="guilabel"><strong>Description</strong></span> and <span class="guilabel"><strong>Location</strong></span> fields to further distinguish this printer from others that may be configured on your system. Both of these fields are optional, and may contain spaces.
+ </div><div class="figure" title="Figure 23.5. Adding a SMB Printer" id="fig-printconf-smb"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-smb.png" width="444" alt="Adding a SMB Printer" /><div class="longdesc"><div class="para">
+ SMB Printer
+ </div></div></div></div><h6>Figure 23.5. Adding a SMB Printer</h6></div><br class="figure-break" /><div class="para">
+ As shown in <a class="xref" href="#fig-printconf-smb" title="Figure 23.5. Adding a SMB Printer">Figure 23.5, “Adding a SMB Printer”</a>, available SMB shares are automatically detected and listed in the <span class="guilabel"><strong>Share</strong></span> column. Click the arrow (
+ <span class="inlinemediaobject"><img src="images/arrow.png" /></span>
+ ) beside a Workgroup to expand it. From the expanded list, select a printer.
+ </div><div class="para">
+ If the printer you are looking for does not appear in the list, enter the SMB address in the <span class="guilabel"><strong>smb://</strong></span> field. Use the format <em class="replaceable"><code>computer name/printer share</code></em>. In <a class="xref" href="#fig-printconf-smb" title="Figure 23.5. Adding a SMB Printer">Figure 23.5, “Adding a SMB Printer”</a>, the <em class="replaceable"><code>computer name</code></em> is <code class="command">dellbox</code>, while the <em class="replaceable"><code>printer share</code></em> is <code class="command">r2</code>.
+ </div><div class="para">
+ In the <span class="guilabel"><strong>Username</strong></span> field, enter the username to access the printer. This user must exist on the SMB system, and the user must have permission to access the printer. The default user name is typically <strong class="userinput"><code>guest</code></strong> for Windows servers, or <strong class="userinput"><code>nobody</code></strong> for Samba servers.
+ </div><div class="para">
+ Enter the <span class="guilabel"><strong>Password</strong></span> (if required) for the user specified in the <span class="guilabel"><strong>Username</strong></span> field.
+ </div><div class="para">
+ You can then test the connection by clicking <span class="guibutton"><strong>Verify</strong></span>. Upon successful verification, a dialog box appears confirming printer share accessibility.
+ </div><div class="para">
+ Next, select the printer type. Refer to <a class="xref" href="#s1-printing-select-model" title="23.5. Selecting the Printer Model and Finishing">Section 23.5, “Selecting the Printer Model and Finishing”</a> for details.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ Samba printer usernames and passwords are stored in the printer server as unencrypted files readable by root and lpd. Thus, other users that have root access to the printer server can view the username and password you use to access the Samba printer.
+ </div><div class="para">
+ As such, when you choose a username and password to access a Samba printer, it is advisable that you choose a password that is different from what you use to access your local Fedora system.
+ </div><div class="para">
+ If there are files shared on the Samba print server, it is recommended that they also use a password different from what is used by the print queue.
+ </div></div></div><div class="section" title="23.4. Adding a JetDirect Printer" id="s1-printing-jetdirect-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-jetdirect-printer">23.4. Adding a JetDirect Printer</h2></div></div></div><a id="id911604" class="indexterm"></a><a id="id911618" class="indexterm"></a><div class="para">
+ To add a JetDirect or AppSocket connected printer share, click the <span class="guibutton"><strong>New Printer</strong></span> button in the main <span class="application"><strong> Printer Configuration Tool</strong></span> window to display the window in <a class="xref" href="#fig-printconf-add" title="Figure 23.2. Adding a Printer">Figure 23.2, “ <span class="application">Adding a Printer</span> ”</a>. Enter a unique name for the printer in the <span class="guilabel"><strong>Printer Name</strong></span> field. The printer name can contain letters, numbers, dashes (-), and underscores (_); it <span class="emphasis"><em>must not</em></span> contain any spaces.
+ </div><div class="para">
+ You can also use the <span class="guilabel"><strong>Description</strong></span> and <span class="guilabel"><strong>Location</strong></span> fields to further distinguish this printer from others that may be configured on your system. Both of these fields are optional, and may contain spaces.
+ </div><div class="figure" title="Figure 23.6. Adding a JetDirect Printer" id="fig-printconf-jetdirect"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-jetdirect.png" width="444" alt="Adding a JetDirect Printer" /><div class="longdesc"><div class="para">
+ Adding a JetDirect Printer
+ </div></div></div></div><h6>Figure 23.6. Adding a JetDirect Printer</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div><div class="para">
+ Text fields for the following options appear:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hostname</strong></span> — The hostname or IP address of the JetDirect printer.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Port Number</strong></span> — The port on the JetDirect printer that is listening for print jobs. The default port is 9100.
+ </div></li></ul></div><div class="para">
+ Next, select the printer type. Refer to <a class="xref" href="#s1-printing-select-model" title="23.5. Selecting the Printer Model and Finishing">Section 23.5, “Selecting the Printer Model and Finishing”</a> for details.
+ </div></div><div class="section" title="23.5. Selecting the Printer Model and Finishing" id="s1-printing-select-model"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-select-model">23.5. Selecting the Printer Model and Finishing</h2></div></div></div><div class="para">
+ Once you have properly selected a printer queue type, you can choose either option:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Select a Printer from database - If you select this option, choose the make of your printer from the list of <span class="guilabel"><strong>Makes</strong></span>. If your printer make is not listed, choose <span class="guilabel"><strong>Generic</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ Provide PPD file - A PostScript Printer Description (PPD) file may also be provided with your printer. This file is normally provided by the manufacturer. If you are provided with a PPD file, you can choose this option and use the browser bar below the option description to select the PPD file.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref" href="#fig-printconf-select-model" title="Figure 23.7. Selecting a Printer Model">Figure 23.7, “Selecting a Printer Model”</a>.
+ </div><div class="figure" title="Figure 23.7. Selecting a Printer Model" id="fig-printconf-select-model"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-select-model.png" width="444" alt="Selecting a Printer Model" /><div class="longdesc"><div class="para">
+ Selecting a Printer Model
+ </div></div></div></div><h6>Figure 23.7. Selecting a Printer Model</h6></div><br class="figure-break" /><div class="para">
+ After choosing an option, click <span class="guibutton"><strong>Forward</strong></span> to continue. <a class="xref" href="#fig-printconf-select-model" title="Figure 23.7. Selecting a Printer Model">Figure 23.7, “Selecting a Printer Model”</a> appears. You now have to choose the corresponding model and driver for the printer.
+ </div><div class="para">
+ The recommended printed driver is automatically selected based on the printer model you chose. The print driver processes the data that you want to print into a format the printer can understand. Since a local printer is attached directly to your computer, you need a printer driver to process the data that is sent to the printer.
+ </div><div class="para">
+ If you have a PPD file for the device (usually provided by the manufacturer), you can select it by choosing <span class="guilabel"><strong>Provide PPD file</strong></span>. You can then browse the filesystem for the PPD file by clicking <span class="guibutton"><strong>Browse</strong></span>.
+ </div><div class="section" title="23.5.1. Confirming Printer Configuration" id="s2-printing-confirm"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-printing-confirm">23.5.1. Confirming Printer Configuration</h3></div></div></div><div class="para">
+ The last step is to confirm your printer configuration. Click <span class="guibutton"><strong>Apply</strong></span> to add the print queue if the settings are correct. Click <span class="guibutton"><strong>Back</strong></span> to modify the printer configuration.
+ </div><div class="para">
+ After applying the changes, print a test page to ensure the configuration is correct. Refer to <a class="xref" href="#s1-printing-test-page" title="23.6. Printing a Test Page">Section 23.6, “Printing a Test Page”</a> for details.
+ </div></div></div><div class="section" title="23.6. Printing a Test Page" id="s1-printing-test-page"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-test-page">23.6. Printing a Test Page</h2></div></div></div><a id="id676389" class="indexterm"></a><div class="para">
+ After you have configured your printer, you should print a test page to make sure the printer is functioning properly. To print a test page, select the printer that you want to try out from the printer list, then click <span class="guibutton"><strong>Print Test Page</strong></span> from the printer's <span class="guilabel"><strong>Settings</strong></span> tab.
+ </div><div class="para">
+ If you change the print driver or modify the driver options, you should print a test page to test the different configuration.
+ </div></div><div class="section" title="23.7. Modifying Existing Printers" id="s1-printing-edit"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-edit">23.7. Modifying Existing Printers</h2></div></div></div><a id="id676433" class="indexterm"></a><div class="para">
+ To delete an existing printer, select the printer and click the <span class="guibutton"><strong>Delete</strong></span> button on the toolbar. The printer is removed from the printer list once you confirm deletion of the printer configuration.
+ </div><a id="id1520742" class="indexterm"></a><div class="para">
+ To set the default printer, select the printer from the printer list and click the <span class="guibutton"><strong>Make Default Printer</strong></span> button in the <span class="guilabel"><strong>Settings</strong></span> tab.
+ </div><div class="section" title="23.7.1. The Settings Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1520769">23.7.1. The <span class="guilabel"><strong>Settings</strong></span> Tab</h3></div></div></div><div class="para">
+ To change printer driver configuration, click the corresponding name in the <span class="guilabel"><strong>Printer</strong></span> list and click the <span class="guilabel"><strong>Settings</strong></span> tab.
+ </div><div class="para">
+ You can modify printer settings such as make and model, make a printer the default, print a test page, change the device location (URI), and more.
+ </div><div class="figure" title="Figure 23.8. Settings Tab" id="fig-printconf-config1"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config1.png" width="444" alt="Settings Tab" /><div class="longdesc"><div class="para">
+ Settings Tab
+ </div></div></div></div><h6>Figure 23.8. Settings Tab</h6></div><br class="figure-break" /></div><div class="section" title="23.7.2. The Policies Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id995216">23.7.2. The <span class="guilabel"><strong>Policies</strong></span> Tab</h3></div></div></div><div class="para">
+ To change settings in print output, click the <span class="guilabel"><strong>Policies</strong></span> tab.
+ </div><div class="para">
+ For example, to create a <em class="firstterm">banner page</em> (a page that describes aspects of the print job such as the originating printer, the username from the which the job originated, and the security status of the document being printed) click the <span class="guilabel"><strong>Starting Banner </strong></span> or <span class="guilabel"><strong>Ending Banner</strong></span> drop-menu and choose the option that best describes the nature of the print jobs (such as <span class="guilabel"><strong>topsecret</strong></span>, <span class="guilabel"><strong>classified</strong></span>, or <span class="guilabel"><strong>confidential</strong></span>).
+ </div><div class="figure" title="Figure 23.9. Policies Tab" id="fig-printconf-config2"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config2.png" width="444" alt="Policies Tab" /><div class="longdesc"><div class="para">
+ Policies Tab
+ </div></div></div></div><h6>Figure 23.9. Policies Tab</h6></div><br class="figure-break" /><div class="para">
+ You can also configure the <span class="guilabel"><strong>Error Policy</strong></span> of the printer, by choosing an option from the drop-down menu. You can choose to abort the print job, retry, or stop it.
+ </div></div><div class="section" title="23.7.3. The Access Control Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id881428">23.7.3. The <span class="guilabel"><strong>Access Control</strong></span> Tab</h3></div></div></div><div class="para">
+ You can change user-level access to the configured printer by clicking the <span class="guilabel"><strong>Access Control</strong></span> tab.
+ </div><div class="para">
+ Add users using the text box and click the <span class="guibutton"><strong>Add</strong></span> button beside it. You can then choose to only allow use of the printer to that subset of users or deny use to those users.
+ </div><div class="figure" title="Figure 23.10. Access Control Tab" id="fig-printconf-config3"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config3.png" width="444" alt="Access Control Tab" /><div class="longdesc"><div class="para">
+ Access Control Tab
+ </div></div></div></div><h6>Figure 23.10. Access Control Tab</h6></div><br class="figure-break" /></div><div class="section" title="23.7.4. The Printer and Job OptionsTab"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1712276">23.7.4. The <span class="guilabel"><strong>Printer</strong></span> and <span class="guilabel"><strong>Job Options</strong></span>Tab</h3></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Printer Options</strong></span> tab contains various configuration options for the printer media and output.
+ </div><div class="figure" title="Figure 23.11. Printer Options Tab" id="fig-printconf-config4"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config4.png" width="444" alt="Printer Options Tab" /><div class="longdesc"><div class="para">
+ Printer Jobs Tab
+ </div></div></div></div><h6>Figure 23.11. Printer Options Tab</h6></div><br class="figure-break" /><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Page Size</strong></span> — Allows the paper size to be selected. The options include US Letter, US Legal, A3, and A4
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Media Source</strong></span> — set to <span class="guilabel"><strong>Automatic</strong></span> by default. Change this option to use paper from a different tray.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Media Type</strong></span> — Allows you to change paper type. Options include: Plain, thick, bond, and transparency.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Resolution</strong></span> — Configure the quality and detail of the printout. Default is 300 dots per inch (dpi).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Toner Saving</strong></span> — Choose whether the printer uses less toner to conserve resources.
+ </div></li></ul></div><div class="para">
+ You can also configure printer job options using the <span class="guilabel"><strong>Job Options</strong></span> tab. Use the drop-menu and choose the job options you wish to use, such as <span class="guilabel"><strong>Landscape</strong></span> modes (horizontal or vertical printout), <span class="guilabel"><strong>copies</strong></span>, or <span class="guilabel"><strong>scaling</strong></span> (increase or decrease the size of the printable area, which can be used to fit an oversize print area onto a smaller physical sheet of print medium).
+ </div></div></div><div class="section" title="23.8. Managing Print Jobs" id="s1-printing-managing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-managing">23.8. Managing Print Jobs</h2></div></div></div><a id="id642290" class="indexterm"></a><div class="para">
+ When you send a print job to the printer daemon, such as printing a text file from <span class="application"><strong>Emacs</strong></span> or printing an image from <span class="application"><strong>The GIMP</strong></span>, the print job is added to the print spool queue. The print spool queue is a list of print jobs that have been sent to the printer and information about each print request, such as the status of the request, the the job number, and more.
+ </div><div class="para">
+ During the printing process, the Printer Status icon appears in the <span class="application"><strong>Notification Area</strong></span> on the panel. To check the status of a print job, double click the Printer Status, which displays a window similar to <a class="xref" href="#fig-gnome-print-manager-list" title="Figure 23.12. GNOME Print Status">Figure 23.12, “GNOME Print Status”</a>.
+ </div><div class="figure" title="Figure 23.12. GNOME Print Status" id="fig-gnome-print-manager-list"><div class="figure-contents"><div class="mediaobject"><img src="images/gnome-print-queue.png" width="444" alt="GNOME Print Status" /><div class="longdesc"><div class="para">
+ GNOME Print Status
+ </div></div></div></div><h6>Figure 23.12. GNOME Print Status</h6></div><br class="figure-break" /><div class="para">
+ To cancel a specific print job listed in the <span class="application"><strong>GNOME Print Status</strong></span>, select it from the list and select <span class="guimenu"><strong>Edit</strong></span> > <span class="guimenuitem"><strong>Cancel Documents</strong></span> from the pulldown menu.
+ </div><a id="id1188831" class="indexterm"></a><div class="para">
+ To view the list of print jobs in the print spool from a shell prompt, type the command <code class="command">lpq</code>. The last few lines look similar to the following:
+ </div><div class="example" title="Example 23.1. Example of lpq output" id="lpq-example"><div class="example-contents"><pre class="screen">
+Rank Owner/ID Class Job Files Size Time
+active user at localhost+902 A 902 sample.txt 2050 01:20:46
+</pre></div><h6>Example 23.1. Example of <code class="command">lpq</code> output</h6></div><br class="example-break" /><a id="id669206" class="indexterm"></a><div class="para">
+ If you want to cancel a print job, find the job number of the request with the command <code class="command">lpq</code> and then use the command <code class="command">lprm <em class="replaceable"><code>job number</code></em> </code>. For example, <code class="command">lprm 902</code> would cancel the print job in <a class="xref" href="#lpq-example" title="Example 23.1. Example of lpq output">Example 23.1, “Example of <code class="command">lpq</code> output”</a>. You must have proper permissions to cancel a print job. You can not cancel print jobs that were started by other users unless you are logged in as root on the machine to which the printer is attached.
+ </div><a id="id669248" class="indexterm"></a><a id="id669262" class="indexterm"></a><div class="para">
+ You can also print a file directly from a shell prompt. For example, the command <code class="command">lpr sample.txt</code> prints the text file <code class="filename">sample.txt</code>. The print filter determines what type of file it is and converts it into a format the printer can understand.
+ </div></div><div class="section" title="23.9. Additional Resources" id="s1-printing-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-additional-resources">23.9. Additional Resources</h2></div></div></div><div class="para">
+ To learn more about printing on Fedora, refer to the following resources.
+ </div><div class="section" title="23.9.1. Installed Documentation" id="s2-printing-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-printing-installed-docs">23.9.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">map lpr</code> — The manual page for the <code class="command">lpr</code> command that allows you to print files from the command line.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man lprm</code> — The manual page for the command line utility to remove print jobs from the print queue.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man mpage</code> — The manual page for the command line utility to print multiple pages on one sheet of paper.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man cupsd</code> — The manual page for the CUPS printer daemon.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man cupsd.conf</code> — The manual page for the CUPS printer daemon configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man classes.conf</code> — The manual page for the class configuration file for CUPS.
+ </div></li></ul></div></div><div class="section" title="23.9.2. Useful Websites" id="s2-printing-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-printing-useful-websites">23.9.2. Useful Websites</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.linuxprinting.org">http://www.linuxprinting.org</a> — <em class="citetitle">GNU/Linux Printing</em> contains a large amount of information about printing in Linux.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.cups.org/">http://www.cups.org/</a> — Documentation, FAQs, and newsgroups about CUPS.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 24. Automated Tasks" id="ch-Automated_Tasks" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 24. Automated Tasks</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-autotasks-cron">24.1. Cron</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-cron-configuring">24.1.1. Configuring Cron Tasks</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">24.1.2. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-service">24.1.3. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-at-batch">24.2. At and Batch</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-at-configuring">24.2.1. Configuring At Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch
-configuring">24.2.2. Configuring Batch Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">24.2.3. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">24.2.4. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">24.2.5. Controlling Access to At and Batch</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-service">24.2.6. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">24.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-autotasks-installed-docs">24.3.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id1685830" class="indexterm"></a><div class="para">
+ In Linux, tasks 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="id942178" class="indexterm"></a><div class="section" title="24.1. Cron" id="s1-autotasks-cron"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-autotasks-cron">24.1. Cron</h2></div></div></div><div class="para">
+ Cron is a daemon 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 task is scheduled, it is not executed. To schedule one-time tasks, refer to <a class="xref" href="#s1-autotasks-at-batch" title="24.2. At and Batch">Section 24.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. To determine if the package is installed, use the <code class="command">rpm -q cronie</code> command. To determine if the service is running, use the command <code class="command">/sbin/service crond status</code>.
+ </div><div class="section" title="24.1.1. Configuring Cron Tasks" id="s2-autotasks-cron-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-cron-configuring">24.1.1. Configuring Cron Tasks</h3></div></div></div><a id="id780885" class="indexterm"></a><a id="id603988" class="indexterm"></a><div class="para">
+ The main configuration file for cron, <code class="filename">/etc/crontab</code>, contains the following lines:
+ </div><pre class="screen">
+SHELL=/bin/bash
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root HOME=/
+# run-parts
+01 * * * * root run-parts /etc/cron.hourly
+02 4 * * * root run-parts /etc/cron.daily
+22 4 * * 0 root run-parts /etc/cron.weekly
+42 4 1 * * root run-parts /etc/cron.monthly
+</pre><div class="para">
+ The first four lines are variables used to configure the environment in which the cron tasks are run. The <code class="computeroutput">SHELL</code> variable tells the system which shell environment to use (in this example the bash shell), while the <code class="computeroutput">PATH</code> variable defines the path used to execute commands. The output of the cron tasks are emailed to the username defined with the <code class="computeroutput">MAILTO</code> variable. If the <code class="computeroutput">MAILTO</code> variable is defined as an empty string (<code class="computeroutput">MAILTO=""</code>), email is not sent. 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">
+ Each line in the <code class="filename">/etc/crontab</code> file represents a task and has the following format:
+ </div><pre class="screen">
+minute hour day month dayofweek 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">dayofweek</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">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 mark (#) are comments and are not processed.
+ </div><div class="para">
+ As shown in the <code class="filename">/etc/crontab</code> file, the <code class="command">run-parts</code> script executes the scripts in the <code class="filename">/etc/cron.hourly/</code>, <code class="filename">/etc/cron.daily/</code>, <code class="filename">/etc/cron.weekly/</code>, and <code class="filename">/etc/cron.monthly/</code> directories on an hourly, daily, weekly, or monthly basis respectively. The files in these directories should be shell scripts.
+ </div><div class="para">
+ If a cron task is required to be executed on a schedule other than hourly, daily, weekly, or monthly, it can be added to the <code class="filename">/etc/cron.d/</code> directory. All files in this directory use the same syntax as <code class="filename">/etc/crontab</code>. Refer to <a class="xref" href="#crontab-examples" title="Example 24.1. Crontab Examples">Example 24.1, “Crontab Examples”</a> for examples.
+ </div><a id="id706958" class="indexterm"></a><div class="example" title="Example 24.1. Crontab Examples" id="crontab-examples"><div class="example-contents"><pre class="screen">
+# record the memory usage of the system every monday
+# at 3:30AM in the file /tmp/meminfo
+30 3 * * mon cat /proc/meminfo >> /tmp/meminfo
+# run custom script the first day of every month at 4:10AM
+10 4 1 * * /root/scripts/backup.sh
+</pre></div><h6>Example 24.1. Crontab Examples</h6></div><br class="example-break" /><a id="id706988" class="indexterm"></a><a id="id665876" class="indexterm"></a><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>.
+ </div><div class="para">
+ The cron daemon checks 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 a crontab file is changed.
+ </div></div><div class="section" title="24.1.2. 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">24.1.2. 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 read each time a user tries to add or delete a cron task.
+ </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><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN" class="section" title="24.1.3. Starting and Stopping the Service" id="s2-autotasks-cron-service" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-cron-service">24.1.3. Starting and Stopping the Service</h3></div></div></div><div class="para">
+ 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 6. Controlling Access to Services">Chapter 6, <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="24.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">24.2. At and Batch</h2></div></div></div><a id="id602992" class="indexterm"></a><a id="id737061" 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="24.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">24.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 type <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 type <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 typing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> on a blank line to exit. If a script is en
tered, 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 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="24.2.3. Viewing Pending Jobs">Section 24.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="24.2.5. Controlling Access to At and Batch">Section 24.2.5, “Controlling Access to At and Batch”</a> for details.
+ </div></div><div class="section" title="24.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">24.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 type <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 type <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 typing <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 use
d 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="24.2.3. Viewing Pending Jobs">Section 24.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="24.2.5. Controlling Access to At and Batch">Section 24.2.5, “Controlling Access to At and Batch”</a> for details.
+ </div></div><div class="section" title="24.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">24.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="24.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">24.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 24.1. at and batch Command Line Options" id="tb-at-command-line-options"><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><h6>Table 24.1. <code class="command">at</code> and <code class="command">batch</code> Command Line Options</h6></div><br class="table-break" /></div><div class="section" title="24.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">24.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 xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN" class="section" title="24.2.6. Starting and Stopping the Service" id="s2-autotasks-at-batch-service" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-at-batch-service">24.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 6. Controlling Access to Services">Chapter 6, <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="24.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">24.3. Additional Resources</h2></div></div></div><a id="id2000995" class="indexterm"></a><a id="id2001009" class="indexterm"></a><a id="id1018047" class="indexterm"></a><div class="para">
+ To learn more about configuring automated tasks, refer to the following resources.
+ </div><div class="section" title="24.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">24.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 — 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">/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 25. Log Files" id="ch-Log_Files" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 25. Log Files</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-logfiles-locating">25.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-viewing">25.2. Viewing Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-adding">25.3. Adding a Log File</a></span></dt><dt><span class="section"><a href="#s1-logfiles-examining">25.4. Monitoring Log Files</a></span></dt></dl></div><a id="id970483" class="indexterm"></a><a id="id1019058" 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="id1759458" class="indexterm"></a><a id="id573086" class="indexterm"></a><div class="para">
+ Some log files are controlled by a daemon called <code class="command">rsyslog</code>. A list of log messages maintained by <code class="command">rsyslog</code> can be found in the <code class="filename">/etc/rsyslog.conf</code> configuration file.
+ </div><div class="section" title="25.1. Locating Log Files" id="s1-logfiles-locating"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-locating">25.1. Locating Log Files</h2></div></div></div><a id="id884275" 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="id617152" class="indexterm"></a><a id="id1939587" class="indexterm"></a><div class="para">
+ You may notice multiple files in the log file directory with numbers after them. These are created when the log files are rotated. 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. By default, it is configured to rotate every week and keep four weeks worth of previous log files.
+ </div></div><div class="section" title="25.2. Viewing Log Files" id="s1-logfiles-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-viewing">25.2. Viewing Log Files</h2></div></div></div><a id="id1125455" 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="id911457" class="indexterm"></a><div class="para">
+ To view system log files in an interactive, real-time application, use the <span class="application"><strong>System Log Viewer</strong></span>. To start the application, go to <span class="guimenu"><strong>Applications</strong></span> (the main menu on the panel) > <span class="guimenuitem"><strong>System</strong></span> > <span class="guimenuitem"><strong>System Logs</strong></span>, or type the command <code class="command">gnome-system-log</code> at a shell prompt.
+ </div><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 25.1. System Log Viewer">Figure 25.1, “ <span class="application">System Log Viewer</span> ”</a>.
+ </div><a id="id812554" class="indexterm"></a><a id="id812572" class="indexterm"></a><div class="figure" title="Figure 25.1. System Log Viewer" id="fig-redhat-logviewer"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer.png" width="444" alt="System Log Viewer" /><div class="longdesc"><div class="para">
+ System Log Viewer
+ </div></div></div></div><h6>Figure 25.1. <span class="application">System Log Viewer</span> </h6></div><br class="figure-break" /><a id="id777465" class="indexterm"></a><div class="para">
+ To filter the contents of the selected log file, click on <span class="guimenuitem"><strong>View</strong></span> from the menu and select <span class="guimenuitem"><strong>Filter</strong></span> as illustrated below.
+ </div><div class="figure" title="Figure 25.2. System Log Viewer - View Menu" id="fig-redhat-logviewer-prefs"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-prefs.png" width="444" alt="System Log Viewer - View Menu" /><div class="longdesc"><div class="para">
+ System Log Viewer - View Menu
+ </div></div></div></div><h6>Figure 25.2. <span class="application">System Log Viewer - View Menu</span> </h6></div><br class="figure-break" /><a id="id745352" class="indexterm"></a><div class="para">
+ Selecting the <span class="guilabel"><strong>Filter</strong></span> menu item will display the <span class="guilabel"><strong>Filter</strong></span> text field where you can type the keywords you wish to use for your filter. To clear your filter click on the <span class="guibutton"><strong>Clear</strong></span> button.The figure below illustrates a sample filter.
+ </div><div class="figure" title="Figure 25.3. System Log Viewer - Filter" id="fig-redhat-logviewer-sample"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-sample.png" width="444" alt="System Log Viewer - Filter" /><div class="longdesc"><div class="para">
+ System Log Viewer - Filter
+ </div></div></div></div><h6>Figure 25.3. <span class="application">System Log Viewer - Filter</span> </h6></div><br class="figure-break" /><a id="id642974" class="indexterm"></a></div><div class="section" title="25.3. 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">25.3. 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="guimenu"><strong>Open Log</strong></span> window where you can select the directory and filename of the log file you wish to view.The figure below illustrates the <span class="guimenu"><strong>Open Log</strong></span> window.
+ </div><div class="figure" title="Figure 25.4. Adding a Log File" id="fig-redhat-logviewer-add"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-add.png" width="444" alt="Adding a Log File" /><div class="longdesc"><div class="para">
+ Adding a Log File
+ </div></div></div></div><h6>Figure 25.4. 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 the contents.
+ </div><div class="para">
+ Please also note that the System Log Viewer also allows you to open zipped logs whose filenames end in ".gz".
+ </div></div><div class="section" title="25.4. Monitoring Log Files" id="s1-logfiles-examining"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-examining">25.4. Monitoring Log Files</h2></div></div></div><a id="id918846" class="indexterm"></a><a id="id1984659" class="indexterm"></a><div class="para">
+ <span class="application"><strong>System Log 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 and after five seconds are displayed in normal format. This is illustrated in the figures below. The figure below illustrates a new alert in the <span class="guimenuitem"><strong>messages</strong></span> log file. The log file is listed in bold text.
+ </div><div class="figure" title="Figure 25.5. Log File Alert" id="fig-redhat-logviewer-monitoring1"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-monitoring1.png" width="444" alt="Log File Alert" /><div class="longdesc"><div class="para">
+ Log File Alert
+ </div></div></div></div><h6>Figure 25.5. Log File Alert</h6></div><br class="figure-break" /><div class="para">
+ Clicking on the <span class="guimenuitem"><strong>messages</strong></span> log file displays the logs in the file with the new lines in bold as illustrated below.
+ </div><div class="figure" title="Figure 25.6. Log file contents" id="fig-redhat-logviewer-monitoring2"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-monitoring2.png" width="444" alt="Log file contents" /><div class="longdesc"><div class="para">
+ Log file contents
+ </div></div></div></div><h6>Figure 25.6. Log file contents</h6></div><br class="figure-break" /><div class="para">
+ The new lines are displayed in bold for five seconds after which they are displayed in normal font.
+ </div><div class="figure" title="Figure 25.7. Log file contents after five seconds" id="fig-redhat-logviewer-monitoring3"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-monitoring3.png" width="444" alt="Log file contents after five seconds" /><div class="longdesc"><div class="para">
+ Log file contents after five seconds
+ </div></div></div></div><h6>Figure 25.7. Log file contents after five seconds</h6></div><br class="figure-break" /></div></div></div><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES" class="part" title="Part IV. System Monitoring" id="pt-system-monitoring" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES"><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="id787642"><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">26. Gathering System Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-sysinfo-system-processes">26.1. System Processes</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-memory-usage">26.2. Memory Usage</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-filesystems">26.3. File Systems</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-hardware">26.4. Hardware</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-additional-resources">26.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-installed-docs">26.5.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-OProfile">27. OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-overview-tools">27.1. Overview of Tools</a
></span></dt><dt><span class="section"><a href="#s1-oprofile-configuring">27.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">27.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">27.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">27.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">27.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">27.4. Saving Data</a></span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">27.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">27.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opreport-si
ngle">27.5.2. Using <code class="command">opreport</code> on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">27.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opannotate">27.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">27.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">27.7. Example Usage</a></span></dt><dt><span class="section"><a href="#s1-oprofile-gui">27.8. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1-oprofile-additional-resources">27.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-installed-docs">27.9.1. Installed Docs</a></span></dt><dt><span class="section"><a href="#s2-oprofile-useful-web
sites">27.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-abrt">28. ABRT</a></span></dt><dd><dl><dt><span class="section"><a href="#id2002784">28.1. Overview</a></span></dt><dt><span class="section"><a href="#id677272">28.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="#configuring">28.3. Configuring ABRT</a></span></dt><dt><span class="section"><a href="#id1986935">28.4. Plugins and Sending Crash Reports</a></span></dt><dt><span class="section"><a href="#id1189335">28.5. Using the Command Line Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#id1189349">28.5.1. Viewing Crashes</a></span></dt><dt><span class="section"><a href="#id737384">28.5.2. Reporting Crashes</a></span></dt><dt><span class="section"><a href="#id570721">28.5.3. Deleting Crashes</a></span></dt></dl></dd></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" title="Chapter 26. Gathering System Info
rmation" id="ch-Gathering_System_Information" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 26. Gathering System Information</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-sysinfo-system-processes">26.1. System Processes</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-memory-usage">26.2. Memory Usage</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-filesystems">26.3. File Systems</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-hardware">26.4. Hardware</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-additional-resources">26.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-installed-docs">26.5.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id1023057" class="indexterm"></a><a id="id947454" 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="26.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">26.1. System Processes</h2></div></div></div><a id="id688911" class="indexterm"></a><a id="id654065" class="indexterm"></a><a id="id714978" 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="id940187" class="indexterm"></a><a id="id904485" 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 26.1. Interactive top commands">Table 26.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 26.1. Interactive top commands" id="interactive-top-command"><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><h6>Table 26.1. Interactive <code class="command">top</code> commands</h6></div><br class="table-break" /><a id="id704459" class="indexterm"></a><a id="id704472" 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>System</strong></span> > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>System Monitor</strong></span> or type <code class="command">gnome-system-monitor</code> at a shell prompt (such as an XTerm). Select the <span class="guilabel"><strong>Process Listing</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 Gnome System Monitor, 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">
+ Hide a process.
+ </div></li><li class="listitem"><div class="para">
+ View hidden processes.
+ </div></li><li class="listitem"><div class="para">
+ View memory maps.
+ </div></li><li class="listitem"><div class="para">
+ View the files opened by the selected process.
+ </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 26.1. GNOME System Monitor" id="fig-sysinfo-processes"><div class="figure-contents"><div class="mediaobject"><img src="images/gnome-system-monitor-processes.png" width="444" alt="GNOME System Monitor" /><div class="longdesc"><div class="para">
+ Process Listing of GNOME System Monitor
+ </div></div></div></div><h6>Figure 26.1. <span class="application">GNOME System Monitor</span> </h6></div><br class="figure-break" /></div><div class="section" title="26.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">26.2. Memory Usage</h2></div></div></div><a id="id916388" class="indexterm"></a><a id="id796340" class="indexterm"></a><a id="id796349" class="indexterm"></a><a id="id796359" 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: 645712 549720 95992 0 176248 224452 -/+ buffers/cache: 149020 496692 Swap: 1310712 0 1310712</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: 630 536 93 0 172 219 -/+ buffers/cache: 145 485 Swap: 1279 0 1279</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, go to <span class="guimenu"><strong>System</strong></span> > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>System Monitor</strong></span> or type <code class="command">gnome-system-monitor</code> at a shell prompt (such as an XTerm). Click on the <span class="guilabel"><strong>Resources</strong></span> tab.
+ </div><div class="figure" title="Figure 26.2. GNOME System Monitor - Resources tab" id="fig-sysinfo-memory"><div class="figure-contents"><div class="mediaobject"><img src="images/gnome-system-monitor-memory.png" width="444" 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 26.2. <span class="application">GNOME System Monitor - Resources tab</span> </h6></div><br class="figure-break" /></div><div class="section" title="26.3. File Systems" id="s1-sysinfo-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-filesystems">26.3. File Systems</h2></div></div></div><a id="id982358" class="indexterm"></a><a id="id601452" class="indexterm"></a><a id="id601461" class="indexterm"></a><div class="para">
+ The <code class="command">df</code> command reports the system's disk space usage. If you type 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/VolGroup00-LogVol00 11675568 6272120 4810348 57% / /dev/sda1 100691 9281 86211 10% /boot none 322856 0 322856 0% /dev/shm</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/VolGroup00-LogVol00 12G 6.0G 4.6G 57% / /dev/sda1 99M 9.1M 85M 10% /boot none 316M 0 316M 0% /dev/shm</pre><a id="id601510" class="indexterm"></a><a id="id601532" 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="id818018" 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 type <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>System</strong></span> > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>System Monitor</strong></span> or type <code class="command">gnome-system-monitor</code> at a shell prompt (such as an XTerm). 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 26.3. GNOME System Monitor - File Systems" id="fig-sysinfo-filesystems"><div class="figure-contents"><div class="mediaobject"><img src="images/gnome-system-monitor-filesystems.png" width="444" alt="GNOME System Monitor - File Systems" /><div class="longdesc"><div class="para">
+ File systems tab of the gnome-system-monitor
+ </div></div></div></div><h6>Figure 26.3. <span class="application">GNOME System Monitor - File Systems</span> </h6></div><br class="figure-break" /></div><div class="section" title="26.4. Hardware" id="s1-sysinfo-hardware"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-hardware">26.4. Hardware</h2></div></div></div><a id="id709199" class="indexterm"></a><a id="id709212" class="indexterm"></a><a id="id709226" class="indexterm"></a><a id="id809416" 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 26.4. Hardware Browser">Figure 26.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 26.4. Hardware Browser" id="sysinfo-hwbrowser-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/hwbrowser.png" width="444" alt="Hardware Browser" /><div class="longdesc"><div class="para">
+ hwbrowser
+ </div></div></div></div><h6>Figure 26.4. <span class="application">Hardware Browser</span> </h6></div><br class="figure-break" /><a id="id2004007" class="indexterm"></a><a id="id2004022" 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 26.5. Device Manager" id="sysinfo-devicemngr-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/devicemngr.png" width="444" alt="Device Manager" /><div class="longdesc"><div class="para">
+ Device Manager
+ </div></div></div></div><h6>Figure 26.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:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06) 00:00.1 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06) 00:01.0 VGA compatible controller: S3 Inc. Savage 4 (rev 04) 00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08) 00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 50) 00:0f.1 IDE interface: ServerWorks OSB4 IDE Controller 00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 04) 01:03.0 SCSI storage controller: Adaptec AIC-7892P U160/m (rev 02) 01:05.0 RAID bus controller: IBM ServeRAID Controller</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="26.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">26.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="26.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">26.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 — Type <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 — type <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 — Type <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 — Type <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 — Type <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="id864561" 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 27. OProfile" id="ch-OProfile" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 27. OProfile</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-oprofile-overview-tools">27.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="#s1-oprofile-configuring">27.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">27.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">27.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">27.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">27.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-d
ata">27.4. Saving Data</a></span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">27.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">27.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opreport-single">27.5.2. Using <code class="command">opreport</code> on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">27.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opannotate">27.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">27.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">27.7. Example Usage</a></span></dt><dt><span class="sectio
n"><a href="#s1-oprofile-gui">27.8. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1-oprofile-additional-resources">27.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-installed-docs">27.9.1. Installed Docs</a></span></dt><dt><span class="section"><a href="#s2-oprofile-useful-websites">27.9.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id1126730" class="indexterm"></a><a id="id1023991" class="indexterm"></a><div class="para">
+ OProfile is a low overhead, system-wide performance monitoring tool. It uses the performance monitoring hardware on the processor to retrieve information about the kernel and executables on the system, such as when memory is referenced, the number of L2 cache requests, and the number of hardware interrupts received. On a Fedora system, the <code class="filename">oprofile</code> RPM package must be installed to use this tool.
+ </div><div class="para">
+ Many processors include dedicated performance monitoring hardware. This hardware makes it possible to detect when certain events happen (such as the requested data not being in cache). The hardware normally takes the form of one or more <em class="firstterm">counters</em> that are incremented each time an event takes place. When the counter value, essentially rolls over, an interrupt is generated, making it possible to control the amount of detail (and therefore, overhead) produced by performance monitoring.
+ </div><div class="para">
+ OProfile uses this hardware (or a timer-based substitute in cases where performance monitoring hardware is not present) to collect <em class="firstterm">samples</em> of performance-related data each time a counter generates an interrupt. These samples are periodically written out to disk; later, the data contained in these samples can then be used to generate reports on system-level and application-level performance.
+ </div><div class="para">
+ OProfile is a useful tool, but be aware of some limitations when using it:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Use of shared libraries</em></span> — Samples for code in shared libraries are not attributed to the particular application unless the <code class="option">--separate=library</code> option is used.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Performance monitoring samples are inexact</em></span> — When a performance monitoring register triggers a sample, the interrupt handling is not precise like a divide by zero exception. Due to the out-of-order execution of instructions by the processor, the sample may be recorded on a nearby instruction.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em> <code class="command">opreport</code> does not associate samples for inline functions' properly</em></span> — <code class="command">opreport</code> uses a simple address range mechanism to determine which function an address is in. Inline function samples are not attributed to the inline function but rather to the function the inline function was inserted into.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>OProfile accumulates data from multiple runs</em></span> — OProfile is a system-wide profiler and expects processes to start up and shut down multiple times. Thus, samples from multiple runs accumulate. Use the command <code class="command">opcontrol --reset</code> to clear out the samples from previous runs.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Non-CPU-limited performance problems</em></span> — OProfile is oriented to finding problems with CPU-limited processes. OProfile does not identify processes that are asleep because they are waiting on locks or for some other event to occur (for example an I/O device to finish an operation).
+ </div></li></ul></div><div class="section" title="27.1. Overview of Tools" id="s1-oprofile-overview-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-overview-tools">27.1. Overview of Tools</h2></div></div></div><a id="id896415" class="indexterm"></a><div class="para">
+ <a class="xref" href="#tb-oprofile-tools" title="Table 27.1. OProfile Commands">Table 27.1, “OProfile Commands”</a> provides a brief overview of the tools provided with the <code class="filename">oprofile</code> package.
+ </div><div class="table" title="Table 27.1. OProfile Commands" id="tb-oprofile-tools"><div class="table-contents"><table summary="OProfile Commands" border="1"><colgroup><col width="29%" /><col width="71%" /></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">ophelp</code>
+ </td><td>
+ <div class="para">
+ Displays available events for the system's processor along with a brief description of each.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="command">opimport</code>
+ </td><td>
+ <div class="para">
+ Converts sample database files from a foreign binary format to the native format for the system. Only use this option when analyzing a sample database from a different architecture.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="command">opannotate</code>
+ </td><td>
+ Creates annotated source for an executable if the application was compiled with debugging symbols. Refer to <a class="xref" href="#s2-oprofile-reading-opannotate" title="27.5.4. Using opannotate">Section 27.5.4, “Using <code class="command">opannotate</code> ”</a> for details.
+ </td></tr><tr><td>
+ <code class="command">opcontrol</code>
+ </td><td>
+ <div class="para">
+ Configures what data is collected. Refer to <a class="xref" href="#s1-oprofile-configuring" title="27.2. Configuring OProfile">Section 27.2, “Configuring OProfile”</a> for details.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="command">opreport</code>
+ </td><td>
+ <div class="para">
+ Retrieves profile data. Refer to <a class="xref" href="#s2-oprofile-reading-opreport" title="27.5.1. Using opreport">Section 27.5.1, “Using <code class="command">opreport</code> ”</a> for details.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="command">oprofiled</code>
+ </td><td>
+ <div class="para">
+ Runs as a daemon to periodically write sample data to disk.
+ </div>
+
+ </td></tr></tbody></table></div><h6>Table 27.1. OProfile Commands</h6></div><br class="table-break" /></div><div class="section" title="27.2. Configuring OProfile" id="s1-oprofile-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-configuring">27.2. Configuring OProfile</h2></div></div></div><a id="id821180" class="indexterm"></a><a id="id821194" class="indexterm"></a><a id="id821212" class="indexterm"></a><div class="para">
+ Before OProfile can be run, it must be configured. At a minimum, selecting to monitor the kernel (or selecting not to monitor the kernel) is required. The following sections describe how to use the <code class="command">opcontrol</code> utility to configure OProfile. As the <code class="command">opcontrol</code> commands are executed, the setup options are saved to the <code class="filename">/root/.oprofile/daemonrc</code> file.
+ </div><div class="section" title="27.2.1. Specifying the Kernel" id="s2-oprofile-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-kernel">27.2.1. Specifying the Kernel</h3></div></div></div><a id="id821255" class="indexterm"></a><div class="para">
+ First, configure whether OProfile should monitor the kernel. This is the only configuration option that is required before starting OProfile. All others are optional.
+ </div><div class="para">
+ To monitor the kernel, execute the following command as root:
+ </div><a id="id996411" class="indexterm"></a><pre class="screen">
+<code class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux</code>
+</pre><div class="note"><h2>Note</h2><div class="para">
+ The <code class="command">debuginfo</code> package must be installed (which contains the uncompressed kernel) in order to monitor the kernel.
+ </div></div><div class="para">
+ To configure OProfile not to monitor the kernel, execute the following command as root:
+ </div><a id="id996467" class="indexterm"></a><pre class="screen">
+<code class="command">opcontrol --setup --no-vmlinux</code>
+</pre><div class="para">
+ This command also loads the <code class="computeroutput">oprofile</code> kernel module, if it is not already loaded, and creates the <code class="filename">/dev/oprofile/</code> directory, if it does not already exist. Refer to <a class="xref" href="#s1-oprofile-dev-oprofile" title="27.6. Understanding /dev/oprofile/">Section 27.6, “Understanding <code class="filename">/dev/oprofile/</code> ”</a> for details about this directory.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ Even if OProfile is configured not to profile the kernel, the SMP kernel still must be running so that the <code class="command">oprofile</code> module can be loaded from it.
+ </div></div><div class="para">
+ Setting whether samples should be collected within the kernel only changes what data is collected, not how or where the collected data is stored. To generate different sample files for the kernel and application libraries, refer to <a class="xref" href="#s2-oprofile-starting-separate" title="27.2.3. Separating Kernel and User-space Profiles">Section 27.2.3, “Separating Kernel and User-space Profiles”</a>.
+ </div></div><div class="section" title="27.2.2. Setting Events to Monitor" id="s2-oprofile-events"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-events">27.2.2. Setting Events to Monitor</h3></div></div></div><a id="id777283" class="indexterm"></a><div class="para">
+ Most processors contain <em class="firstterm">counters</em>, which are used by OProfile to monitor specific events. As shown in <a class="xref" href="#tb-oprofile-processors" title="Table 27.2. OProfile Processors and Counters">Table 27.2, “OProfile Processors and Counters”</a>, the number of counters available depends on the processor.
+ </div><div class="table" title="Table 27.2. OProfile Processors and Counters" id="tb-oprofile-processors"><div class="table-contents"><table summary="OProfile Processors and Counters" border="1"><colgroup><col width="43%" /><col width="29%" /><col width="29%" /></colgroup><thead><tr><th>
+ Processor
+ </th><th>
+ <code class="command">cpu_type</code>
+ </th><th>
+ Number of Counters
+ </th></tr></thead><tbody><tr><td>
+ Pentium Pro
+ </td><td>
+ i386/ppro
+ </td><td>
+ 2
+ </td></tr><tr><td>
+ Pentium II
+ </td><td>
+ i386/pii
+ </td><td>
+ 2
+ </td></tr><tr><td>
+ Pentium III
+ </td><td>
+ i386/piii
+ </td><td>
+ 2
+ </td></tr><tr><td>
+ Pentium 4 (non-hyper-threaded)
+ </td><td>
+ i386/p4
+ </td><td>
+ 8
+ </td></tr><tr><td>
+ Pentium 4 (hyper-threaded)
+ </td><td>
+ i386/p4-ht
+ </td><td>
+ 4
+ </td></tr><tr><td>
+ Athlon
+ </td><td>
+ i386/athlon
+ </td><td>
+ 4
+ </td></tr><tr><td>
+ AMD64
+ </td><td>
+ x86-64/hammer
+ </td><td>
+ 4
+ </td></tr><tr><td>
+ TIMER_INT
+ </td><td>
+ timer
+ </td><td>
+ 1
+ </td></tr><tr><td>
+ IBM eServer iSeries and pSeries
+ </td><td>
+ timer
+ </td><td>
+ 1
+ </td></tr><tr><td>
+ </td><td>
+ ppc64/power4
+ </td><td>
+ 8
+ </td></tr><tr><td>
+ </td><td>
+ ppc64/power5
+ </td><td>
+ 6
+ </td></tr><tr><td>
+ </td><td>
+ ppc64/970
+ </td><td>
+ 8
+ </td></tr><tr><td>
+ IBM eServer S/390 and S/390x
+ </td><td>
+ timer
+ </td><td>
+ 1
+ </td></tr><tr><td>
+ IBM eServer zSeries
+ </td><td>
+ timer
+ </td><td>
+ 1
+ </td></tr></tbody></table></div><h6>Table 27.2. OProfile Processors and Counters</h6></div><br class="table-break" /><div class="para">
+ Use <a class="xref" href="#tb-oprofile-processors" title="Table 27.2. OProfile Processors and Counters">Table 27.2, “OProfile Processors and Counters”</a> to verify that the correct processor type was detected and to determine the number of events that can be monitored simultaneously. <code class="computeroutput">timer</code> is used as the processor type if the processor does not have supported performance monitoring hardware.
+ </div><div class="para">
+ If <code class="computeroutput">timer</code> is used, events cannot be set for any processor because the hardware does not have support for hardware performance counters. Instead, the timer interrupt is used for profiling.
+ </div><div class="para">
+ If <code class="computeroutput">timer</code> is not used as the processor type, the events monitored can be changed, and counter 0 for the processor is set to a time-based event by default. If more than one counter exists on the processor, the counters other than counter 0 are not set to an event by default. The default events monitored are shown in <a class="xref" href="#tb-oprofile-default-events" title="Table 27.3. Default Events">Table 27.3, “Default Events”</a>.
+ </div><div class="table" title="Table 27.3. Default Events" id="tb-oprofile-default-events"><div class="table-contents"><table summary="Default Events" border="1"><colgroup><col width="25%" /><col width="33%" /><col width="42%" /></colgroup><thead><tr><th>
+ Processor
+ </th><th>
+ Default Event for Counter
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ Pentium Pro, Pentium II, Pentium III, Athlon, AMD64
+ </td><td>
+ CPU_CLK_UNHALTED
+ </td><td>
+ The processor's clock is not halted
+ </td></tr><tr><td>
+ Pentium 4 (HT and non-HT)
+ </td><td>
+ GLOBAL_POWER_EVENTS
+ </td><td>
+ The time during which the processor is not stopped
+ </td></tr><tr><td>
+ TIMER_INT
+ </td><td>
+ (none)
+ </td><td>
+ Sample for each timer interrupt
+ </td></tr><tr><td>
+ ppc64/power4
+ </td><td>
+ CYCLES
+ </td><td>
+ Processor Cycles
+ </td></tr><tr><td>
+ ppc64/power5
+ </td><td>
+ CYCLES
+ </td><td>
+ Processor Cycles
+ </td></tr><tr><td>
+ ppc64/970
+ </td><td>
+ CYCLES
+ </td><td>
+ Processor Cycles
+ </td></tr></tbody></table></div><h6>Table 27.3. Default Events</h6></div><br class="table-break" /><div class="para">
+ The number of events that can be monitored at one time is determined by the number of counters for the processor. However, it is not a one-to-one correlation; on some processors, certain events must be mapped to specific counters. To determine the number of counters available, execute the following command:
+ </div><pre class="screen">
+<code class="command">ls -d /dev/oprofile/[0-9]*</code>
+</pre><div class="para">
+ The events available vary depending on the processor type. To determine the events available for profiling, execute the following command as root (the list is specific to the system's processor type):
+ </div><a id="id972123" class="indexterm"></a><a id="id972140" class="indexterm"></a><pre class="screen">
+<code class="command">ophelp</code>
+</pre><div class="para">
+ The events for each counter can be configured via the command line or with a graphical interface. For more information on the graphical interface, refer to <a class="xref" href="#s1-oprofile-gui" title="27.8. Graphical Interface">Section 27.8, “Graphical Interface”</a>. If the counter cannot be set to a specific event, an error message is displayed.
+ </div><div class="para">
+ To set the event for each configurable counter via the command line, use <code class="command">opcontrol</code>:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em> </code>
+</pre><div class="para">
+ Replace <em class="replaceable"><code><event-name></code></em> with the exact name of the event from <code class="command">ophelp</code>, and replace <em class="replaceable"><code><sample-rate></code></em> with the number of events between samples.
+ </div><div class="section" title="27.2.2.1. Sampling Rate" id="s3-oprofile-events-sampling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-oprofile-events-sampling">27.2.2.1. Sampling Rate</h4></div></div></div><a id="id1846732" class="indexterm"></a><div class="para">
+ By default, a time-based event set is selected. It creates a sample every 100,000 clock cycles per processor. If the timer interrupt is used, the timer is set to whatever the jiffy rate is and is not user-settable. If the <code class="computeroutput">cpu_type</code> is not <code class="computeroutput">timer</code>, each event can have a <em class="firstterm">sampling rate</em> set for it. The sampling rate is the number of events between each sample snapshot.
+ </div><div class="para">
+ When setting the event for the counter, a sample rate can also be specified:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em> </code>
+</pre><div class="para">
+ Replace <em class="replaceable"><code><sample-rate></code></em> with the number of events to wait before sampling again. The smaller the count, the more frequent the samples. For events that do not happen frequently, a lower count may be needed to capture the event instances.
+ </div><div class="warning"><h2>Caution</h2><div class="para">
+ Be extremely careful when setting sampling rates. Sampling too frequently can overload the system, causing the system to appear as if it is frozen or causing the system to actually freeze.
+ </div></div></div><div class="section" title="27.2.2.2. Unit Masks" id="s3-oprofile-events-unit-masks"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-oprofile-events-unit-masks">27.2.2.2. Unit Masks</h4></div></div></div><a id="id854110" class="indexterm"></a><div class="para">
+ Some user performance monitoring events may also require unit masks to further define the event.
+ </div><div class="para">
+ Unit masks for each event are listed with the <code class="command">ophelp</code> command. The values for each unit mask are listed in hexadecimal format. To specify more than one unit mask, the hexadecimal values must be combined using a bitwise <em class="firstterm">or</em> operation.
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em>:<em class="replaceable"><code><unit-mask></code></em> </code>
+</pre></div></div><div class="section" title="27.2.3. Separating Kernel and User-space Profiles" id="s2-oprofile-starting-separate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-starting-separate">27.2.3. Separating Kernel and User-space Profiles</h3></div></div></div><a id="id854172" class="indexterm"></a><div class="para">
+ By default, kernel mode and user mode information is gathered for each event. To configure OProfile to ignore events in kernel mode for a specific counter, execute the following command:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em>:<em class="replaceable"><code><unit-mask></code></em>:0</code>
+</pre><div class="para">
+ Execute the following command to start profiling kernel mode for the counter again:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em>:<em class="replaceable"><code><unit-mask></code></em>:1</code>
+</pre><div class="para">
+ To configure OProfile to ignore events in user mode for a specific counter, execute the following command:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em>:<em class="replaceable"><code><unit-mask></code></em>:<em class="replaceable"><code><kernel></code></em>:0</code>
+</pre><div class="para">
+ Execute the following command to start profiling user mode for the counter again:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em>:<em class="replaceable"><code><unit-mask></code></em>:<em class="replaceable"><code><kernel></code></em>:1</code>
+</pre><div class="para">
+ When the OProfile daemon writes the profile data to sample files, it can separate the kernel and library profile data into separate sample files. To configure how the daemon writes to sample files, execute the following command as root:
+ </div><pre class="screen">
+<code class="command">opcontrol --separate=<em class="replaceable"><code><choice></code></em> </code>
+</pre><div class="para">
+ <em class="replaceable"><code><choice></code></em> can be one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">none</code> — do not separate the profiles (default)
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">library</code> — generate per-application profiles for libraries
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">kernel</code> — generate per-application profiles for the kernel and kernel modules
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">all</code> — generate per-application profiles for libraries and per-application profiles for the kernel and kernel modules
+ </div></li></ul></div><div class="para">
+ If <code class="option">--separate=library</code> is used, the sample file name includes the name of the executable as well as the name of the library.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ These configuration changes will take effect when <code class="command">oprofile</code> is restarted.
+ </div></div></div></div><div class="section" title="27.3. Starting and Stopping OProfile" id="s1-oprofile-starting"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-starting">27.3. Starting and Stopping OProfile</h2></div></div></div><a id="id670177" class="indexterm"></a><div class="para">
+ To start monitoring the system with OProfile, execute the following command as root:
+ </div><a id="id670194" class="indexterm"></a><pre class="screen">
+<code class="command">opcontrol --start</code>
+</pre><div class="para">
+ Output similar to the following is displayed:
+ </div><pre class="screen">Using log file /var/lib/oprofile/oprofiled.log Daemon started. Profiler running.</pre><div class="para">
+ The settings in <code class="filename">/root/.oprofile/daemonrc</code> are used.
+ </div><a id="id941030" class="indexterm"></a><a id="id941048" class="indexterm"></a><a id="id941067" class="indexterm"></a><div class="para">
+ The OProfile daemon, <code class="command">oprofiled</code>, is started; it periodically writes the sample data to the <code class="filename">/var/lib/oprofile/samples/</code> directory. The log file for the daemon is located at <code class="filename">/var/lib/oprofile/oprofiled.log</code>.
+ </div><div class="para">
+ To stop the profiler, execute the following command as root:
+ </div><pre class="screen">
+<code class="command">opcontrol --shutdown</code>
+</pre></div><div class="section" title="27.4. Saving Data" id="s1-oprofile-saving-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-saving-data">27.4. Saving Data</h2></div></div></div><a id="id952790" class="indexterm"></a><div class="para">
+ Sometimes it is useful to save samples at a specific time. For example, when profiling an executable, it may be useful to gather different samples based on different input data sets. If the number of events to be monitored exceeds the number of counters available for the processor, multiple runs of OProfile can be used to collect data, saving the sample data to different files each time.
+ </div><div class="para">
+ To save the current set of sample files, execute the following command, replacing <em class="replaceable"><code><name></code></em> with a unique descriptive name for the current session.
+ </div><pre class="screen">
+<code class="command">opcontrol --save=<em class="replaceable"><code><name></code></em> </code>
+</pre><div class="para">
+ The directory <code class="filename">/var/lib/oprofile/samples/<em class="replaceable"><code>name</code></em>/</code> is created and the current sample files are copied to it.
+ </div></div><div class="section" title="27.5. Analyzing the Data" id="s1-oprofile-analyzing-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-analyzing-data">27.5. Analyzing the Data</h2></div></div></div><a id="id900647" class="indexterm"></a><div class="para">
+ Periodically, the OProfile daemon, <code class="command">oprofiled</code>, collects the samples and writes them to the <code class="filename">/var/lib/oprofile/samples/</code> directory. Before reading the data, make sure all data has been written to this directory by executing the following command as root:
+ </div><pre class="screen">
+<code class="command">opcontrol --dump</code>
+</pre><div class="para">
+ Each sample file name is based on the name of the executable. For example, the samples for the default event on a Pentium III processor for <code class="command">/bin/bash</code> becomes:
+ </div><pre class="screen">\{root\}/bin/bash/\{dep\}/\{root\}/bin/bash/CPU_CLK_UNHALTED.100000</pre><div class="para">
+ The following tools are available to profile the sample data once it has been collected:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">opreport</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">opannotate</code>
+ </div></li></ul></div><div class="para">
+ Use these tools, along with the binaries profiled, to generate reports that can be further analyzed.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ The executable being profiled must be used with these tools to analyze the data. If it must change after the data is collected, backup the executable used to create the samples as well as the sample files. Please note that the sample file and the binary have to agree. Making a backup isn't going to work if they do not match. <code class="command">oparchive</code> can be used to address this problem.
+ </div></div><div class="para">
+ Samples for each executable are written to a single sample file. Samples from each dynamically linked library are also written to a single sample file. While OProfile is running, if the executable being monitored changes and a sample file for the executable exists, the existing sample file is automatically deleted. Thus, if the existing sample file is needed, it must be backed up, along with the executable used to create it before replacing the executable with a new version. The oprofile analysis tools use the executable file that created the samples during analysis. If the executable changes the analysis tools will be unable to analyze the associated samples. Refer to <a class="xref" href="#s1-oprofile-saving-data" title="27.4. Saving Data">Section 27.4, “Saving Data”</a> for details on how to backup the sample file.
+ </div><div class="section" title="27.5.1. Using opreport" id="s2-oprofile-reading-opreport"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-reading-opreport">27.5.1. Using <code class="command">opreport</code> </h3></div></div></div><a id="id802205" class="indexterm"></a><a id="id802223" class="indexterm"></a><div class="para">
+ The <code class="command">opreport</code> tool provides an overview of all the executables being profiled.
+ </div><div class="para">
+ The following is part of a sample output:
+ </div><pre class="screen">
+Profiling through timer interrupt
+TIMER:0|
+samples| %|
+------------------
+25926 97.5212 no-vmlinux
+359 1.3504 pi
+65 0.2445 Xorg
+62 0.2332 libvte.so.4.4.0
+56 0.2106 libc-2.3.4.so
+34 0.1279 libglib-2.0.so.0.400.7
+19 0.0715 libXft.so.2.1.2
+17 0.0639 bash
+8 0.0301 ld-2.3.4.so
+8 0.0301 libgdk-x11-2.0.so.0.400.13
+6 0.0226 libgobject-2.0.so.0.400.7
+5 0.0188 oprofiled
+4 0.0150 libpthread-2.3.4.so
+4 0.0150 libgtk-x11-2.0.so.0.400.13
+3 0.0113 libXrender.so.1.2.2
+3 0.0113 du
+1 0.0038 libcrypto.so.0.9.7a
+1 0.0038 libpam.so.0.77
+1 0.0038 libtermcap.so.2.0.8
+1 0.0038 libX11.so.6.2
+1 0.0038 libgthread-2.0.so.0.400.7
+1 0.0038 libwnck-1.so.4.9.0
+</pre><div class="para">
+ Each executable is listed on its own line. The first column is the number of samples recorded for the executable. The second column is the percentage of samples relative to the total number of samples. The third column is the name of the executable.
+ </div><div class="para">
+ Refer to the <code class="command">opreport</code> man page for a list of available command line options, such as the <code class="option">-r</code> option used to sort the output from the executable with the smallest number of samples to the one with the largest number of samples.
+ </div></div><div class="section" title="27.5.2. Using opreport on a Single Executable" id="s2-oprofile-reading-opreport-single"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-reading-opreport-single">27.5.2. Using <code class="command">opreport</code> on a Single Executable</h3></div></div></div><a id="id696660" class="indexterm"></a><a id="id1022900" class="indexterm"></a><div class="para">
+ To retrieve more detailed profiled information about a specific executable, use <code class="command">opreport</code>:
+ </div><pre class="screen">
+<code class="command">opreport <em class="replaceable"><code><mode></code></em> <em class="replaceable"><code><executable></code></em> </code>
+</pre><div class="para">
+ <em class="replaceable"><code><executable></code></em> must be the full path to the executable to be analyzed. <em class="replaceable"><code><mode></code></em> must be one of the following:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="option">-l</code> </span></dt><dd><div class="para">
+ List sample data by symbols. For example, the following is part of the output from running the command <code class="command">opreport -l /lib/tls/libc-<em class="replaceable"><code><version></code></em>.so</code>:
+ </div><pre class="screen"> samples % symbol name 12 21.4286 __gconv_transform_utf8_internal 5 8.9286 _int_malloc 4 7.1429 malloc 3 5.3571 __i686.get_pc_thunk.bx 3 5.3571 _dl_mcount_wrapper_check 3 5.3571 mbrtowc 3 5.3571 memcpy 2 3.5714 _int_realloc 2 3.5714 _nl_intern_locale_data 2 3.5714 free 2 3.5714 strcmp 1 1.7857 __ctype_get_mb_cur_max 1 1.7857 __unregister_atfork 1 1.7857 __write_nocancel 1 1.7857 _dl_addr 1 1.7857 _int_free 1 1.7857 _itoa_word 1 1.7857 calc_eclosure_iter 1 1.7857 fopen@@GLIBC_2.1 1 1.7857 getpid 1 1.7857 memmove 1 1.7857 msort_with_tmp 1 1.7857 strcpy 1 1.7857 strlen 1 1.7857 vfprintf 1 1.7857 write</pre><div class="para">
+ The first column is the number of samples for the symbol, the second column is the percentage of samples for this symbol relative to the overall samples for the executable, and the third column is the symbol name.
+ </div><div class="para">
+ To sort the output from the largest number of samples to the smallest (reverse order), use <code class="option">-r</code> in conjunction with the <code class="option">-l</code> option.
+ </div></dd><dt><span class="term"> <code class="option">-i <em class="replaceable"><code><symbol-name></code></em> </code> </span></dt><dd><div class="para">
+ List sample data specific to a symbol name. For example, the following output is from the command <code class="command">opreport -l -i __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code><version></code></em>.so</code>:
+ </div><pre class="screen"> samples % symbol name 12 100.000 __gconv_transform_utf8_internal</pre><div class="para">
+ The first line is a summary for the symbol/executable combination.
+ </div><div class="para">
+ The first column is the number of samples for the memory symbol. The second column is the percentage of samples for the memory address relative to the total number of samples for the symbol. The third column is the symbol name.
+ </div></dd><dt><span class="term"> <code class="option">-d</code> </span></dt><dd><div class="para">
+ List sample data by symbols with more detail than <code class="option">-l</code>. For example, the following output is from the command <code class="command">opreport -l -d __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code><version></code></em>.so</code>:
+ </div><pre class="screen"> vma samples % symbol name 00a98640 12 100.000 __gconv_transform_utf8_internal 00a98640 1 8.3333 00a9868c 2 16.6667 00a9869a 1 8.3333 00a986c1 1 8.3333 00a98720 1 8.3333 00a98749 1 8.3333 00a98753 1 8.3333 00a98789 1 8.3333 00a98864 1 8.3333 00a98869 1 8.3333 00a98b08 1 8.3333</pre><div class="para">
+ The data is the same as the <code class="option">-l</code> option except that for each symbol, each virtual memory address used is shown. For each virtual memory address, the number of samples and percentage of samples relative to the number of samples for the symbol is displayed.
+ </div></dd><dt><span class="term"> <code class="option">-x</code> <em class="replaceable"><code><symbol-name></code></em> </span></dt><dd><div class="para">
+ Exclude the comma-separated list of symbols from the output.
+ </div></dd><dt><span class="term"> <code class="option">session</code>:<em class="replaceable"><code><name></code></em> </span></dt><dd><div class="para">
+ Specify the full path to the session or a directory relative to the <code class="filename">/var/lib/oprofile/samples/</code> directory.
+ </div></dd></dl></div></div><div class="section" title="27.5.3. Getting more detailed output on the modules" id="s2-oprofile-module-output"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-module-output">27.5.3. Getting more detailed output on the modules</h3></div></div></div><a id="id869355" class="indexterm"></a><a id="id869373" class="indexterm"></a><div class="para">
+ OProfile collects data on a system-wide basis for kernel- and user-space code running on the machine. However, once a module is loaded into the kernel, the information about the origin of the kernel module is lost. The module could have come from the initrd file on boot up, the directory with the various kernel modules, or a locally created kernel module. As a result when OProfile records sample for a module, it just lists the samples for the modules for an executable in the root directory, but this is unlikely to be the place with the actual code for the module. You will need to take some steps to make sure that analysis tools get the executable.
+ </div><div class="para">
+ For example on an AMD64 machine the sampling is set up to record "Data cache accesses" and "Data cache misses" and assuming you would like to see the data for the ext3 module:
+ </div><pre class="screen">
+<code class="command">$ opreport /ext3</code>
+CPU: AMD64 processors, speed 797.948 MHz (estimated)
+Counted DATA_CACHE_ACCESSES events (Data cache accesses) with a unit mask of 0x00 (No unit mask) count 500000
+Counted DATA_CACHE_MISSES events (Data cache misses) with a unit mask of 0x00 (No unit mask) count 500000
+DATA_CACHE_ACC...|DATA_CACHE_MIS...|
+samples| %| samples| %|
+------------------------------------
+148721 100.000 1493 100.000 ext3
+</pre><div class="para">
+ To get a more detailed view of the actions of the module, you will need to either have the module unstripped (e.g. installed from a custom build) or have the debuginfo RPM installed for the kernel.
+ </div><div class="para">
+ Find out which kernel is running, "uname -a", get the appropriate debuginfo rpm, and install on the machine.
+ </div><div class="para">
+ Then make a symbolic link so oprofile finds the code for the module in the correct place:
+ </div><pre class="screen">
+ <code class="command"># ln -s /lib/modules/`uname -r`/kernel/fs/ext3/ext3.ko /ext3</code>
+</pre><div class="para">
+ Then the detailed information can be obtained with:
+ </div><pre class="screen">
+<code class="command"># opreport image:/ext3 -l|more</code>
+warning: could not check that the binary file /ext3 has not been modified since the profile was taken. Results may be inaccurate.
+CPU: AMD64 processors, speed 797.948 MHz (estimated)
+Counted DATA_CACHE_ACCESSES events (Data cache accesses) with a unit mask of 0x00 (No unit mask) count 500000
+Counted DATA_CACHE_MISSES events (Data cache misses) with a unit mask of 0x00 (No unit mask) count 500000
+samples % samples % symbol name
+16728 11.2479 7 0.4689 ext3_group_sparse
+16454 11.0637 4 0.2679 ext3_count_free_blocks
+14583 9.8056 51 3.4159 ext3_fill_super
+8281 5.5681 129 8.6403 ext3_ioctl
+7810 5.2514 62 4.1527 ext3_write_info
+7286 4.8991 67 4.4876 ext3_ordered_writepage
+6509 4.3767 130 8.7073 ext3_new_inode
+6378 4.2886 156 10.4488 ext3_new_block
+5932 3.9887 87 5.8272 ext3_xattr_block_list
+...
+</pre></div><div class="section" title="27.5.4. Using opannotate" id="s2-oprofile-reading-opannotate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-reading-opannotate">27.5.4. Using <code class="command">opannotate</code> </h3></div></div></div><a id="id849402" class="indexterm"></a><a id="id849420" class="indexterm"></a><div class="para">
+ The <code class="command">opannotate</code> tool tries to match the samples for particular instructions to the corresponding lines in the source code. The resulting files generated should have the samples for the lines at the left. It also puts in a comment at the beginning of each function listing the total samples for the function.
+ </div><div class="para">
+ For this utility to work, the executable must be compiled with GCC's <code class="option">-g</code> option. By default, Fedora packages are not compiled with this option.
+ </div><div class="para">
+ The general syntax for <code class="command">opannotate</code> is as follows:
+ </div><pre class="screen">
+<code class="command">opannotate --search-dirs <em class="replaceable"><code><src-dir></code></em> --source <em class="replaceable"><code><executable></code></em> </code>
+</pre><div class="para">
+ The directory containing the source code and the executable to be analyzed must be specified. Refer to the <code class="command">opannotate</code> man page for a list of additional command line options.
+ </div></div></div><div class="section" title="27.6. Understanding /dev/oprofile/" id="s1-oprofile-dev-oprofile"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-dev-oprofile">27.6. Understanding <code class="filename">/dev/oprofile/</code> </h2></div></div></div><a id="id977723" class="indexterm"></a><a id="id977741" class="indexterm"></a><div class="para">
+ The <code class="filename">/dev/oprofile/</code> directory contains the file system for OProfile. Use the <code class="command">cat</code> command to display the values of the virtual files in this file system. For example, the following command displays the type of processor OProfile detected:
+ </div><pre class="screen">
+<code class="command">cat /dev/oprofile/cpu_type</code>
+</pre><div class="para">
+ A directory exists in <code class="filename">/dev/oprofile/</code> for each counter. For example, if there are 2 counters, the directories <code class="filename">/dev/oprofile/0/</code> and <code class="filename">dev/oprofile/1/</code> exist.
+ </div><div class="para">
+ Each directory for a counter contains the following files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">count</code> — The interval between samples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">enabled</code> — If 0, the counter is off and no samples are collected for it; if 1, the counter is on and samples are being collected for it.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">event</code> — The event to monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">kernel</code> — If 0, samples are not collected for this counter event when the processor is in kernel-space; if 1, samples are collected even if the processor is in kernel-space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">unit_mask</code> — Defines which unit masks are enabled for the counter.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">user</code> — If 0, samples are not collected for the counter event when the processor is in user-space; if 1, samples are collected even if the processor is in user-space.
+ </div></li></ul></div><div class="para">
+ The values of these files can be retrieved with the <code class="command">cat</code> command. For example:
+ </div><pre class="screen">
+<code class="command">cat /dev/oprofile/0/count</code>
+</pre></div><div class="section" title="27.7. Example Usage" id="s1-oprofile-example-usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-example-usage">27.7. Example Usage</h2></div></div></div><div class="para">
+ While OProfile can be used by developers to analyze application performance, it can also be used by system administrators to perform system analysis. For example:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Determine which applications and services are used the most on a system</em></span> — <code class="command">opreport</code> can be used to determine how much processor time an application or service uses. If the system is used for multiple services but is under performing, the services consuming the most processor time can be moved to dedicated systems.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Determine processor usage</em></span> — The <code class="computeroutput">CPU_CLK_UNHALTED</code> event can be monitored to determine the processor load over a given period of time. This data can then be used to determine if additional processors or a faster processor might improve system performance.
+ </div></li></ul></div></div><div class="section" title="27.8. Graphical Interface" id="s1-oprofile-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-gui">27.8. Graphical Interface</h2></div></div></div><a id="id726970" class="indexterm"></a><div class="para">
+ Some OProfile preferences can be set with a graphical interface. To start it, execute the <code class="command">oprof_start</code> command as root at a shell prompt. To use the graphical interface, you will need to have the <code class="filename">oprofile-gui</code> package installed.
+ </div><div class="para">
+ After changing any of the options, save them by clicking the <span class="guibutton"><strong>Save and quit</strong></span> button. The preferences are written to <code class="filename">/root/.oprofile/daemonrc</code>, and the application exits. Exiting the application does not stop OProfile from sampling.
+ </div><div class="para">
+ On the <span class="guilabel"><strong>Setup</strong></span> tab, to set events for the processor counters as discussed in <a class="xref" href="#s2-oprofile-events" title="27.2.2. Setting Events to Monitor">Section 27.2.2, “Setting Events to Monitor”</a>, select the counter from the pulldown menu and select the event from the list. A brief description of the event appears in the text box below the list. Only events available for the specific counter and the specific architecture are displayed. The interface also displays whether the profiler is running and some brief statistics about it.
+ </div><div class="figure" title="Figure 27.1. OProfile Setup" id="fig-oprofile-setup"><div class="figure-contents"><div class="mediaobject"><img src="images/oprof-start-setup.png" alt="OProfile Setup" /><div class="longdesc"><div class="para">
+ <code class="command">oprof_start</code> interface
+ </div></div></div></div><h6>Figure 27.1. OProfile Setup</h6></div><br class="figure-break" /><div class="para">
+ On the right side of the tab, select the <span class="guilabel"><strong>Profile kernel</strong></span> option to count events in kernel mode for the currently selected event, as discussed in <a class="xref" href="#s2-oprofile-starting-separate" title="27.2.3. Separating Kernel and User-space Profiles">Section 27.2.3, “Separating Kernel and User-space Profiles”</a>. If this option is unselected, no samples are collected for the kernel.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Profile user binaries</strong></span> option to count events in user mode for the currently selected event, as discussed in <a class="xref" href="#s2-oprofile-starting-separate" title="27.2.3. Separating Kernel and User-space Profiles">Section 27.2.3, “Separating Kernel and User-space Profiles”</a>. If this option is unselected, no samples are collected for user applications.
+ </div><div class="para">
+ Use the <span class="guilabel"><strong>Count</strong></span> text field to set the sampling rate for the currently selected event as discussed in <a class="xref" href="#s3-oprofile-events-sampling" title="27.2.2.1. Sampling Rate">Section 27.2.2.1, “Sampling Rate”</a>.
+ </div><div class="para">
+ If any unit masks are available for the currently selected event, as discussed in <a class="xref" href="#s3-oprofile-events-unit-masks" title="27.2.2.2. Unit Masks">Section 27.2.2.2, “Unit Masks”</a>, they are displayed in the <span class="guilabel"><strong>Unit Masks</strong></span> area on the right side of the <span class="guilabel"><strong>Setup</strong></span> tab. Select the checkbox beside the unit mask to enable it for the event.
+ </div><div class="para">
+ On the <span class="guilabel"><strong>Configuration</strong></span> tab, to profile the kernel, enter the name and location of the <code class="filename">vmlinux</code> file for the kernel to monitor in the <span class="guilabel"><strong>Kernel image file</strong></span> text field. To configure OProfile not to monitor the kernel, select <span class="guilabel"><strong>No kernel image</strong></span>.
+ </div><div class="figure" title="Figure 27.2. OProfile Configuration" id="fig-oprofile-configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/oprof-start-config.png" width="444" alt="OProfile Configuration" /><div class="longdesc"><div class="para">
+ OProfile Configuration
+ </div></div></div></div><h6>Figure 27.2. OProfile Configuration</h6></div><br class="figure-break" /><div class="para">
+ If the <span class="guilabel"><strong>Verbose</strong></span> option is selected, the <code class="command">oprofiled</code> daemon log includes more information.
+ </div><div class="para">
+ If <span class="guilabel"><strong>Per-application kernel samples files</strong></span> is selected, OProfile generates per-application profiles for the kernel and kernel modules as discussed in <a class="xref" href="#s2-oprofile-starting-separate" title="27.2.3. Separating Kernel and User-space Profiles">Section 27.2.3, “Separating Kernel and User-space Profiles”</a>. This is equivalent to the <code class="command">opcontrol --separate=kernel</code> command. If <span class="guilabel"><strong>Per-application shared libs samples files</strong></span> is selected, OProfile generates per-application profiles for libraries. This is equivalent to the <code class="command">opcontrol --separate=library</code> command.
+ </div><div class="para">
+ To force data to be written to samples files as discussed in <a class="xref" href="#s1-oprofile-analyzing-data" title="27.5. Analyzing the Data">Section 27.5, “Analyzing the Data”</a>, click the <span class="guibutton"><strong>Flush profiler data</strong></span> button. This is equivalent to the <code class="command">opcontrol --dump</code> command.
+ </div><div class="para">
+ To start OProfile from the graphical interface, click <span class="guibutton"><strong>Start profiler</strong></span>. To stop the profiler, click <span class="guibutton"><strong>Stop profiler</strong></span>. Exiting the application does not stop OProfile from sampling.
+ </div></div><div class="section" title="27.9. Additional Resources" id="s1-oprofile-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-additional-resources">27.9. Additional Resources</h2></div></div></div><a id="id686957" class="indexterm"></a><div class="para">
+ This chapter only highlights OProfile and how to configure and use it. To learn more, refer to the following resources.
+ </div><div class="section" title="27.9.1. Installed Docs" id="s1-oprofile-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-oprofile-installed-docs">27.9.1. Installed Docs</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/oprofile-<em class="replaceable"><code><version></code></em>/oprofile.html</code> — <em class="citetitle">OProfile Manual</em>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">oprofile</code> man page — Discusses <code class="command">opcontrol</code>, <code class="command">opreport</code>, <code class="command">opannotate</code>, and <code class="command">ophelp</code>
+ </div></li></ul></div></div><div class="section" title="27.9.2. Useful Websites" id="s2-oprofile-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-useful-websites">27.9.2. Useful Websites</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://oprofile.sourceforge.net/">http://oprofile.sourceforge.net/</a> — Contains the latest documentation, mailing lists, IRC channels, and more.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 28. ABRT" id="ch-abrt" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 28. ABRT</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#id2002784">28.1. Overview</a></span></dt><dt><span class="section"><a href="#id677272">28.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="#configuring">28.3. Configuring ABRT</a></span></dt><dt><span class="section"><a href="#id1986935">28.4. Plugins and Sending Crash Reports</a></span></dt><dt><span class="section"><a href="#id1189335">28.5. Using the Command Line Interface</a></span></dt><dd><dl><dt><span class="section"><a href="#id1189349">28.5.1. Viewing Crashes</a></span></dt><dt><span class="section"><a href="#id737384">28.5.2. Reporting Crashes</a></span></dt><dt><span class="section"><a href="#id570721">28.5.3. Deleting Crashes</a></span></dt></dl></dd><
/dl></div><div class="section" title="28.1. Overview"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id2002784">28.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, through its modular, plugin-oriented architecture, <span class="application"><strong>ABRT</strong></span> provides a number of ways to transmit the crash information to a relevant issue tracker, such as Bugzilla. <span class="application"><strong>ABRT</strong></span>'s various plugins provide the capability of capturing crash information from applications written in the C, C++ and Python languages, as well as the necessary communication backends for issue tracke
rs to which it can report.
+ </div><div class="para">
+ The <span class="application"><strong>ABRT</strong></span> application consists of the <code class="systemitem">abrtd</code> system service, <span class="application"><strong>abrt-applet</strong></span>, which runs in the user's Notification Area, and the <span class="application"><strong>Automatic Bug-Reporting Tool</strong></span> GUI application.
+ </div><div class="mediaobject" align="center"><img src="images/ABRT-Main_Window.png" align="middle" width="444" /><div class="caption"><div class="para">
+ Automatic Bug Reporting Tool Main Window
+ </div></div></div><div class="para">
+ You can open the <span class="application"><strong>ABRT</strong></span> GUI window 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="para">
+ A number of additional packages can be installed to provide <span class="application"><strong>ABRT</strong></span> plugins and addons. Here are descriptions of some of the <span class="application"><strong>ABRT</strong></span> packages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">abrt-desktop</span> — <span class="application"><strong>ABRT</strong></span>'s main package. Installing this package will install <span class="application"><strong>ABRT</strong></span> and also pull in several addon packages. Note that this package is installed by default on Fedora.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt</span> — This package contains the <code class="command">abrtd</code> daemon, configuration file, and localization and other files.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-addon-kerneloops</span> — this plugin provides support for catching and analyzing <em class="firstterm">kernel oopses</em>, i.e. errors that occur in the kernel and which may or may not result in a kernel panic. Also, the <span class="package">abrt-addon-kerneloops</span> plugin provides a way to send its report to a specified server, such as <a href="http://www.kerneloops.org/">kerneloops.org</a>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">gdb</span> — <span class="package">abrt</span> uses <code class="command">gdb</code>, the GNU debugger, to transparently provide relevant crash information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-gui</span> — this package contains the <span class="application"><strong>ABRT</strong></span> Notification Area icon, which notifies users when a program crash has been detected, and the <span class="application"><strong>Automatic Bug Reporting Tool</strong></span> GUI application, which lists program crash instances and provides ways to report those crashes to issue trackers and other locations.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-plugin-bugzilla</span> — this package contains the plugin that is able to automatically submit bug reports to Bugzilla contain crash information such as backtraces and user comments.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-plugin-ticketuploader</span> — this package contains the plugin that uploads tickets created by <span class="application"><strong>ABRT</strong></span> to a specified URL.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-addon-ccpp</span> — this plugin provides support for catching crashes in C and C++ binary programs.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-addon-python</span> — this plugin provides support for catching crashes in programs written in the Python programming language.
+ </div></li></ul></div></div><div class="section" title="28.2. Installing and Running ABRT"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id677272">28.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> is running in the Notification Area of your desktop session. You can ensure that <span class="application"><strong>ABRT</strong></span> is installed by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install abrt-desktop</code>
+</pre><div class="para">
+ <span class="application"><strong>ABRT</strong></span> is typically configured to start up at boot time. You can ensure that the <code class="systemitem">abrtd</code> daemon is running by issuing the command:
+ </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> daemon 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 <code class="command">chkconfig abrtd on</code> command as root.
+ </div><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>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 <code class="command">abrt-applet</code> detects a crash, it displays a red alarm icon in the Notifcation 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 window 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="28.3. Configuring ABRT" id="configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="configuring">28.3. 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><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><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 listed after the <em class="parameter"><code>BlackList</code></em> option 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, list them here separated by commas.
+ </div></dd><dt><span class="term">Database = SQLite3</span></dt><dd><div class="para">
+ This option 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><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 no longer catch and save program crash information.
+ </div></dd><dt><span class="term">ActionsAndReporters = SOSreport</span></dt><dd><div class="para">
+ This option tells <span class="application"><strong>ABRT</strong></span> to run the <code class="command">sosreport</code> command immediately after an application crash. 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> 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> after C and C++ or Python application crashes, respectively.
+ </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 order of actions and reporters is important.
+ </div><dl><dt><span class="term">Kerneloops = TicketUploader, Bugzilla</span></dt><dd><div class="para">
+ This directive specifies that, for kernel oopses, the TicketUploader and Bugzilla reporters should run.
+ </div></dd><dt><span class="term">CCpp = TicketUploader, Bugzilla</span></dt><dd><div class="para">
+ This directive specifies that, when C or C++program crashes occur, both the TicketUploader and Bugzilla reporters should run.
+ </div></dd><dt><span class="term">Python = TicketUploader, Bugzilla</span></dt><dd><div class="para">
+ This directive specifies that, when C or C++program crashes occur, both the TicketUploader and Bugzilla reporters should run.
+ </div></dd></dl></div><div class="variablelist" title="[ Cron ] Section Directives"><h6>[ Cron ] Section Directives</h6><dl><dt><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 28.1. [ Cron ] section of /etc/abrt/abrt.conf" id="ex-_Cron__section_of__etc_abrt_abrt.conf"><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><h6>Example 28.1. [ Cron ] section of /etc/abrt/abrt.conf</h6></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="28.4. Plugins and Sending Crash Reports"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id1986935">28.4. Plugins and Sending Crash Reports</h2></div></div></div><div class="para">
+ The <code class="literal">[AnalyzerActionsAndReporters]</code> section in <code class="filename">abrt.conf</code> specifies which plugins are to be used to report crash data. As of version 1.0.0, the default <code class="filename">abrt.conf</code> contains:
+ </div><pre class="screen">[ AnalyzerActionsAndReporters ]
+ Kerneloops = KerneloopsReporter
+ CCpp = Bugzilla, Logger
+ Python = Bugzilla, Logger</pre><div class="para">
+ These lines indicate that kernel oopses are to be reported to the <a href="kerneloops.org">kerneloops.org</a> site, and that both binary crashes and python crashes are to be reported to Bugzilla and to a local text file. Each of these destinations' details can be specified in the corresponding <code class="filename">plugins/*.conf</code> file. For example, <code class="filename">plugins/Bugzilla.conf</code> specifies which Bugzilla URL to use (set to <a href="https://bugzilla.redhat.com/">https://bugzilla.redhat.com/</a> by default), the user's login name, password for logging in to the Bugzilla site, etc.
+ </div></div><div class="section" title="28.5. Using the Command Line Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id1189335">28.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="28.5.1. Viewing Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1189349">28.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 --get-list</code>:
+ </div><pre class="screen">
+~]# <code class="command">abrt-cli --get-list</code>
+0.
+ UID : 501
+ UUID : d074c2882400b3ff245415e676ed53f22bb8e7b5
+ Package : gnome-packagekit-2.28.2-0.1.20091030git.fc12
+ Executable : /usr/bin/gpk-application
+ Crash Time : Wed 18 Nov 2009 12:07:40 PM CET
+ Crash Count: 2
+1.
+ UID : 501
+ UUID : 52d0d2f64f0b07fb0e626ecdfa4ac4faadc38258
+ Package : gnome-commander-1.3-0.3.git_D20090929T1100_13dev.fc12
+ Executable : /usr/libexec/gnome-commander/gnome-commander
+ Crash Time : Wed 18 Nov 2009 04:58:46 PM CET
+ 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. It is useful when <code class="command">abrt-cli</code> is executed with superuser privileges and it lists crashes from all users. 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="28.5.2. Reporting Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id737384">28.5.2. Reporting Crashes</h3></div></div></div><div class="para">
+ To report certain crash, you enter <code class="command">abrt-cli --report <UUID></code>, where <code class="varname">UUID</code> is a field from <code class="command">abrt-cli --get-list</code>. You do not need to remember the exact <code class="varname">UUID</code>; either use a mouse to copy and paste it, or use bash completion (write first few characters of the <code class="varname">UUID</code> and press <span class="keycap"><strong><TAB></strong></span>).
+ </div><pre class="screen">
+~]# <code class="command">abrt-cli --report 52d</code>
+ <span class="keycap"><strong><TAB></strong></span>
+~]# <code class="command">abrt-cli --report 52d0d2f64f0b07fb0e626ecdfa4ac4faadc38258</code>
+>> 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"><h2>Preferred Text Editor</h2><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 class="para">
+ When you are done with the report, save your changes and close the editor. You will be asked if you want to send the report. Respond <span class="keycap"><strong>Y</strong></span> to send the report or <span class="keycap"><strong>N</strong></span> to cancel it.
+ </div></div><div class="section" title="28.5.3. Deleting Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id570721">28.5.3. Deleting Crashes</h3></div></div></div><div class="para">
+ If you know that you do not want to report a certain crash, you can delete it from the crash list. To delete a certain crash, enter the command: <code class="command">abrt-cli --delete <em class="replaceable"><code><UUID></code></em> </code>.
+ </div></div></div></div></div><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES" class="part" title="Part V. Kernel and Driver Configuration" id="pt-kernel-configuration" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part V. Kernel and Driver Configuration</h1></div></div></div><div class="partintro" title="Kernel and Driver Configuration" id="id1024018"><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-Manually_Upgrading_the_Kernel">29. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kernel-packages">29.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">29.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">29.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">29.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image">29.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">29.6. Verifying the Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-kernel-boot-loader-grub">29.6.1. Configuring the GRUB Boot Loader</a></span></dt><dt><span c
lass="section"><a href="#s2-kernel-boot-loader-iseries">29.6.2. Configuring the <span class="trademark">OS/400</span>® Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-pseries">29.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-General_Parameters_and_Modules">30. General Parameters and Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kernel-module-utils">30.1. Kernel Module Utilities</a></span></dt><dt><span class="section"><a href="#s1-kernel-modules-persistant">30.2. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#s1-modules-parameters-specifying">30.3. Specifying Module Parameters</a></span></dt><dt><span class="section"><a href="#s1-modules-scsi">30.4. Storage parameters</a></span></dt><dt><span class="section"><a href="#s1-modules-ethernet">30.5. Ethernet Parameters</a></span></dt><dd><dl><dt><span class="section"><a hr
ef="#s2-modules-multiple-eth">30.5.1. Using Multiple Ethernet Cards</a></span></dt><dt><span class="section"><a href="#s2-modules-bonding">30.5.2. The Channel Bonding Module</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">30.6. Additional Resources</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" title="Chapter 29. Manually Upgrading the Kernel" id="ch-Manually_Upgrading_the_Kernel" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 29. Manually Upgrading the Kernel</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-kernel-packages">29.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">29.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">29.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform
-upgrade">29.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image">29.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">29.6. Verifying the Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-kernel-boot-loader-grub">29.6.1. Configuring the GRUB Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-iseries">29.6.2. Configuring the <span class="trademark">OS/400</span>® Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-pseries">29.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></div><a id="id915985" 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
+ <a id="id1022808" class="indexterm"></a>
+ <a id="id883729" class="indexterm"></a>
+ <a id="id735616" class="indexterm"></a>
+ 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><div class="warning"><h2>Use Yum to Install Kernels Whenever Possible</h2><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
+ <a id="id838880" class="indexterm"></a>
+ <a id="id753500" class="indexterm"></a>
+ 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 class="para">
+ For more information on installing kernel packages
+ <a id="id810285" class="indexterm"></a>
+ 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="29.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">29.1. Overview of Kernel Packages</h2></div></div></div><div class="para">
+ Fedora contains the following kernel packages:
+ <a id="id849582" class="indexterm"></a>
+
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">kernel</span> —
+ <a id="id1225184" class="indexterm"></a>
+ <a id="id815886" class="indexterm"></a>
+ Contains the kernel for single, multicore and multiprocessor systems.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-devel</span> —
+ <a id="id815913" class="indexterm"></a>
+ <a id="id815929" class="indexterm"></a>
+ 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-doc</span> —
+ <a id="id1002254" class="indexterm"></a>
+ <a id="id1002270" class="indexterm"></a>
+ 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> —
+ <a id="id1002312" class="indexterm"></a>
+ <a id="id986063" class="indexterm"></a>
+ 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> —
+ <a id="id986093" class="indexterm"></a>
+ <a id="id986109" class="indexterm"></a>
+ 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> — <span class="package">kernel-firmware</span> —
+ <a id="id986141" class="indexterm"></a>
+ <a id="id927282" class="indexterm"></a>
+ Technically a documentation instead of kernel package, <span class="package">perf</span> contains supporting documentation for the perf tool shipped in each kernel image subpackage.
+ </div></li></ul></div><div class="note"><h2>Note: kernel-source package availability</h2><div class="para">
+ The <span class="package">kernel-source</span> package has been removed and replaced with a source RPM package that can only be retrieved from Red Hat Network. This SRPM package must then be built locally using the <code class="command">rpmbuild</code> command. For more information on obtaining and installing the kernel source package, refer to the latest updated Fedora 13 Release Notes (and their updates) at <a href="http://www.redhat.com/docs/manuals/enterprise/">http://www.redhat.com/docs/manuals/enterprise/</a>
+ </div></div></div><div class="section" title="29.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">29.2. Preparing to Upgrade</h2></div></div></div><a id="id927344" class="indexterm"></a><div class="para">
+ Before upgrading the kernel
+ <a id="id927356" class="indexterm"></a>
+ <a id="id755113" class="indexterm"></a>
+ , it is recommended that you take some precautionary steps.
+ </div><div class="para">
+ In the first step, make sure working boot media exists
+ <a id="id755128" class="indexterm"></a>
+ 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 the <code class="command">mkbootdisk</code> man page 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="29.1. Overview of Kernel Packages">Section 29.1, “Overview of Kernel Packages”</a> for descriptions of the different packages.
+ </div><div class="para">
+ In the file name, each kernel package contains the architecture for which the package was built. The format is kernel-<em class="replaceable"><code><variant></code></em>-<em class="replaceable"><code><version></code></em>.<em class="replaceable"><code><arch></code></em>.rpm, where <em class="replaceable"><code><variant></code></em> is one of either <span class="package">PAE</span>, <span class="package">xen</span>, and so forth. The <em class="replaceable"><code><arch></code></em> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">x86_64</code> for the AMD64 and Intel EM64T architectures
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ppc64</code> for the <span class="trademark">IBM</span>® <span class="trademark">eServer</span>™ <span class="trademark">pSeries</span>™ architecture
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">s390x</code> for the <span class="trademark">IBM</span>® <span class="trademark">eServer</span>™ <span class="trademark">System z</span>® architecture
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">i686</code> for <span class="trademark">Intel</span>® <span class="trademark">Pentium</span>® II, <span class="trademark">Intel</span>® <span class="trademark">Pentium</span>® III, <span class="trademark">Intel</span>® <span class="trademark">Pentium</span>® 4, <span class="trademark">AMD Athlon</span>®, and <span class="trademark">AMD Duron</span>® systems
+ </div></li></ul></div></div><div class="section" title="29.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">29.3. Downloading the Upgraded Kernel</h2></div></div></div><a id="id731476" class="indexterm"></a><div class="para">
+ There are several ways to determine
+ <a id="id731492" class="indexterm"></a>
+ if an updated kernel is available for the system.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Security Errata —
+ <a id="id1778092" class="indexterm"></a>
+ 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 —
+ <a id="id1778119" class="indexterm"></a>
+ 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="29.5. Verifying the Initial RAM Disk Image">Section 29.5, “Verifying the Initial RAM Disk Image”</a> and <a class="xref" href="#s1-kernel-boot-loader" title="29.6. Verifying the Boot Loader">Section 29.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="29.4. Performing the Upgrade">Section 29.4, “Performing the Upgrade”</a>.
+ </div></div><div class="section" title="29.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">29.4. Performing the Upgrade</h2></div></div></div><div class="para">
+ After retrieving all of the necessary packages
+ <a id="id1778179" class="indexterm"></a>
+ , it is time to upgrade the existing kernel.
+ </div><div class="important"><h2>Important</h2><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 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="29.5. Verifying the Initial RAM Disk Image">Section 29.5, “Verifying the Initial RAM Disk Image”</a> for details.
+ </div></div><div class="section" title="29.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">29.5. Verifying the Initial RAM Disk Image</h2></div></div></div><div class="para">
+ The job of the initial RAM disk image
+ <a id="id736392" class="indexterm"></a>
+ 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 13 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="29.5. Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i">Section 29.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"><h6>Procedure 29.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 29.1. Ensuring that the kernel and initramfs versions match" id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"><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><h6>Example 29.1. Ensuring that the kernel and initramfs versions match</h6></div><br class="example-break" /><div class="para">
+ <a class="xref" href="#ex-Ensuring_that_the_kernel_and_initramfs_versions_match" title="Example 29.1. Ensuring that the kernel and initramfs versions match">Example 29.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"><h2>initrd files in the /boot directory are not the same as initramfs files</h2><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></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="29.6. Verifying the Boot Loader">Section 29.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><div class="para">
+ On IBM eSeries System i machines
+ <a id="id958655" class="indexterm"></a>
+ , 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="29.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">29.6. Verifying the Boot Loader</h2></div></div></div><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
+ <a id="id895738" class="indexterm"></a>
+ 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 29.1. Boot Loaders by Architecture" id="tb-grub-arch-loaders"><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="29.6.1. Configuring the GRUB Boot Loader">Section 29.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="29.6.1. Configuring the GRUB Boot Loader">Section 29.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="29.6.2. Configuring the OS/400® Boot Loader">Section 29.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="29.6.3. Configuring the YABOOT Boot Loader">Section 29.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><h6>Table 29.1. Boot Loaders by Architecture</h6></div><br class="table-break" /><div class="section" title="29.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">29.6.1. Configuring the GRUB Boot Loader</h3></div></div></div><div class="para">
+ GRUB's configuration file
+ <a id="id722404" class="indexterm"></a>
+ <a id="id722416" class="indexterm"></a>
+ , <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&
gt;</code></em> </code> line of the same stanza.
+ </div><div class="example" title="Example 29.2. /boot/grub/grub.conf" id="ex-_boot_grub_grub.conf"><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/sda2
+# initrd /initramfs-[generic-]version.img
+#boot=/dev/sda
+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><h6>Example 29.2. /boot/grub/grub.conf</h6></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 29.2. /boot/grub/grub.conf">Example 29.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"><h2>The initrd directive in grub.conf refers to an initramfs image</h2><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 13, 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="29.5. Verifying the Initial RAM Disk Image">Section 29.5, “Verifying the Initial RAM Disk Image”</a>.
+ </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 29.1. Verifying the Initial RAM Disk Image">Procedure 29.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 29.2. /boot/grub/grub.conf">Example 29.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 29.2. /boot/grub/grub.conf">Example 29.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 0), 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"><h2>Important: Causing the GRUB boot menu to display</h2><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 class="para">
+ Alternatively, use the boot media you created earlier to boot the system.
+ </div></div><div class="section" title="29.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">29.6.2. Configuring the <span class="trademark">OS/400</span>® Boot Loader</h3></div></div></div><div class="para">
+ The <code class="filename">/boot/vmlinitrd-<em class="replaceable"><code><kernel-version></code></em> </code> file
+ <a id="id627000" class="indexterm"></a>
+ <a id="id627012" class="indexterm"></a>
+ 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="29.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">29.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 30. General Parameters and Modules" id="ch-General_Parameters_and_Modules" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 30. General Parameters and Modules</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-kernel-module-utils">30.1. Kernel Module Utilities</a></span></dt><dt><span class="section"><a href="#s1-kernel-modules-persistant">30.2. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#s1-modules-parameters-specifying">30.3. Specifying Module Parameters</a></span></dt><dt><span class="section"><a href="#s1-modules-scsi">30.4. Storage parameters</a></span></dt><dt><span class="section"><a href="#s1-modules-ethernet">30.5. Ethernet Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-modules-multiple-eth">30.5.1. Using Multiple Ethernet Cards</a></span></dt><dt><span class="section"><a
href="#s2-modules-bonding">30.5.2. The Channel Bonding Module</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">30.6. Additional Resources</a></span></dt></dl></div><a id="id626918" class="indexterm"></a><a id="id582824" class="indexterm"></a><a id="id774429" class="indexterm"></a><a id="id665261" class="indexterm"></a><div class="para">
+ This chapter is provided to illustrate <span class="emphasis"><em>some</em></span> of the possible parameters available for common hardware device <em class="firstterm">drivers</em><sup>[<a id="id863402" href="#ftn.id863402" class="footnote">5</a>]</sup>, which under Fedora are called <em class="firstterm">kernel module</em>s . In most cases, the default parameters do work. However, there may be times when extra module parameters are necessary for a device to function properly or to override the module's default parameters for the device.
+ </div><div class="para">
+ During installation, Fedora uses a limited subset of device drivers to create a stable installation environment. Although the installation program supports installation on many different types of hardware, some drivers (including those for SCSI adapters and network adapters) are not included in the installation kernel. Rather, they must be loaded as modules by the user at boot time.
+ </div><div class="para">
+ Once installation is completed, support exists for a large number of devices through kernel modules.
+ </div><div class="section" title="30.1. Kernel Module Utilities" id="s1-kernel-module-utils"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-module-utils">30.1. Kernel Module Utilities</h2></div></div></div><a id="id1001922" class="indexterm"></a><div class="para">
+ A group of commands for managing kernel modules is available if the <code class="filename">module-init-tools</code>
+ <a id="id882158" class="indexterm"></a>
+ <a id="id871946" class="indexterm"></a>
+ package is installed. Use these commands to determine if a module has been loaded successfully or when trying different modules for a piece of new hardware.
+ </div><a id="id849841" class="indexterm"></a><a id="id949673" class="indexterm"></a><div class="para">
+ The command <code class="command">/sbin/lsmod</code> displays a list of currently loaded modules. For example:
+ </div><pre class="screen">
+~]$ <code class="command">/sbin/lsmod</code>
+Module Size Used by
+autofs4 25618 3
+sunrpc 231823 1
+bonding 115826 0
+ip6t_REJECT 4641 2
+nf_conntrack_ipv6 19623 2
+ip6table_filter 2895 1
+ip6_tables 19232 1 ip6table_filter
+ipv6 322766 61 bonding,ip6t_REJECT,nf_conntrack_ipv6
+dm_mirror 13723 0
+dm_region_hash 11920 1 dm_mirror
+dm_log 9944 2 dm_mirror,dm_region_hash
+uinput 8126 0
+sg 30478 0
+sr_mod 16066 0
+snd_ens1370 23085 4
+gameport 10783 1 snd_ens1370
+snd_rawmidi 22955 1 snd_ens1370
+cdrom 39833 1 sr_mod
+snd_seq 56461 0
+snd_seq_device 6634 2 snd_rawmidi,snd_seq
+snd_pcm 83399 1 snd_ens1370
+snd_timer 22304 4 snd_seq,snd_pcm
+snd 70077 12 snd_ens1370,snd_rawmidi,snd_seq,snd_seq_device,snd_pcm,snd_timer
+virtio_net 15937 0
+i2c_piix4 12707 0
+soundcore 7892 1 snd
+joydev 10514 0
+snd_page_alloc 8604 2 snd_ens1370,snd_pcm
+i2c_core 31338 1 i2c_piix4
+virtio_balloon 3599 0
+ext4 362885 2
+mbcache 7510 1 ext4
+jbd2 98427 1 ext4
+virtio_blk 5159 3
+ata_generic 3619 0
+pata_acpi 3675 0
+virtio_pci 6741 0
+virtio_ring 6026 1 virtio_pci
+virtio 4864 4 virtio_net,virtio_balloon,virtio_blk,virtio_pci
+ata_piix 22532 0
+dm_mod 73839 8 dm_mirror,dm_log</pre><div class="para">
+ The first column lists the names of modules; the second column lists the sizes of the modules, and the third column lists the use counts. The output from the <code class="command">/sbin/lsmod</code> command is less verbose and easier to read than the output of <code class="filename">cat /proc/modules</code>.
+ </div><a id="id623633" class="indexterm"></a><a id="id623646" class="indexterm"></a><div class="para">
+ To load a kernel module, use the <code class="command">/sbin/modprobe</code> command followed by the kernel module name. By default, <code class="command">modprobe</code> attempts to load the module from the <code class="filename">/lib/modules/<em class="replaceable"><code><kernel-version></code></em>/kernel/drivers/</code> subdirectories. There is a subdirectory for each type of module, such as the <code class="filename">net/</code> subdirectory for network interface drivers. Some kernel modules have module dependencies, meaning that other modules must be loaded first for it to load. The <code class="command">/sbin/modprobe</code> command checks for these dependencies and loads the module dependencies before loading the specified module.
+ </div><div class="para">
+ For example, the command:
+ </div><pre class="screen">~]# <code class="command">/sbin/modprobe e100</code>
+</pre><div class="para">
+ …first loads all module dependencies of the <code class="systemitem">e100</code> module before loading the <code class="systemitem">e100</code> module itself.
+ </div><div class="para">
+ To print to the screen all commands as <code class="command">/sbin/modprobe</code> executes them, use the <code class="option">-v</code> option. For example:
+ </div><pre class="screen">~]# <code class="command">/sbin/modprobe -v e100</code>
+</pre><div class="para">
+ Output similar to the following is displayed:
+ </div><pre class="screen">
+/sbin/insmod /lib/modules/2.6.9-5.EL/kernel/drivers/net/e100.ko
+Using /lib/modules/2.6.9-5.EL/kernel/drivers/net/e100.ko
+Symbol version prefix 'smp_'
+</pre><a id="id762107" class="indexterm"></a><div class="para">
+ The <code class="command">/sbin/insmod</code> command can also be used to load kernel modules; however, it does not resolve dependencies. You should thus always use <code class="command">/sbin/modprobe</code> instead of the <code class="command">insmod</code> command to load kernel modules.
+ </div><a id="id762137" class="indexterm"></a><a id="id728429" class="indexterm"></a><div class="para">
+ To unload kernel modules, use the <code class="command">/sbin/rmmod</code> command followed by the module name. The <code class="command">rmmod</code> utility only unloads modules that are not in use and that are not a dependency of other modules in use.
+ </div><div class="para">
+ For example, the command:
+ </div><pre class="screen">~]# <code class="command">/sbin/rmmod e100</code>
+</pre><div class="para">
+ …unloads the <code class="systemitem">e100</code> kernel module.
+ </div><div class="para">
+ Another useful kernel module utility is <code class="command">modinfo</code>. Use the command <code class="command">/sbin/modinfo</code> to display information about a kernel module. The general syntax is:
+ </div><pre class="screen">~]# <code class="command">/sbin/modinfo <em class="replaceable"><code>[<span class="optional">options</span>] </code></em> <em class="replaceable"><code><kernel_module_name></code></em> </code>
+</pre><div class="para">
+ Options include <code class="option">-d</code>, which displays a brief description of the module, and <code class="option">-p</code>, which lists the parameters the module supports. The <code class="command">modinfo</code> command is useful for listing information such as version, dependencies, paramater options, and aliases of modules.For a complete list of options, refer to the <code class="command">modinfo</code> man page.
+ </div></div><div class="section" title="30.2. Persistent Module Loading" id="s1-kernel-modules-persistant"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-modules-persistant">30.2. Persistent Module Loading</h2></div></div></div><a id="id654501" class="indexterm"></a><a id="id654513" class="indexterm"></a><div class="para">
+ Many kernel modules are loaded automatically at boot time, as <code class="command">/sbin/lsmod</code> shows. You can specify other modules to be loaded at boot time by creating a file in the <code class="filename">/etc/sysconfig/modules/</code> directory. You can use any name you like for the file that you create, but you must give it a <code class="filename">.modules</code> extension, and you must make it executable by running the following command:
+ </div><pre class="screen">modules]# <code class="command">chmod 755 <em class="replaceable"><code><filename.modules></code></em> </code>
+</pre><div class="note"><h2>No Need to Load Network and SCSI Modules</h2><div class="para">
+ Networking and SCSI modules do not generally need to be manually loaded as they have their own particular loading mechanisms.
+ </div></div><div class="para">
+ Here is a complete sample script named <code class="filename">bluez-uinput.modules</code> that loads the <code class="systemitem">uinput</code> module:
+ </div><div class="example" title="Example 30.1. /etc/sysconfig/modules/bluez-uinput.modules" id="ex-bluez-uinput.modules"><div class="example-contents"><pre class="programlisting">#!/bin/sh
+
+if [ ! -c /dev/input/uinput ] ; then
+ exec /sbin/modprobe uinput >/dev/null 2>&1
+fi</pre></div><h6>Example 30.1. /etc/sysconfig/modules/bluez-uinput.modules</h6></div><br class="example-break" /><div class="para">
+ The first line of any <code class="filename">.modules</code> file should be a shebang line that gives the location of the bash shell interpreter:
+ </div><pre class="programlisting">#!/bin/sh</pre><div class="para">
+ Like many configuration files, all <code class="filename">.modules</code> files are bash scripts. The if-conditional on line 3 tests to make sure that the /dev/input/uinput files does <span class="emphasis"><em>not</em></span> exist (the <span class="keycap"><strong>!</strong></span> symbol negates the condition), and, if that is the case, then executes <code class="command">/sbin/modprobe</code> with the name of the kernel module to load—<code class="systemitem">uinput</code> in this example. The remainder of the line simply redirects any output so that the <code class="command">modprobe</code> command is quiet.
+ </div></div><div class="section" title="30.3. Specifying Module Parameters" id="s1-modules-parameters-specifying"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-modules-parameters-specifying">30.3. Specifying Module Parameters</h2></div></div></div><a id="id787335" class="indexterm"></a><a id="id787351" class="indexterm"></a><div class="para">
+ In some situations, it may be necessary to supply parameters to a module
+ <a id="id787366" class="indexterm"></a>
+ as it is loaded for it to function properly.
+ </div><div class="para">
+ For instance, to enable full duplex at 100Mbps connection speed for an Intel Ether Express/100 card, load the <code class="filename">e100</code> driver with the <code class="option">e100_speed_duplex=4</code> option.
+ </div><div class="important"><h2>Important: kernel module parameters separated by commas</h2><div class="para">
+ When a module parameter has values separated by commas, do <span class="emphasis"><em>not</em></span> use spaces after the commas to separate the values.
+ </div></div></div><div class="section" title="30.4. Storage parameters" id="s1-modules-scsi"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-modules-scsi">30.4. Storage parameters</h2></div></div></div><a id="id1776818" class="indexterm"></a><a id="id1776830" class="indexterm"></a><div class="table" title="Table 30.1. Storage Module Parameters" id="tb-modules-scsiparameters"><div class="table-contents"><table summary="Storage Module Parameters" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th>
+ Hardware
+ </th><th>
+ Module
+ </th><th>
+ Parameters
+ </th></tr></thead><tbody><tr><td>
+ 3ware Storage Controller and 9000 series
+ </td><td>
+ <code class="filename">3w-xxxx.ko, 3w-9xxx.ko</code>
+ </td><td>
+ </td></tr><tr><td>
+ Adaptec Advanced Raid Products, Dell PERC2, 2/Si, 3/Si, 3/Di, HP NetRAID-4M, IBM ServeRAID, and ICP SCSI driver
+ </td><td>
+ <code class="filename">aacraid.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>nondasd</code></em> — Control scanning of hba for nondasd devices. 0=off, 1=on
+ </div>
+ <div class="para">
+ <em class="parameter"><code>dacmode</code></em> — Control whether dma addressing is using 64 bit DAC. 0=off, 1=on
+ </div>
+ <div class="para">
+ <em class="parameter"><code>commit</code></em> — Control whether a COMMIT_CONFIG is issued to the adapter for foreign arrays. This is typically needed in systems that do not have a BIOS. 0=off, 1=on
+ </div>
+ <div class="para">
+ <em class="parameter"><code>startup_timeout</code></em> — The duration of time in seconds to wait for adapter to have it's kernel up and running. This is typically adjusted for large systems that do not have a BIOS
+ </div>
+ <div class="para">
+ <em class="parameter"><code>aif_timeout</code></em> — The duration of time in seconds to wait for applications to pick up AIFs before deregistering them. This is typically adjusted for heavily burdened systems.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>numacb</code></em> — Request a limit to the number of adapter control blocks (FIB) allocated. Valid values are 512 and down. Default is to use suggestion from Firmware.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>acbsize</code></em> — Request a specific adapter control block (FIB) size. Valid values are 512, 2048, 4096 and 8192. Default is to use suggestion from Firmware.
+ </div>
+
+ </td></tr><tr><td>
+ Adaptec 28xx, R9xx, 39xx AHA-284x, AHA-29xx, AHA-394x, AHA-398x, AHA-274x, AHA-274xT, AHA-2842, AHA-2910B, AHA-2920C, AHA-2930/U/U2, AHA-2940/W/U/UW/AU/, U2W/U2/U2B/, U2BOEM, AHA-2944D/WD/UD/UWD, AHA-2950U2/W/B, AHA-3940/U/W/UW/, AUW/U2W/U2B, AHA-3950U2D, AHA-3985/U/W/UW, AIC-777x, AIC-785x, AIC-786x, AIC-787x, AIC-788x , AIC-789x, AIC-3860
+ </td><td>
+ <code class="filename">aic7xxx.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>verbose</code></em> — Enable verbose/diagnostic logging
+ </div>
+ <div class="para">
+ <em class="parameter"><code>allow_memio</code></em> — Allow device registers to be memory mapped
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — Bitmask of debug values to enable
+ </div>
+ <div class="para">
+ <em class="parameter"><code>no_probe</code></em> — Toggle EISA/VLB controller probing
+ </div>
+ <div class="para">
+ <em class="parameter"><code>probe_eisa_vl</code></em> — Toggle EISA/VLB controller probing
+ </div>
+ <div class="para">
+ <em class="parameter"><code>no_reset</code></em> — Supress initial bus resets
+ </div>
+ <div class="para">
+ <em class="parameter"><code>extended</code></em> — Enable extended geometry on all controllers
+ </div>
+ <div class="para">
+ <em class="parameter"><code>periodic_otag</code></em> — Send an ordered tagged transaction periodically to prevent tag starvation. This may be required by some older disk drives or RAID arrays.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>tag_info:<tag_str></code></em> — Set per-target tag depth
+ </div>
+ <div class="para">
+ <em class="parameter"><code>global_tag_depth:<int></code></em> — Global tag depth for every target on every bus
+ </div>
+ <div class="para">
+ <em class="parameter"><code>seltime:<int></code></em> — Selection Timeout (0/256ms,1/128ms,2/64ms,3/32ms)
+ </div>
+
+ </td></tr><tr><td>
+ IBM ServeRAID
+ </td><td>
+ <code class="filename">ips.ko</code>
+ </td><td>
+ </td></tr><tr><td>
+ LSI Logic MegaRAID Mailbox Driver
+ </td><td>
+ <code class="filename">megaraid_mbox.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>unconf_disks</code></em> — Set to expose unconfigured disks to kernel (default=0)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>busy_wait</code></em> — Max wait for mailbox in microseconds if busy (default=10)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>max_sectors</code></em> — Maximum number of sectors per IO command (default=128)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>cmd_per_lun</code></em> — Maximum number of commands per logical unit (default=64)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>fast_load</code></em> — Faster loading of the driver, skips physical devices! (default=0)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug_level</code></em> — Debug level for driver (default=0)
+ </div>
+
+ </td></tr><tr><td>
+ Emulex LightPulse Fibre Channel SCSI driver
+ </td><td>
+ <code class="filename">lpfc.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>lpfc_poll</code></em> — FCP ring polling mode control: 0 - none, 1 - poll with interrupts enabled 3 - poll and disable FCP ring interrupts
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_log_verbose</code></em> — Verbose logging bit-mask
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_lun_queue_depth</code></em> — Max number of FCP commands we can queue to a specific LUN
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_hba_queue_depth</code></em> — Max number of FCP commands we can queue to a lpfc HBA
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_scan_down</code></em> — Start scanning for devices from highest ALPA to lowest
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_nodev_tmo</code></em> — Seconds driver will hold I/O waiting for a device to come back
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_topology</code></em> — Select Fibre Channel topology
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_link_speed</code></em> — Select link speed
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_fcp_class</code></em> — Select Fibre Channel class of service for FCP sequences
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_use_adisc</code></em> — Use ADISC on rediscovery to authenticate FCP devices
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_ack0</code></em> — Enable ACK0 support
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_cr_delay</code></em> — A count of milliseconds after which an interrupt response is generated
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_cr_count</code></em> — A count of I/O completions after which an interrupt response is generated
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_multi_ring_support</code></em> — Determines number of primary SLI rings to spread IOCB entries across
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_fdmi_on</code></em> — Enable FDMI support
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_discovery_threads</code></em> — Maximum number of ELS commands during discovery
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_max_luns</code></em> — Maximum allowed LUN
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_poll_tmo</code></em> — Milliseconds driver will wait between polling FCP ring
+ </div>
+
+ </td></tr><tr><td>
+ HP Smart Array
+ </td><td>
+ cciss.ko
+ </td><td>
+ </td></tr><tr><td>
+ LSI Logic MPT Fusion
+ </td><td>
+ mptbase.ko mptctl.ko mptfc.ko mptlan.ko mptsas.ko mptscsih.ko mptspi.ko
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>mpt_msi_enable</code></em> — MSI Support Enable
+ </div>
+ <div class="para">
+ <em class="parameter"><code>mptfc_dev_loss_tmo</code></em> — Initial time the driver programs the transport to wait for an rport to return following a device loss event.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>mpt_pt_clear</code></em> — Clear persistency table
+ </div>
+ <div class="para">
+ <em class="parameter"><code>mpt_saf_te</code></em> — Force enabling SEP Processor
+ </div>
+
+ </td></tr><tr><td>
+ QLogic Fibre Channel Driver
+ </td><td>
+ qla2xxx.ko
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>ql2xlogintimeout</code></em> — Login timeout value in seconds.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>qlport_down_retry</code></em> — Maximum number of command retries to a port that returns a PORT-DOWN status
+ </div>
+ <div class="para">
+ <em class="parameter"><code>ql2xplogiabsentdevice</code></em> — Option to enable PLOGI to devices that are not present after a Fabric scan.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>ql2xloginretrycount</code></em> — Specify an alternate value for the NVRAM login retry count.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>ql2xallocfwdump</code></em> — Option to enable allocation of memory for a firmware dump during HBA initialization. Default is 1 - allocate memory.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>extended_error_logging</code></em> — Option to enable extended error logging.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>ql2xfdmienable</code></em> — Enables FDMI registratons.
+ </div>
+
+ </td></tr><tr><td>
+ NCR, Symbios and LSI 8xx and 1010
+ </td><td>
+ sym53c8xx
+
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>cmd_per_lun</code></em> — The maximum number of tags to use by default
+ </div>
+ <div class="para">
+ <em class="parameter"><code>tag_ctrl</code></em> — More detailed control over tags per LUN
+ </div>
+ <div class="para">
+ <em class="parameter"><code>burst</code></em> — Maximum burst. 0 to disable, 255 to read from registers
+ </div>
+ <div class="para">
+ <em class="parameter"><code>led</code></em> — Set to 1 to enable LED support
+ </div>
+ <div class="para">
+ <em class="parameter"><code>diff</code></em> — 0 for no differential mode, 1 for BIOS, 2 for always, 3 for not GPIO3
+ </div>
+ <div class="para">
+ <em class="parameter"><code>irqm</code></em> — 0 for open drain, 1 to leave alone, 2 for totem pole
+ </div>
+ <div class="para">
+ <em class="parameter"><code>buschk</code></em> — 0 to not check, 1 for detach on error, 2 for warn on error
+ </div>
+ <div class="para">
+ <em class="parameter"><code>hostid</code></em> — The SCSI ID to use for the host adapters
+ </div>
+ <div class="para">
+ <em class="parameter"><code>verb</code></em> — 0 for minimal verbosity, 1 for normal, 2 for excessive
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — Set bits to enable debugging
+ </div>
+ <div class="para">
+ <em class="parameter"><code>settle</code></em> — Settle delay in seconds. Default 3
+ </div>
+ <div class="para">
+ <em class="parameter"><code>nvram</code></em> — Option currently not used
+ </div>
+ <div class="para">
+ <em class="parameter"><code>excl</code></em> — List ioport addresses here to prevent controllers from being attached
+ </div>
+ <div class="para">
+ <em class="parameter"><code>safe</code></em> — Set other settings to a "safe mode"
+ </div>
+
+ </td></tr></tbody></table></div><h6>Table 30.1. Storage Module Parameters</h6></div><br class="table-break" /></div><div class="section" title="30.5. Ethernet Parameters" id="s1-modules-ethernet"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-modules-ethernet">30.5. Ethernet Parameters</h2></div></div></div><a id="id1027951" class="indexterm"></a><a id="id1027963" class="indexterm"></a><a id="id1027975" class="indexterm"></a><a id="id1027987" class="indexterm"></a><div class="para">
+ Most modern Ethernet-based network interface cards (NICs), do not require module parameters to alter settings. Instead, they can be configured using <code class="command">ethtool</code> or <code class="command">mii-tool</code>. Only after these tools fail to work should module parameters be adjusted. Module paramaters can be viewed using the <code class="command">modinfo</code> command.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ For information about using these tools, consult the man pages for <code class="command">ethtool</code>, <code class="command">mii-tool</code>, and <code class="command">modinfo</code>.
+ </div></div><div class="table" title="Table 30.2. Ethernet Module Parameters" id="tb-modules-ethernet"><div class="table-contents"><table summary="Ethernet Module Parameters" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th>
+ Hardware
+ </th><th>
+ Module
+ </th><th>
+ Parameters
+ </th></tr></thead><tbody><tr><td>
+ 3Com EtherLink PCI III/XL Vortex (3c590, 3c592, 3c595, 3c597) Boomerang (3c900, 3c905, 3c595)
+ </td><td>
+ <code class="filename">3c59x.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — 3c59x debug level (0-6)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>options</code></em> — 3c59x: Bits 0-3: media type, bit 4: bus mastering, bit 9: full duplex
+ </div>
+ <div class="para">
+ <em class="parameter"><code>global_options</code></em> — 3c59x: same as options, but applies to all NICs if options is unset
+ </div>
+ <div class="para">
+ <em class="parameter"><code>full_duplex</code></em> — 3c59x full duplex setting(s) (1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>global_full_duplex</code></em> — 3c59x: same as full_duplex, but applies to all NICs if full_duplex is unset
+ </div>
+ <div class="para">
+ <em class="parameter"><code>hw_checksums</code></em> — 3c59x Hardware checksum checking by adapter(s) (0-1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>flow_ctrl</code></em> — 3c59x 802.3x flow control usage (PAUSE only) (0-1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>enable_wol</code></em> — 3c59x: Turn on Wake-on-LAN for adapter(s) (0-1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>global_enable_wol</code></em> — 3c59x: same as enable_wol, but applies to all NICs if enable_wol is unset
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — 3c59x copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>max_interrupt_work</code></em> — 3c59x maximum events handled per interrupt
+ </div>
+ <div class="para">
+ <em class="parameter"><code>compaq_ioaddr</code></em> — 3c59x PCI I/O base address (Compaq BIOS problem workaround)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>compaq_irq</code></em> — 3c59x PCI IRQ number (Compaq BIOS problem workaround)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>compaq_device_id</code></em> — 3c59x PCI device ID (Compaq BIOS problem workaround)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>watchdog</code></em> — 3c59x transmit timeout in milliseconds
+ </div>
+ <div class="para">
+ <em class="parameter"><code>global_use_mmio</code></em> — 3c59x: same as use_mmio, but applies to all NICs if options is unset
+ </div>
+ <div class="para">
+ <em class="parameter"><code>use_mmio</code></em> — 3c59x: use memory-mapped PCI I/O resource (0-1)
+ </div>
+
+ </td></tr><tr><td>
+ RTL8139, SMC EZ Card Fast Ethernet, RealTek cards using RTL8129, or RTL8139 Fast Ethernet chipsets
+ </td><td>
+ <code class="filename">8139too.ko</code>
+ </td><td>
+ </td></tr><tr><td>
+ Broadcom 4400 10/100 PCI ethernet driver
+ </td><td>
+ <code class="filename">b44.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>b44_debug</code></em> — B44 bitmapped debugging message enable value
+ </div>
+
+ </td></tr><tr><td>
+ Broadcom NetXtreme II BCM5706/5708 Driver
+ </td><td>
+ <code class="filename">bnx2.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>disable_msi</code></em> — Disable Message Signaled Interrupt (MSI)
+ </div>
+
+ </td></tr><tr><td>
+ Intel Ether Express/100 driver
+ </td><td>
+ <code class="filename">e100.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — Debug level (0=none,...,16=all)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>eeprom_bad_csum_allow</code></em> — Allow bad eeprom checksums
+ </div>
+
+ </td></tr><tr><td>
+ Intel EtherExpress/1000 Gigabit
+ </td><td>
+ <code class="filename">e1000.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>TxDescriptors</code></em> — Number of transmit descriptors
+ </div>
+ <div class="para">
+ <em class="parameter"><code>RxDescriptors</code></em> — Number of receive descriptors
+ </div>
+ <div class="para">
+ <em class="parameter"><code>Speed</code></em> — Speed setting
+ </div>
+ <div class="para">
+ <em class="parameter"><code>Duplex</code></em> — Duplex setting
+ </div>
+ <div class="para">
+ <em class="parameter"><code>AutoNeg</code></em> — Advertised auto-negotiation setting
+ </div>
+ <div class="para">
+ <em class="parameter"><code>FlowControl</code></em> — Flow Control setting
+ </div>
+ <div class="para">
+ <em class="parameter"><code>XsumRX</code></em> — Disable or enable Receive Checksum offload
+ </div>
+ <div class="para">
+ <em class="parameter"><code>TxIntDelay</code></em> — Transmit Interrupt Delay
+ </div>
+ <div class="para">
+ <em class="parameter"><code>TxAbsIntDelay</code></em> — Transmit Absolute Interrupt Delay
+ </div>
+ <div class="para">
+ <em class="parameter"><code>RxIntDelay</code></em> — Receive Interrupt Delay
+ </div>
+ <div class="para">
+ <em class="parameter"><code>RxAbsIntDelay</code></em> — Receive Absolute Interrupt Delay
+ </div>
+ <div class="para">
+ <em class="parameter"><code>InterruptThrottleRate</code></em> — Interrupt Throttling Rate
+ </div>
+ <div class="para">
+ <em class="parameter"><code>SmartPowerDownEnable</code></em> — Enable PHY smart power down
+ </div>
+ <div class="para">
+ <em class="parameter"><code>KumeranLockLoss</code></em> — Enable Kumeran lock loss workaround
+ </div>
+
+ </td></tr><tr><td>
+ Myricom 10G driver (10GbE)
+ </td><td>
+ <code class="filename">myri10ge.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_fw_name</code></em> — Firmware image name
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_ecrc_enable</code></em> — Enable Extended CRC on PCI-E
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_max_intr_slots</code></em> — Interrupt queue slots
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_small_bytes</code></em> — Threshold of small packets
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_msi</code></em> — Enable Message Signalled Interrupts
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_intr_coal_delay</code></em> — Interrupt coalescing delay
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_flow_control</code></em> — Pause parameter
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_deassert_wait</code></em> — Wait when deasserting legacy interrupts
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_force_firmware</code></em> — Force firmware to assume aligned completions
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_skb_cross_4k</code></em> — Can a small skb cross a 4KB boundary?
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_initial_mtu</code></em> — Initial MTU
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_napi_weight</code></em> — Set NAPI weight
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_watchdog_timeout</code></em> — Set watchdog timeout
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_max_irq_loops</code></em> — Set stuck legacy IRQ detection threshold
+ </div>
+
+ </td></tr><tr><td>
+ NatSemi DP83815 Fast Ethernet
+ </td><td>
+ <code class="filename">natsemi.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>mtu</code></em> — DP8381x MTU (all boards)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — DP8381x default debug level
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — DP8381x copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>options</code></em> — DP8381x: Bits 0-3: media type, bit 17: full duplex
+ </div>
+ <div class="para">
+ <em class="parameter"><code>full_duplex</code></em> — DP8381x full duplex setting(s) (1)
+ </div>
+
+ </td></tr><tr><td>
+ AMD PCnet32 and AMD PCnetPCI
+ </td><td>
+ <code class="filename">pcnet32.ko</code>
+ </td><td>
+ </td></tr><tr><td>
+ PCnet32 and PCnetPCI
+ </td><td>
+ <code class="filename">pcnet32.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — pcnet32 debug level
+ </div>
+ <div class="para">
+ <em class="parameter"><code>max_interrupt_work</code></em> — pcnet32 maximum events handled per interrupt
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — pcnet32 copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>tx_start_pt</code></em> — pcnet32 transmit start point (0-3)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>pcnet32vlb</code></em> — pcnet32 Vesa local bus (VLB) support (0/1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>options</code></em> — pcnet32 initial option setting(s) (0-15)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>full_duplex</code></em> — pcnet32 full duplex setting(s) (1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>homepna</code></em> — pcnet32 mode for 79C978 cards (1 for HomePNA, 0 for Ethernet, default Ethernet
+ </div>
+
+ </td></tr><tr><td>
+ RealTek RTL-8169 Gigabit Ethernet driver
+ </td><td>
+ <code class="filename">r8169.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>media</code></em> — force phy operation. Deprecated by ethtool (8).
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — Copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>use_dac</code></em> — Enable PCI DAC. Unsafe on 32 bit PCI slot.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — Debug verbosity level (0=none, ..., 16=all)
+ </div>
+
+ </td></tr><tr><td>
+ Neterion Xframe 10GbE Server Adapter
+ </td><td>
+ <code class="filename">s2io.ko</code>
+ </td><td>
+ </td></tr><tr><td>
+ SIS 900/701G PCI Fast Ethernet
+ </td><td>
+ <code class="filename">sis900.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>multicast_filter_limit</code></em> — SiS 900/7016 maximum number of filtered multicast addresses
+ </div>
+ <div class="para">
+ <em class="parameter"><code>max_interrupt_work</code></em> — SiS 900/7016 maximum events handled per interrupt
+ </div>
+ <div class="para">
+ <em class="parameter"><code>sis900_debug</code></em> — SiS 900/7016 bitmapped debugging message level
+ </div>
+
+ </td></tr><tr><td>
+ Adaptec Starfire Ethernet driver
+ </td><td>
+ <code class="filename">starfire.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>max_interrupt_work</code></em> — Maximum events handled per interrupt
+ </div>
+ <div class="para">
+ <em class="parameter"><code>mtu</code></em> — MTU (all boards)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — Debug level (0-6)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — Copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>intr_latency</code></em> — Maximum interrupt latency, in microseconds
+ </div>
+ <div class="para">
+ <em class="parameter"><code>small_frames</code></em> — Maximum size of receive frames that bypass interrupt latency (0,64,128,256,512)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>options</code></em> — Deprecated: Bits 0-3: media type, bit 17: full duplex
+ </div>
+ <div class="para">
+ <em class="parameter"><code>full_duplex</code></em> — Deprecated: Forced full-duplex setting (0/1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>enable_hw_cksum</code></em> — Enable/disable hardware cksum support (0/1)
+ </div>
+
+ </td></tr><tr><td>
+ Broadcom Tigon3
+ </td><td>
+ <code class="filename">tg3.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>tg3_debug</code></em> — Tigon3 bitmapped debugging message enable value
+ </div>
+
+ </td></tr><tr><td>
+ ThunderLAN PCI
+ </td><td>
+ <code class="filename">tlan.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>aui</code></em> — ThunderLAN use AUI port(s) (0-1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>duplex</code></em> — ThunderLAN duplex setting(s) (0-default, 1-half, 2-full)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>speed</code></em> — ThunderLAN port speen setting(s) (0,10,100)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — ThunderLAN debug mask
+ </div>
+ <div class="para">
+ <em class="parameter"><code>bbuf</code></em> — ThunderLAN use big buffer (0-1)
+ </div>
+
+ </td></tr><tr><td>
+ Digital 21x4x Tulip PCI Ethernet cards SMC EtherPower 10 PCI(8432T/8432BT) SMC EtherPower 10/100 PCI(9332DST) DEC EtherWorks 100/10 PCI(DE500-XA) DEC EtherWorks 10 PCI(DE450) DEC QSILVER's, Znyx 312 etherarray Allied Telesis LA100PCI-T Danpex EN-9400, Cogent EM110
+ </td><td>
+ <code class="filename">tulip.ko</code>
+ </td><td>
+ <em class="parameter"><code>io</code></em> <em class="replaceable"><code>io_port</code></em>
+ </td></tr><tr><td>
+ VIA Rhine PCI Fast Ethernet cards with either the VIA VT86c100A Rhine-II PCI or 3043 Rhine-I D-Link DFE-930-TX PCI 10/100
+ </td><td>
+ <code class="filename">via-rhine.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>max_interrupt_work</code></em> — VIA Rhine maximum events handled per interrupt
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — VIA Rhine debug level (0-7)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — VIA Rhine copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>avoid_D3</code></em> — Avoid power state D3 (work-around for broken BIOSes)
+ </div>
+
+ </td></tr></tbody></table></div><h6>Table 30.2. Ethernet Module Parameters</h6></div><br class="table-break" /><div class="section" title="30.5.1. Using Multiple Ethernet Cards" id="s2-modules-multiple-eth"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-modules-multiple-eth">30.5.1. Using Multiple Ethernet Cards</h3></div></div></div><a id="id911193" class="indexterm"></a><a id="id911209" 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="30.5.2. The Channel Bonding Module" id="s2-modules-bonding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-modules-bonding">30.5.2. The Channel Bonding Module</h3></div></div></div><a id="id949839" class="indexterm"></a><a id="id949851" class="indexterm"></a><div class="para">
+ Fedora allows administrators to bind NICs
+ <a id="id949865" class="indexterm"></a>
+ together into a single channel using the <code class="filename">bonding</code> kernel module
+ <a id="id949881" class="indexterm"></a>
+ and a special network interface, called a <em class="firstterm">channel bonding interface</em> <a id="id868380" class="indexterm"></a>
+ <a id="id868391" class="indexterm"></a>
+ . Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
+ </div><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="30.5.2.1. Bonding Module Directives">Section 30.5.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="30.5.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">30.5.2.1. Bonding Module Directives</h4></div></div></div><a id="id858513" class="indexterm"></a><a id="id858525" 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
+ <a id="id858559" class="indexterm"></a>
+ <a id="id858571" class="indexterm"></a>
+ 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> <a id="id816662" class="indexterm"></a>
+ <a id="id816674" class="indexterm"></a>
+ 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 <code class="filename">/sys</code>.
+ </div><div class="para">
+ All bonded interfaces can be configured dynamically by interacting with and manipulating files under the <code class="filename">/sys/class/net/</code> directory. After you have created a channel bonding interface file such as <code class="filename">ifcfg-bond0</code> and inserted <em class="parameter"><code>SLAVE=bond0</code></em> directives in the bonded interfaces 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 then proceed to testing and determining the best parameters for your bonded 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">~]# ifconfig bond0 up</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">~]# ifconfig
+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">~]# cat /sys/class/net/bonding_masters
+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">~]# ifconfig bond0 down</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">~]# echo 1000 > /sys/class/net/bond0/bonding/miimon</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">~]# echo 6 > /sys/class/net/bond0/bonding/mode</pre><div class="para">
+ ...or, using the name of the mode:
+ </div><pre class="screen">~]# echo balance-alb > /sys/class/net/bond0/bonding/mode</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 bonded 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 bonded 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 is a list of available channel bonding module parameters for the <code class="filename">bonding</code> module. For more in-depth information on configuring channel bonding and the exhaustive list of bonding module parameters, install the <span class="package">kernel-doc</span> package (refer to <a class="xref" href="#s1-kernel-modules-additional-resources" title="30.6. Additional Resources">Section 30.6, “Additional Resources”</a>) and then locate and reference the <code class="filename">bonding.txt</code> file:
+ </div><pre class="screen">~]# yum -y install kernel-doc
+~]# gedit $(rpm -ql kernel-doc |grep -i bonding.txt) &</pre><div class="variablelist" title="Bonding Interface Parameters"><h6>Bonding Interface Parameters</h6><dl><dt><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"><h2>Important</h2><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 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><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><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><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><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><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><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">~]# ethtool <em class="replaceable"><code><interface_name></code></em> | grep "Link detected:"</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"><h2>Important</h2><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></dd><dt><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><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 option affects only the active-backup mode.
+ </div></dd><dt><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><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 option 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><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><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"><h2>Tip</h2><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></dd><dt><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 option 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="30.6. 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">30.6. Additional Resources</h2></div></div></div><div class="para">
+ For more information on kernel modules and their utilities, refer to the following resources.
+ </div><div class="variablelist"><dl><dt><span class="term">man pages</span></dt><dd><div class="para">
+ <code class="command">lsmod</code>, <code class="command">modprobe</code>, <code class="command">mmod</code>, <code class="command">modinfo</code> — Refer to the man pages for these commands to learn how to display module information and manipulate modules.
+ </div></dd><dt><span class="term"> <span class="package">kernel-doc</span> package documentation</span></dt><dd><div class="para">
+ For in-depth documentation on the Fedora kernel, kernel modules and their parameters, install the <span class="package">kernel-doc</span> package:
+ </div><pre class="screen">~]# <code class="command">yum install kernel-doc</code>
+</pre><div class="para">
+ This package installs documentation under <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation</code>.
+ </div></dd><dt><span class="term"> <em class="citetitle">Linux Loadable Kernel Module HOWTO</em> </span></dt><dd><div class="para">
+ <a href="http://tldp.org/HOWTO/Module-HOWTO/">http://tldp.org/HOWTO/Module-HOWTO/</a> — The <em class="citetitle">Linux Loadable Kernel Module HOWTO</em> from the Linux Documentation Project.
+ </div></dd></dl></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id863402" href="#id863402" class="para">5</a>] </sup>
+ A <em class="firstterm">driver</em> is software that enables Linux to use a particular hardware device. Without a driver, the kernel cannot communicate with attached devices.
+ </p></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 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 Deployment Guide</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><div class="index" title="Index" id="id735310"><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>global options, <a class="indexterm" href="#s3-email-mda-fetchmail-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><dt> .procmailrc , <a class="indexterm" href="#s2-email-procmail-configuration">Procmail Configuration</a></dt><dt> /dev/oprofile/ , <a class="indexterm" href="#s1-oprofile-dev-oprofile">Understanding /dev/oprofile/ </a></dt><dt> /dev/shm , <a class="indexterm" href="#s1-sysinfo-filesystems">File Systems</
a></dt><dt> /etc/httpd/conf/httpd.conf , <a class="indexterm" href="#s1-apache-config-ui">Apache HTTP Server Configuration</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="#id729711">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/cron , <a class="indexterm" href="#s2-autotasks-cron-configuring">Configuring Cron Tasks</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt> (see OProfile)</dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>Access Control</dt><dd><dl><dt>configuring in SSSD, <a class="indexterm" href="#id623093">Configuring Access Control</a></dt><dt>in SSSD, rules, <a class="indexterm" href="#id623093">Configuring Access Control</a></dt></dl></dd><dt> AccessFileName </dt><dd><dl><dt>Apache configuratio
n directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Action </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddDescription </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddEncoding </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddHandler </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddIcon </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddIconByEncoding </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">Gen
eral Configuration Tips</a></dt></dl></dd><dt> AddIconByType </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</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> AddLanguage </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddType </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Alias </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Allow </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Confi
guration Tips</a></dt></dl></dd><dt> AllowOverride </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>Apache (see Apache HTTP Server)</dt><dt>Apache HTTP Server</dt><dd><dl><dt>1.3</dt><dd><dl><dt>migration to 2.0, <a class="indexterm" href="#s3-httpd-v2-mig">Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></dt></dl></dd><dt>2.0</dt><dd><dl><dt>migration from 1.3, <a class="indexterm" href="#s3-httpd-v2-mig">Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></dt><dt>MPM specific directives, <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt>2.2</dt><dd><dl><dt>2.0, <a class="indexterm" href="#s1-httpd-mig">Migrating Apache HTTP Server Configuration Files</a></dt><dt>features of, <a class="indexterm" href="#s2-httpd-v2-features">Features of Apache HTTP Server 2.2</a></dt><dt>migration from 2.0, <a c
lass="indexterm" href="#s1-httpd-v22-mig">Migrating Apache HTTP Server 2.0 Configuration Files</a></dt><dt>migration to 2.2, <a class="indexterm" href="#s1-httpd-mig">Migrating Apache HTTP Server Configuration Files</a></dt></dl></dd><dt>additional resources, <a class="indexterm" href="#s1-apache-additional-resources">Additional Resources</a></dt><dd><dl><dt>useful websites, <a class="indexterm" href="#s2-apache-additional-resources-web">Useful Websites</a></dt></dl></dd><dt>configuration, <a class="indexterm" href="#s1-apache-config">Configuration Directives in httpd.conf </a></dt><dt>introducing, <a class="indexterm" href="#ch-The_Apache_HTTP_Server">The Apache HTTP Server</a></dt><dt>log files</dt><dd><dl><dt> /var/log/httpd/error_log , <a class="indexterm" href="#s1-apache-config">Configuration Directives in httpd.conf </a></dt><dt>combined log file format, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt>format of, <a class="indexterm"
href="#s2-apache-tips">General Configuration Tips</a></dt><dt>troubleshooting with, <a class="indexterm" href="#s1-apache-config">Configuration Directives in httpd.conf </a>, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt>using log analyzer tools with, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>migration to 2.0, <a class="indexterm" href="#s3-httpd-v2-mig">Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></dt><dd><dl><dt>bind addresses and ports, <a class="indexterm" href="#s3-httpd-v2-mig-port">Interface and Port Binding</a></dt><dt>content negotiation, <a class="indexterm" href="#s3-httpd-mig-main-cont">Content Negotiation</a></dt><dt>directory indexing, <a class="indexterm" href="#s3-httpd-mig-main-dirindex">Directory Indexing</a></dt><dt>DSO Support, <a class="indexterm" href="#s3-httpd-v2-mig-dso">Dynamic Shared Object (DSO) Support</a></dt><dt>error documents, <a class="
indexterm" href="#s3-httpd-mig-main-error">Error Documents</a></dt><dt>LDAP, <a class="indexterm" href="#s3-httpd-v2-mig-mod-ldapz">The mod_authz_ldap Module</a></dt><dt>logging, <a class="indexterm" href="#s3-httpd-mig-main-log">Logging</a></dt><dt>module system changes, <a class="indexterm" href="#s2-httpd-v2-mig-mod">Modules and Apache HTTP Server 2.0</a></dt><dt> mod_auth_db , <a class="indexterm" href="#s3-httpd-v2-mig-mod-dbm">The mod_auth_dbm and mod_auth_db Modules</a></dt><dt> mod_auth_dbm , <a class="indexterm" href="#s3-httpd-v2-mig-mod-dbm">The mod_auth_dbm and mod_auth_db Modules</a></dt><dt> mod_include , <a class="indexterm" href="#s3-httpd-v2-mig-mod-include">The mod_include Module</a></dt><dt> mod_perl , <a class="indexterm" href="#s3-httpd-v2-mig-mod-perl">The mod_perl Module</a></dt><dt> mod_proxy , <a class="indexterm" href="#s3-httpd-v2-mig-mod-proxy">The mod_proxy Module</a></dt><dt> mod_ssl , <a class="indexterm" href="#s3-httpd-v2-mig-mod-ssl">The mod
_ssl Module</a></dt><dt>PHP, <a class="indexterm" href="#s3-httpd-v2-mig-mod-php">PHP</a></dt><dt>removed directives, <a class="indexterm" href="#s3-httpd-v2-mig-other">Other Global Environment Changes</a></dt><dt>server-pool size, <a class="indexterm" href="#s3-httpd-v2-mig-pool">Server-Pool Size Regulation</a></dt><dt> SuexecUserGroup , <a class="indexterm" href="#s3-httpd-v2-mig-mod-suexec">The suexec Module</a>, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> UserDir directive, <a class="indexterm" href="#s3-httpd-mig-main-map"> UserDir Mapping</a></dt><dt>virtual host configuration, <a class="indexterm" href="#s2-httpd-v2-mig-virtual">Virtual Host Configuration</a></dt></dl></dd><dt>migration to 2.2, <a class="indexterm" href="#s1-httpd-mig">Migrating Apache HTTP Server Configuration Files</a></dt><dt>Multi-Processing Modules</dt><dd><dl><dt>activating worker MPM, <a class="indexterm" href="#s3-httpd-v2-mig-pool">Server-Pool Size Regu
lation</a></dt><dt> prefork , <a class="indexterm" href="#s3-httpd-v2-mig-pool">Server-Pool Size Regulation</a></dt><dt> worker , <a class="indexterm" href="#s3-httpd-v2-mig-pool">Server-Pool Size Regulation</a></dt></dl></dd><dt>reloading, <a class="indexterm" href="#s1-apache-startstop">Starting and Stopping httpd </a></dt><dt>restarting, <a class="indexterm" href="#s1-apache-startstop">Starting and Stopping httpd </a></dt><dt>running without security, <a class="indexterm" href="#s1-apache-virtualhosts">Virtual Hosts</a></dt><dt>securing, <a class="indexterm" href="#s2-secureserver-overview-certs">An Overview of Certificates and Security</a></dt><dt>server status reports, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt>starting, <a class="indexterm" href="#s1-apache-startstop">Starting and Stopping httpd </a></dt><dt>stopping, <a class="indexterm" href="#s1-apache-startstop">Starting and Stopping httpd </a></dt><dt>troubleshooting, <a cla
ss="indexterm" href="#s1-apache-config">Configuration Directives in httpd.conf </a></dt></dl></dd><dt>Apache HTTP Server Keys</dt><dd><dl><dt>use new keys, <a class="indexterm" href="#s1-use-new-key">How to configure the server to use the new key</a></dt></dl></dd><dt>APXS Apache utility, <a class="indexterm" href="#s1-apache-addmods">Adding Modules</a></dt><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><d
t> 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="#s1-ldap-pam">Configuring a System to Authenticate Using OpenLDAP</a>, <a class="indexterm" href="#s2-ldap-pamd">PAM and LDAP</a>, <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>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, <a class="indexter
m" href="#s1-bind-additional-resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-bind-installed-docs">Installed Documentation</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 files</dt><dd><dl><dt> /etc/named.conf , <a class="indexterm" href="#s2-bind-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="#s1-bind-namedconf"> /etc/named.conf </a></dt><dt> /var/named/ directory, <a class="indexterm" href="#s2-bind-introduction-bind">BIND as a Nameserver</a></dt><dt>BIND as a Nameserver, <a class="indexterm" href="#s2-bind-introduction-bind">BIND as a Nameserver</a></dt><dt>zone files, <a class="indexterm" href="#s1-bind-zone">Zone Files</a></dt></dl></dd><dt>configuration of</dt><dd><dl><dt>reverse name resolution, <a clas
s="indexterm" href="#s2-bind-configuration-zone-reverse">Reverse Name Resolution Zone Files</a></dt><dt>zone file directives, <a class="indexterm" href="#s2-bind-zone-directives">Zone File Directives</a></dt><dt>zone file examples, <a class="indexterm" href="#s2-bind-zone-examples">Example Zone File</a></dt><dt>zone file resource records, <a class="indexterm" href="#s3-bind-zone-rr">Zone File Resource Records</a></dt><dt> zone statements sample, <a class="indexterm" href="#s3-bind-configuration-named-zone">Sample zone Statements</a></dt></dl></dd><dt>features, <a class="indexterm" href="#s1-bind-features">Advanced Features of BIND</a></dt><dd><dl><dt>DNS enhancements, <a class="indexterm" href="#s2-bind-features-protocol">DNS Protocol Enhancements</a></dt><dt>IPv6, <a class="indexterm" href="#s2-bind-features-ipv6">IP version 6</a></dt><dt>multiple views, <a class="indexterm" href="#s2-bind-features-views">Multiple Views</a></dt><dt>security, <a class="indexterm" href="#s2-b
ind-features-security">Security</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="#ch-The_BIND_DNS_Server">The BIND DNS Server</a>, <a class="indexterm" href="#s1-bind-introduction">Introduction to DNS</a></dt><dt> named daemon, <a class="indexterm" href="#s2-bind-introduction-bind">BIND as a Nameserver</a></dt><dt>nameserver</dt><dd><dl><dt>definition of, <a class="indexterm" href="#s1-bind-introduction">Introduction to DNS</a></dt></dl></dd><dt>nameserver types</dt><dd><dl><dt>caching-only, <a class="indexterm" href="#s2-bind-introduction-nameservers">Nameserver Types</a></dt><dt>forwarding, <a class="indexterm" href="#s2-bind-introduction-nameservers">Nameserver Types</a></dt><dt>master, <a class="indexterm" href="#s2-bind-introduction-nameservers">Nameserver Types</a></dt><dt>slave, <a class="indexterm" href="#s2-bind-introduction-nameservers">Nameserver Types</a></dt></dl></dd><dt> rndc program, <a class="indexterm" href="#s1-bind-rndc">Using rndc </a></dt><
dd><dl><dt> /etc/rndc.conf , <a class="indexterm" href="#s2-bind-rndc-configuration-rndcconf">Configuring /etc/rndc.conf </a></dt><dt>command line options, <a class="indexterm" href="#s2-bind-rndc-options">Command Line Options</a></dt><dt>configuring keys, <a class="indexterm" href="#s2-bind-rndc-configuration-rndcconf">Configuring /etc/rndc.conf </a></dt><dt>configuring named to use, <a class="indexterm" href="#s2-bind-rndc-configuration-namedconf">Configuring /etc/named.conf </a></dt></dl></dd><dt>root nameserver</dt><dd><dl><dt>definition of, <a class="indexterm" href="#s1-bind-introduction">Introduction to DNS</a></dt></dl></dd><dt>zones</dt><dd><dl><dt>definition of, <a class="indexterm" href="#s2-bind-introduction-zones">Nameserver Zones</a></dt></dl></dd></dl></dd><dt>bind</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>related books, <a class="indexterm" href="#s2-bind-related-books">Related Books</a></dt></dl></dd></dl></dd><dt>block devices, <a class="indexter
m" 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 kernel module</dt><dd><dl><dt>sysfs, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><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><dt> BrowserMatch </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>CA (see secure server)</dt><dt>cache directives for Apache, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> CacheNegotiatedDocs </dt><dd><dl><dt>Apache configuration dire
ctive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>caching-only nameserver (see BIND)</dt><dt>CGI scripts</dt><dd><dl><dt>allowing execution outside cgi-bin , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt>outside the ScriptAlias , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</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>bonding directives, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt><dt>bonding options, <a class="indexterm" href="#s2-modules-bonding">The Channel Bonding Module</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><dt>(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>command line options</dt><dd><dl><dt>printing from, <a class="indexterm" href="#s1-printing-managing">Managing Print Jobs</a></dt></dl></dd><dt>configuration</dt><dd><dl><dt>Apache HTTP Server, <a class="indexterm" href="#s1-apache-config">Configuration Directives in httpd.conf </a></dt><dt>virtual hosts, <a class="indexterm" href="#s1-apache-virtualhosts">Virtual Hosts</a></dt></dl></dd><dt>configuration directives, Apache, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dd><dl><dt> Ac
cessFileName , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Action , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> AddDescription , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> AddEncoding , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> AddHandler , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> AddIcon , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> AddIconByEncoding , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> AddIconByType , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> AddLanguage , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> AddType , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Alias , <a
class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Allow , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> AllowOverride , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> BrowserMatch , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> CacheNegotiatedDocs , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> CustomLog , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> DefaultIcon , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> DefaultType , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Deny , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Directory , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> DirectoryIndex , <a class="index
term" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> DocumentRoot , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ErrorDocument , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ErrorLog , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ExtendedStatus , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt>for cache functionality, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Group , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> HeaderName , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> HostnameLookups , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> IfDefine , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> IfModule , <a class="indexterm"
href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Include , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> IndexIgnore , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> IndexOptions , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> KeepAlive , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dd><dl><dt>(see also KeepAliveTimeout )</dt><dt>troubleshooting, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> KeepAliveTimeout , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> LanguagePriority , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Listen , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> LoadModule , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips
</a></dt><dt> Location , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> LogFormat </dt><dd><dl><dt>format options, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> LogLevel , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> MaxClients , <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt><dt> MaxKeepAliveRequests , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> MaxRequestsPerChild , <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt><dt> MaxSpareServers , <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt><dt> MaxSpareThreads , <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt><dt> MinSpareServers , <a class="indexterm" href="#s2-apache-mp
m-containers">MPM Specific Server-Pool Directives</a></dt><dt> MinSpareThreads , <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt><dt> NameVirtualHost , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Options , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Order , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> PidFile , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Proxy , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ProxyRequests , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ReadmeName , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> Redirect , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ScriptAlias , <a class="indexterm" href
="#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerAdmin , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerName , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerRoot , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerSignature , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerTokens , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> SetEnvIf , <a class="indexterm" href="#s2-apache-sslcommands">Configuration Directives for SSL</a></dt><dt>SSL configuration, <a class="indexterm" href="#s2-apache-sslcommands">Configuration Directives for SSL</a></dt><dt> StartServers , <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt><dt> SuexecUserGroup , <a class="indexterm" href="#s3-httpd-v2-mig-mod-suexec">The suexec Module</a>,
<a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ThreadsPerChild , <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt><dt> Timeout , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> TypesConfig , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> UseCanonicalName , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> User , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> UserDir , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> VirtualHost , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>Configuration File Changes, <a class="indexterm" href="#sec-Preserving_Configuration_File_Changes">Preserving Configuration File Changes</a></dt><dt>Cron, <a class="indexterm" href="#ch-Automated_
Tasks">Automated Tasks</a></dt><dt>cron</dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-autotasks-additional-resources">Additional Resources</a></dt><dt>configuration file, <a class="indexterm" href="#s2-autotasks-cron-configuring">Configuring Cron Tasks</a></dt><dt>example crontabs, <a class="indexterm" href="#s2-autotasks-cron-configuring">Configuring Cron Tasks</a></dt><dt>user-defined tasks, <a class="indexterm" href="#s2-autotasks-cron-configuring">Configuring Cron Tasks</a></dt></dl></dd><dt> crontab , <a class="indexterm" href="#s2-autotasks-cron-configuring">Configuring Cron Tasks</a></dt><dt>CUPS, <a class="indexterm" href="#ch-Printer_Configuration">Printer Configuration</a></dt><dt> CustomLog </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd></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_Configuration-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> DefaultIcon </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> DefaultType </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>deleting cache files</dt><dd><dl><dt>in SSSD, <a class="indexterm" href="#sect-SSSD_User_Guide-SSSD_Features-Specifying_Multiple_Domains">Specifying 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> Deny </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>desktop environments (see X)</dt><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="#id729711">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></d
t><dt> dhcpd.leases , <a class="indexterm" href="#id729711">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="#id729711">Starting and Stopping the Server</a></dt><dt>stopping the server, <a class="indexterm" href="#id729711">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="#id729711">Starting and Stopping the Server</a></dt><dt> dhcrelay , <a class="indexterm" href="#dhcp-relay-agent">DHCP Relay Agent</a></dt><dt> Directory </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> DirectoryIndex </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>display managers (see X)</dt><dt>DNS, <a class="indexterm" href="#s1-bind-introdu
ction">Introduction to DNS</a></dt><dd><dl><dt>(see also BIND)</dt><dt>introducing, <a class="indexterm" href="#s1-bind-introduction">Introduction to DNS</a></dt></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> DocumentRoot </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt>changing, <a class="indexterm" href="#s1-apache-virtualhosts">Virtual Hosts</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>DSOs</dt><dd><dl><dt>loading, <a class="indexterm" href="#s1-apache-addmods">Adding Modules</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>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 Cl
assifications</a></dt><dt>protocols, <a class="indexterm" href="#s1-email-protocols">Email Protocols</a></dt><dd><dl><dt>Dovecot, <a class="indexterm" href="#s3-email-protocols-dovecot">Dovecot</a></dt><dt>IMAP, <a class="indexterm" href="#s3-email-protocols-imap">IMAP</a></dt><dt>POP, <a class="indexterm" 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 D
elivery Agent, <a class="indexterm" href="#s2-email-types-mda">Mail Delivery Agent</a></dt><dt>Mail Tranport 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> ErrorDocument </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ErrorLog </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>Ethernet (see network)</dt><dt>Ethernet module (see kernel module)</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><dt> ExtendedStatus </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd></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-fetchmail-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 opt
ions, <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> findsmb , <a class="indexterm" href="#s2-samba-connect-share-cmdline">Command Line</a></dt><dt> findsmb program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt>forwarding nameserver (see BIND)</dt><dt>frame buffer device, <a class="indexterm" href="#s2-proc-fb"> /proc/fb </a></dt><dd><
dl><dt>(see also /proc/fb )</dt></dl></dd><dt> free , <a class="indexterm" href="#s1-sysinfo-memory-usage">Memory Usage</a></dt><dt>FTP, <a class="indexterm" href="#ch-FTP">FTP</a></dt><dd><dl><dt>(see also vsftpd )</dt><dt>active mode, <a class="indexterm" href="#s2-ftp-protocol-multiport">Multiple Ports, Multiple Modes</a></dt><dt>command port, <a class="indexterm" href="#s2-ftp-protocol-multiport">Multiple Ports, Multiple Modes</a></dt><dt>data port, <a class="indexterm" href="#s2-ftp-protocol-multiport">Multiple Ports, Multiple Modes</a></dt><dt>definition of, <a class="indexterm" href="#ch-FTP">FTP</a></dt><dt>introducing, <a class="indexterm" href="#s1-ftp-protocol">The File Transfer Protocol</a></dt><dt>passive mode, <a class="indexterm" href="#s2-ftp-protocol-multiport">Multiple Ports, Multiple Modes</a></dt><dt>server software</dt><dd><dl><dt> Red Hat Content Accelerator , <a class="indexterm" href="#s1-ftp-servers">FTP Servers</a></dt><dt> vsftpd , <a class="inde
xterm" href="#s1-ftp-servers">FTP Servers</a></dt></dl></dd></dl></dd></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>GNOME, <a class="indexterm" href="#s2-x-clients-desktop">Desktop Environments</a></dt><dd><dl><dt>(see also X)</dt></dl></dd><dt> GNOME System Monitor , <a class="indexterm" href="#s1-sysinfo-system-processes">System Processes</a></dt><dt> gnome-system-log (see Log 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 </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</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>gro
up 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="#ers_and_Groups
">Users and Groups</a></dt><dt>introducing, <a class="indexterm" href="#ers_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-lo
ader-grub">Configuring the GRUB Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="#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">Hardware</a></dt></dl></dd><dt> Hardware Browser , <a class="indexterm" href="#s1-sysinfo-hardware">Hardware</a></dt><dt> HeaderName </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> HostnameLookups </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> HTTP Configuration Tool </dt><dd><dl><dt>error log, <a class="indexterm" href="#s3-httpd-logging">Logging</a></dt><dt>modules, <a class="indexterm" href="#s1-apache-config-ui">Apache HTTP Server Configuration</a></dt><dt>transfer log, <a class=
"indexterm" href="#s3-httpd-logging">Logging</a></dt></dl></dd><dt>HTTP directives</dt><dd><dl><dt> DirectoryIndex , <a class="indexterm" href="#s3-httpd-site-config">Site Configuration</a></dt><dt> ErrorDocument , <a class="indexterm" href="#s3-httpd-site-config">Site Configuration</a></dt><dt> ErrorLog , <a class="indexterm" href="#s3-httpd-logging">Logging</a></dt><dt> HostnameLookups , <a class="indexterm" href="#s3-httpd-logging">Logging</a></dt><dt> Listen , <a class="indexterm" href="#s2-httpd-basic-settings">Basic Settings</a></dt><dt> LogFormat , <a class="indexterm" href="#s3-httpd-logging">Logging</a></dt><dt> LogLevel , <a class="indexterm" href="#s3-httpd-logging">Logging</a></dt><dt> Options , <a class="indexterm" href="#s3-httpd-site-config">Site Configuration</a></dt><dt> ServerAdmin , <a class="indexterm" href="#s2-httpd-basic-settings">Basic Settings</a></dt><dt> ServerName , <a class="indexterm" href="#s2-httpd-basic-settings">Basic Settings</a></dt><dt> T
ransferLog , <a class="indexterm" href="#s3-httpd-logging">Logging</a></dt></dl></dd><dt> httpd , <a class="indexterm" href="#s1-apache-config-ui">Apache HTTP Server Configuration</a></dt><dt> httpd.conf (see configuration directives, Apache)</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> IfDefine </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ifdown , <a class="indexterm" href="#s1-networkscripts-control">Interface Control Scripts</a></dt><dt> IfModule </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ifup , <a class="indexterm" href="#s1-networkscripts-control">Interface C
ontrol Scripts</a></dt><dt> Include </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> IndexIgnore </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> IndexOptions </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><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>ini
tial 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="#s1-kernel-module-utils">Kernel Module Utilities</a></dt><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>KDE, <a class="indexterm" href="#s2-x-clients-desktop">Desktop Environments</a></dt><dd><dl><dt>(see also X)</dt></dl></dd><dt> KeepAlive </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd
><dt> KeepAliveTimeout </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</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 package, <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></d
t><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 bonding</dt><dd><dl><dt>sysfs, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>kernel module</dt><dd><dl><dt>/etc/sysconfig/modules/, <a class="indexterm" href="#s1-kernel-modules-persistant">Persistent Module Loading</a></dt><dt>bonding kernel module, <a class="indexterm" href="#s2-modules-bonding">The Chann
el Bonding Module</a></dt><dd><dl><dt>bonding directives, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>channel bonding, <a class="indexterm" href="#s2-modules-bonding">The Channel Bonding Module</a></dt><dt>channel bonding interface, <a class="indexterm" href="#s2-modules-bonding">The Channel Bonding Module</a></dt><dt>commands</dt><dd><dl><dt>group of, <a class="indexterm" href="#s1-kernel-module-utils">Kernel Module Utilities</a></dt></dl></dd><dt>Ethernet module, <a class="indexterm" href="#s1-modules-ethernet">Ethernet Parameters</a></dt><dd><dl><dt>supporting multiple cards, <a class="indexterm" href="#s2-modules-multiple-eth">Using Multiple Ethernet Cards</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="#ch-General_Parameters_and_Modules">General Parameters and Module
s</a></dt><dt>listing, <a class="indexterm" href="#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>loading, <a class="indexterm" href="#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>module parameters</dt><dd><dl><dt>specifying, <a class="indexterm" href="#s1-modules-parameters-specifying">Specifying Module Parameters</a></dt><dt>supplying, <a class="indexterm" href="#s1-modules-parameters-specifying">Specifying Module Parameters</a></dt></dl></dd><dt>module-init-tools, <a class="indexterm" href="#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>NIC module, <a class="indexterm" href="#s1-modules-ethernet">Ethernet Parameters</a></dt><dt>persistent loading, <a class="indexterm" href="#s1-kernel-modules-persistant">Persistent Module Loading</a></dt><dt>SCSImodule</dt><dd><dl><dt>parameters, <a class="indexterm" href="#s1-modules-scsi">Storage parameters</a></dt></dl></dd><dt>types of, <a class="indexterm" href="#ch-General_Parameters_and_Mod
ules">General Parameters and Modules</a></dt><dt>unload, <a class="indexterm" href="#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>utilities, <a class="indexterm" href="#s1-kernel-module-utils">Kernel Module Utilities</a></dt></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="#s
1-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 utility, <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><dt> kwin , <a class="indexterm" href="#s2-x-clients-winmanagers">Window Managers</a></dt><dd><dl><dt>(see also X)</dt></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt> LanguagePriority </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>LDAP</dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-ldap-additional-resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-ldap-installed-docs">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="#s2-ldap-related-books">Related Books</a></dt><dt>useful websites, <a class="indexterm" href="#s2-ldap-additional-resources-web">Useful Websites</a></dt></dl></dd><dt>advantages of, <a class="indexterm" href="#s1-ldap-adv">Why Use LDAP?</a></dt><dt>applications</dt><dd><dl><dt> ldapadd , <a class="indexte
rm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt> ldapdelete , <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt> ldapmodify , <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt> ldappasswd , <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt> ldapsearch , <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt>OpenLDAP suite, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt> slapadd , <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt> slapcat , <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt> slapd , <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt> slapindex , <a class="indexterm" href="#s1-ldap-daemonsutils">Ope
nLDAP Daemons and Utilities</a></dt><dt> slappasswd , <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt> slurpd , <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt>utilities, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt></dl></dd><dt>authentication using, <a class="indexterm" href="#s1-ldap-pam">Configuring a System to Authenticate Using OpenLDAP</a></dt><dd><dl><dt> Authentication Configuration Tool , <a class="indexterm" href="#s1-ldap-pam">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>editing /etc/ldap.conf , <a class="indexterm" href="#s1-ldap-pam">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>editing /etc/nsswitch.conf , <a class="indexterm" href="#s1-ldap-pam">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>editing /etc/openldap/ldap.conf , <a class="indexterm" href="#s1-ldap-pam">Configuri
ng a System to Authenticate Using OpenLDAP</a></dt><dt>editing slapd.conf , <a class="indexterm" href="#s1-ldap-pam">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>packages, <a class="indexterm" href="#s1-ldap-pam">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>PAM, <a class="indexterm" href="#s2-ldap-pamd">PAM and LDAP</a></dt><dt>setting up clients, <a class="indexterm" href="#s1-ldap-pam">Configuring a System to Authenticate Using OpenLDAP</a></dt></dl></dd><dt>client applications, <a class="indexterm" href="#s2-ldap-applications">LDAP Client Applications</a></dt><dt>configuration files</dt><dd><dl><dt> /etc/ldap.conf , <a class="indexterm" href="#s1-ldap-files">OpenLDAP Configuration Files</a></dt><dt> /etc/openldap/ldap.conf , <a class="indexterm" href="#s1-ldap-files">OpenLDAP Configuration Files</a></dt><dt> /etc/openldap/schema/ directory, <a class="indexterm" href="#s1-ldap-files">OpenLDAP Configuration Files</a>, <a class="indexter
m" href="#s1-ldap-files-schemas">The /etc/openldap/schema/ Directory</a></dt><dt> /etc/openldap/slapd.conf , <a class="indexterm" href="#s1-ldap-files">OpenLDAP Configuration Files</a>, <a class="indexterm" href="#s2-ldap-files-slapd-conf">Editing /etc/openldap/slapd.conf </a></dt></dl></dd><dt>daemons, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dt>definition of, <a class="indexterm" href="#ch-Lightweight_Directory_Access_Protocol_LDAP">Lightweight Directory Access Protocol (LDAP)</a></dt><dt>LDAPv2, <a class="indexterm" href="#ch-Lightweight_Directory_Access_Protocol_LDAP">Lightweight Directory Access Protocol (LDAP)</a></dt><dt>LDAPv3, <a class="indexterm" href="#ch-Lightweight_Directory_Access_Protocol_LDAP">Lightweight Directory Access Protocol (LDAP)</a></dt><dt>LDIF</dt><dd><dl><dt>format of, <a class="indexterm" href="#s1-ldap-terminology">LDAP Terminology</a></dt></dl></dd><dt>OpenLDAP features, <a class="indexterm" href
="#s1-ldap-v3">OpenLDAP Features</a></dt><dt>setting up, <a class="indexterm" href="#s1-ldap-quickstart">OpenLDAP Setup Overview</a></dt><dd><dl><dt>migrating older directories, <a class="indexterm" href="#s1-ldap-migrate">Migrating Directories from Earlier Releases</a></dt></dl></dd><dt>terminology, <a class="indexterm" href="#s1-ldap-terminology">LDAP Terminology</a></dt><dt>upgrading directories, <a class="indexterm" href="#s1-ldap-migrate">Migrating Directories from Earlier Releases</a></dt><dt>using with Apache HTTP Server, <a class="indexterm" href="#s2-ldap-other-apps">PHP4, LDAP, and the Apache HTTP Server</a></dt><dt>using with NSS, <a class="indexterm" href="#s2-ldap-pam-nss">NSS, PAM, and LDAP</a></dt><dt>using with PAM, <a class="indexterm" href="#s2-ldap-pam-nss">NSS, PAM, and LDAP</a></dt><dt>using with PHP4, <a class="indexterm" href="#s2-ldap-other-apps">PHP4, LDAP, and the Apache HTTP Server</a></dt></dl></dd><dt> ldapadd command, <a class="indexterm" href="
#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> ldapdelete command, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> ldapmodify command, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> ldappasswd command, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> ldapsearch command, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt>Lightweight Directory Access Protocol (see LDAP)</dt><dt> Listen </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> LoadModule </dt><dd><dl><dt>Apache configuration
directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Location </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</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>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> LogFormat </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> LogLevel </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> logrotate , <a class="indexterm" href="#s1-logfiles-locating">Locating Log Files</a></dt><dt> lpd , <a class="indexterm" href="#ch-Printer_Configuration">Printer Configuration</a></dt><dt> lsmod , <a class="indexterm" href="#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt> lspci , <a class="indexterm" href="#s2-proc-pci"> /proc/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="#s1-email-swit
chmail">Mail Transport Agent (MTA) Configuration</a></dt><dt>Mail User Agent, <a class="indexterm" href="#s1-email-switchmail">Mail Transport Agent (MTA) Configuration</a> (see email)</dt><dt>master nameserver (see BIND)</dt><dt> MaxClients </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> MaxKeepAliveRequests </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> MaxRequestsPerChild </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> MaxSpareServers </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> MaxSpareThreads </dt><dd><dl><dt>Apache configuration directiv
e, <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt>MDA (see Mail Delivery Agent)</dt><dt>memory usage, <a class="indexterm" href="#s1-sysinfo-memory-usage">Memory Usage</a></dt><dt> metacity , <a class="indexterm" href="#s2-x-clients-winmanagers">Window Managers</a></dt><dd><dl><dt>(see also X)</dt></dl></dd><dt> MinSpareServers </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> MinSpareThreads </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> modprobe , <a class="indexterm" href="#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>module (see kernel module)</dt><dt>module parameters (see kernel module)</dt><dt>modules</dt><dd><dl><dt>Apache</dt><dd><dl><dt>loading, <a class="indexter
m" href="#s1-apache-addmods">Adding Modules</a></dt><dt>the own, <a class="indexterm" href="#s1-apache-addmods">Adding Modules</a></dt></dl></dd></dl></dd><dt>MTA (see Mail Transport Agent)</dt><dd><dl><dt>setting default, <a class="indexterm" href="#s1-email-switchmail">Mail Transport Agent (MTA) Configuration</a></dt><dt>switching with Mail Transport Agent Switcher , <a class="indexterm" href="#s1-email-switchmail">Mail Transport Agent (MTA) Configuration</a></dt></dl></dd><dt>MUA, <a class="indexterm" href="#s1-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 Multihomed DHCP Server</a></dt></dl></dd><dt>multiple domains</dt><dd><dl><dt>specifying in SSSD, <a class="indexterm" href="#sec
t-SSSD_User_Guide-SSSD_Features-Specifying_Multiple_Domains">Specifying Multiple Domains</a></dt></dl></dd><dt> mwm , <a class="indexterm" href="#s2-x-clients-winmanagers">Window Managers</a></dt><dd><dl><dt>(see also X)</dt></dl></dd></dl></div><div class="indexdiv"><h3>N</h3><dl><dt> named daemon (see BIND)</dt><dt> named.conf (see BIND)</dt><dt>nameserver (see BIND)</dt><dt> NameVirtualHost </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> net program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></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 class="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 cl
ass="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="#s2-modules-bonding">The Channel Bonding Module</a></dt></dl></dd><dt>NIC module</dt><dd><dl><dt>kernel module, <a class="indexterm" href="#s1-modules-ethernet">Ethernet Parameters</a></dt></dl></dd><dt> nmblookup program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><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_Pro
tocol">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 (see NTP)</dt><dt> ntsysv (see services configuration)</dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>objects, dynamically shared (see DSOs)</dt><dt> opannotate (see OProfile)</dt><dt> opcontrol (see OProfile)</dt><dt>OpenLDAP (see LDAP)</dt><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="i
ndexterm" 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-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>server, <a class="indexterm" href="#s2-ssh-configuration-sshd">Starting an Ope
nSSH 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">Generating 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></dl></dd><dt> ophelp , <a class="indexterm" href="#s2-oprofile-events">Setting Events to Monitor</a></dt><dt> opreport (see OProfile)</dt><dt>OProfile, <a class="indexterm" href="#ch-OProfile">OProfile</a></dt><dd><dl><dt> /dev/oprofile/ , <a class="indexterm" href="#s1-oprofile-dev-oprofile">Understanding /dev/oprofile/ </a></dt><dt>additional resources, <a class="indexterm" href="#s1-oprofile-additional-resources">Additional Resources</a></dt><dt>configuring, <a class="indexterm" href="#s1-oprofile-configuring">Configuring OProfile</a></dt><dd><dl><dt>separating profiles, <a class="indexterm" href="#s2-oprofile-starting-separate">Separating Kernel and User-space Profiles</a></dt></dl></dd><dt>events</dt><dd><dl><dt>sampling rate, <a class="indexterm" href="#s3-oprofile-events-sampling">Sampling Rate</a></dt><dt>setting, <a class="indexte
rm" href="#s2-oprofile-events">Setting Events to Monitor</a></dt></dl></dd><dt>monitoring the kernel, <a class="indexterm" href="#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> opannotate , <a class="indexterm" href="#s2-oprofile-reading-opannotate">Using opannotate </a></dt><dt> opcontrol , <a class="indexterm" href="#s1-oprofile-configuring">Configuring OProfile</a></dt><dd><dl><dt> --no-vmlinux , <a class="indexterm" href="#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> --start , <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile</a></dt><dt> --vmlinux= , <a class="indexterm" href="#s2-oprofile-kernel">Specifying the Kernel</a></dt></dl></dd><dt> ophelp , <a class="indexterm" href="#s2-oprofile-events">Setting Events to Monitor</a></dt><dt> opreport , <a class="indexterm" href="#s2-oprofile-reading-opreport">Using opreport </a>, <a class="indexterm" href="#s2-oprofile-module-output">Getting more detailed output on the modules<
/a></dt><dd><dl><dt>on a single executable, <a class="indexterm" href="#s2-oprofile-reading-opreport-single">Using opreport on a Single Executable</a></dt></dl></dd><dt> oprofiled , <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile</a></dt><dd><dl><dt>log file, <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile</a></dt></dl></dd><dt>overview of tools, <a class="indexterm" href="#s1-oprofile-overview-tools">Overview of Tools</a></dt><dt>reading data, <a class="indexterm" href="#s1-oprofile-analyzing-data">Analyzing the Data</a></dt><dt>saving data, <a class="indexterm" href="#s1-oprofile-saving-data">Saving Data</a></dt><dt>starting, <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile</a></dt><dt>unit mask, <a class="indexterm" href="#s3-oprofile-events-unit-masks">Unit Masks</a></dt></dl></dd><dt> oprofiled (see OProfile)</dt><dt> oprof_start , <a class="indexterm" href="#s1-oprofile-g
ui">Graphical Interface</a></dt><dt> Options </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Order </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></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><dt>PackageKit, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dd><dl><dt>adding and removing, <a class="indexterm" href="#sec-Using_Add_Remove_Softwa
re">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_th
e_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 Displaying Package Information</a></dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Dis
playing 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 wit
h 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-find
ing">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-Instal
ling_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 class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>listing packages with Yum, <a class="indexterm" href="#sec-Searching_Li
sting_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="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum repolist, <a class="i
ndexterm" 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>failed dependancies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">Unresolved Dependency</a></dt><dt>freshening, <a class="indexterm" href="#s2-rpm-freshe
ning">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 Package Information</a></dt></dl></dd><dt>searching packages with Yum, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searchin
g, 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 Sof
tware 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" href="#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> pdbedit program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> PidFile </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</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="#s1-email-switchmail">Mail Transport Agent (MTA) Configuration</a></dt><dt> prefdm (
see X)</dt><dt> printconf (see printer configuration)</dt><dt>printer configuration, <a class="indexterm" href="#ch-Printer_Configuration">Printer Configuration</a></dt><dd><dl><dt>adding</dt><dd><dl><dt>CUPS (IPP) printer, <a class="indexterm" href="#s1-printing-ipp-printer">Adding an IPP Printer</a></dt><dt>IPP printer, <a class="indexterm" href="#s1-printing-ipp-printer">Adding an IPP Printer</a></dt><dt>JetDirect printer, <a class="indexterm" href="#s1-printing-jetdirect-printer">Adding a JetDirect Printer</a></dt><dt>local printer, <a class="indexterm" href="#s1-printing-local-printer">Adding a Local Printer</a></dt><dt>Samba (SMB) printer, <a class="indexterm" href="#s1-printing-smb-printer">Adding a Samba (SMB) Printer</a></dt></dl></dd><dt>cancel print job, <a class="indexterm" href="#s1-printing-managing">Managing Print Jobs</a></dt><dt>CUPS, <a class="indexterm" href="#ch-Printer_Configuration">Printer Configuration</a></dt><dt>default printer, <a class="indexterm
" href="#s1-printing-edit">Modifying Existing Printers</a></dt><dt>delete existing printer, <a class="indexterm" href="#s1-printing-edit">Modifying Existing Printers</a></dt><dt>IPP printer, <a class="indexterm" href="#s1-printing-ipp-printer">Adding an IPP Printer</a></dt><dt>JetDirect printer, <a class="indexterm" href="#s1-printing-jetdirect-printer">Adding a JetDirect Printer</a></dt><dt>local printer, <a class="indexterm" href="#s1-printing-local-printer">Adding a Local Printer</a></dt><dt>managing print jobs, <a class="indexterm" href="#s1-printing-managing">Managing Print Jobs</a></dt><dt>networked CUPS (IPP) printer, <a class="indexterm" href="#s1-printing-ipp-printer">Adding an IPP Printer</a></dt><dt>printing from the command line, <a class="indexterm" href="#s1-printing-managing">Managing Print Jobs</a></dt><dt>Samba (SMB) printer, <a class="indexterm" href="#s1-printing-smb-printer">Adding a Samba (SMB) Printer</a></dt><dt>test page, <a class="indexterm" href="#s
1-printing-test-page">Printing a Test Page</a></dt><dt>viewing print spool, command line, <a class="indexterm" href="#s1-printing-managing">Managing Print Jobs</a></dt></dl></dd><dt> Printer Configuration Tool (see printer configuration)</dt><dt> printtool (see printer configuration)</dt><dt> proc file system</dt><dd><dl><dt> /proc/buddyinfo , <a class="indexterm" 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/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 class="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="indexterm" 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/pci </dt><dd><dl><dt>viewing using lspci , <a class="indexterm" href="#s2-proc-pci"> /proc/pci </a></dt></dl></dd><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="indexterm" 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" h
ref="#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-websites">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" hre
f="#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></dt><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></dt><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> Proxy </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>proxy server, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ProxyRequests </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General C
onfiguration Tips</a></dt></dl></dd><dt> ps , <a class="indexterm" href="#s1-sysinfo-system-processes">System Processes</a></dt><dt> public_html directories, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</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> ReadmeName </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Red Hat RPM Guide , <a class="indexterm" href="#s2-rpm-related-books">Related Books</a></dt><dt> Redirect </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>removing package groups</dt><dd><dl><dt>removing package groups with PackageKit, <a class="indexterm" href="#sec-Installing_an
d_Removing_Package_Groups">Installing and Removing Package Groups</a></dt></dl></dd><dt> rmmod , <a class="indexterm" href="#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>root nameserver (see BIND)</dt><dt> rpcclient program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></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><dt>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="ind
exterm" href="#s2-rpm-querying">Querying</a></dt><dt>querying for file list, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common 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 Versi
on 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>Samba (see Samba)</dt><dd><dl><dt>Abilities, <a class="indexterm" href="#s2-samba-abilities">Samba Features</a></dt><dt>Account Information Databases, <a class="indexterm" href="#s1-samba-account-info-dbs">Samba Account Information Databases</a></dt><dd><dl><dt> ldapsam , <a class="indexterm" href="#s1-samba-account-info-dbs">Samba Account Information Databases</a></dt><dt> ldapsam_compat , <a class="indexterm" href="#s1-samba-account-info-dbs">Samba Account Information Databases</a></dt><dt> mysqlsam , <a class="indexterm" href="#s1-samba-account-info-dbs">Samba Account Information Databases</a></dt><dt>Plain Text, <a class="indexterm" href="#s1-samba-account
-info-dbs">Samba Account Information Databases</a></dt><dt> smbpasswd , <a class="indexterm" href="#s1-samba-account-info-dbs">Samba Account Information Databases</a></dt><dt> tdbsam , <a class="indexterm" href="#s1-samba-account-info-dbs">Samba Account Information Databases</a></dt><dt> xmlsam , <a class="indexterm" href="#s1-samba-account-info-dbs">Samba Account Information Databases</a></dt></dl></dd><dt>Additional Resources, <a class="indexterm" href="#s1-samba-resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-samba-resources-installed">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="#s2-samba-resources-published">Related Books</a></dt><dt>useful websites, <a class="indexterm" href="#s2-samba-resources-community">Useful Websites</a></dt></dl></dd><dt>Backward Compatible Database Backends, <a class="indexterm" href="#s1-samba-account-info-dbs">Samba Account Information Databases</a></d
t><dt>Browsing, <a class="indexterm" href="#s1-samba-network-browsing">Samba Network Browsing</a></dt><dt>configuration, <a class="indexterm" href="#s1-samba-configuring">Configuring a Samba Server</a>, <a class="indexterm" href="#s2-samba-configuring-cmdline">Command Line Configuration</a></dt><dd><dl><dt>default, <a class="indexterm" href="#s1-samba-configuring">Configuring a Samba Server</a></dt></dl></dd><dt>CUPS Printing Support, <a class="indexterm" href="#s1-samba-cups">Samba with CUPS Printing Support</a></dt><dd><dl><dt>CUPS smb.conf, <a class="indexterm" href="#s2-samba-cups-smb.conf">Simple smb.conf Settings</a></dt></dl></dd><dt>daemon, <a class="indexterm" href="#s1-samba-daemons">Samba Daemons and Related Services</a></dt><dd><dl><dt>nmbd, <a class="indexterm" href="#s2-samba-services">Samba Daemons</a></dt><dt>overview, <a class="indexterm" href="#s2-samba-services">Samba Daemons</a></dt><dt>smbd, <a class="indexterm" href="#s2-samba-services">Samba Daemons</a
></dt><dt>winbindd, <a class="indexterm" href="#s2-samba-services">Samba Daemons</a></dt></dl></dd><dt>encrypted passwords, <a class="indexterm" href="#s2-samba-encrypted-passwords">Encrypted Passwords</a></dt><dt> findsmb , <a class="indexterm" href="#s2-samba-connect-share-cmdline">Command Line</a></dt><dt>graphical configuration, <a class="indexterm" href="#s2-samba-configuring-gui">Graphical Configuration</a></dt><dd><dl><dt>adding a share, <a class="indexterm" href="#s3-samba-gui-add-share">Adding a Share</a></dt><dt>configuring server settings, <a class="indexterm" href="#s3-samba-gui-server-settings">Configuring Server Settings</a></dt><dt>managing Samba users, <a class="indexterm" href="#s3-samba-gui-users">Managing Samba Users</a></dt></dl></dd><dt>Introduction, <a class="indexterm" href="#samba-rgs-overview">Introduction to Samba</a></dt><dt>Network Browsing, <a class="indexterm" href="#s1-samba-network-browsing">Samba Network Browsing</a></dt><dd><dl><dt>Domain Br
owsing, <a class="indexterm" href="#s2-samba-domain-browsing">Domain Browsing</a></dt><dt>WINS, <a class="indexterm" href="#s2-samba-wins">WINS (Windows Internetworking Name Server)</a></dt></dl></dd><dt>New Database Backends, <a class="indexterm" href="#s1-samba-account-info-dbs">Samba Account Information Databases</a></dt><dt>Programs, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dd><dl><dt> findsmb , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> net , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> nmblookup , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> pdbedit , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> rpcclient , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbcacls , <a class="indexterm" href="#s1-samba-programs">Samba
Distribution Programs</a></dt><dt> smbclient , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbcontrol , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbpasswd , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbspool , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbstatus , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbtar , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> testparm , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> wbinfo , <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt></dl></dd><dt>Reference, <a class="indexterm" href="#ch-Samba">Samba</a></dt><dt>Security Modes, <a class="indexterm" href="#s1-samba-security-modes">Samba Security
Modes</a></dt><dd><dl><dt>Active Directory Security Mode, <a class="indexterm" href="#s2-samba-ads-security-mode">Active Directory Security Mode (User-Level Security)</a></dt><dt>Domain Security Mode, <a class="indexterm" href="#s2-samba-domain-security-mode">Domain Security Mode (User-Level Security)</a></dt><dt>Server Security Mode, <a class="indexterm" href="#s2-samba-server-security-mode">Server Security Mode (User-Level Security)</a></dt><dt>Share-Level Security, <a class="indexterm" href="#s2-samba-share-level">Share-Level Security</a></dt><dt>User Level Security, <a class="indexterm" href="#s2-samba-user-level">User-Level Security</a></dt></dl></dd><dt>Server Types, <a class="indexterm" href="#s1-samba-servers">Samba Server Types and the smb.conf File</a></dt><dt>server types</dt><dd><dl><dt>Domain Controller, <a class="indexterm" href="#s2-samba-domain-controller">Domain Controller</a></dt><dt>Domain Member, <a class="indexterm" href="#s2-samba-domain-member">Domain
Member Server</a></dt><dt>Stand Alone, <a class="indexterm" href="#s2-samba-standalone">Stand-alone Server</a></dt></dl></dd><dt>service</dt><dd><dl><dt>conditional restarting, <a class="indexterm" href="#s1-samba-startstop">Starting and Stopping Samba</a></dt><dt>reloading, <a class="indexterm" href="#s1-samba-startstop">Starting and Stopping Samba</a></dt><dt>restarting, <a class="indexterm" href="#s1-samba-startstop">Starting and Stopping Samba</a></dt><dt>starting, <a class="indexterm" href="#s1-samba-startstop">Starting and Stopping Samba</a></dt><dt>stopping, <a class="indexterm" href="#s1-samba-startstop">Starting and Stopping Samba</a></dt></dl></dd><dt>share</dt><dd><dl><dt>connecting to via the command line, <a class="indexterm" href="#s2-samba-connect-share-cmdline">Command Line</a></dt><dt>connecting to with Nautilus, <a class="indexterm" href="#s1-samba-connect-share">Connecting to a Samba Share</a></dt><dt>mounting, <a class="indexterm" href="#s1-samba-mounting
">Mounting the Share</a></dt></dl></dd><dt>smb.conf, <a class="indexterm" href="#s1-samba-servers">Samba Server Types and the smb.conf File</a></dt><dd><dl><dt>Active Directory Member Server example, <a class="indexterm" href="#s3-samba-domain-member-ads">Active Directory Domain Member Server</a></dt><dt>Anonymous Print Server example, <a class="indexterm" href="#s3-samba-standalone-anonprint">Anonymous Print Server</a></dt><dt>Anonymous Read Only example, <a class="indexterm" href="#s3-samba-standalone-anonreadonly">Anonymous Read-Only</a></dt><dt>Anonymous Read/Write example, <a class="indexterm" href="#s3-samba-standalone-anonreadwrite">Anonymous Read/Write</a></dt><dt>NT4-style Domain Member example, <a class="indexterm" href="#s3-samba-domain-member-nt4">Windows NT4-based Domain Member Server</a></dt><dt>PDC using Active Directory, <a class="indexterm" href="#samba-rgs-pdc-ads">Primary Domain Controller (PDC) with Active Directory</a></dt><dt>PDC using tdbsam , <a class
="indexterm" href="#s3-samba-pdc-tdbsam">Primary Domain Controller (PDC) using tdbsam </a></dt><dt>Secure File and Print Server example, <a class="indexterm" href="#s3-samba-standalone-readwriteall">Secure Read/Write File and Print Server</a></dt></dl></dd><dt> smbclient , <a class="indexterm" href="#s2-samba-connect-share-cmdline">Command Line</a></dt><dt>WINS, <a class="indexterm" href="#s2-samba-wins">WINS (Windows Internetworking Name Server)</a></dt><dt>with Windows NT 4.0, 2000, ME, and XP, <a class="indexterm" href="#s2-samba-encrypted-passwords">Encrypted Passwords</a></dt></dl></dd><dt> scp (see OpenSSH)</dt><dt> ScriptAlias </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>SCSI module (see kernel module)</dt><dt>secure server</dt><dd><dl><dt>certificate</dt><dd><dl><dt>authorities, <a class="indexterm" href="#s2-secureserver-certs">Types of Certificates</a></dt><dt>choosing
a CA, <a class="indexterm" href="#s2-secureserver-certs">Types of Certificates</a></dt><dt> moving it after an upgrade, <a class="indexterm" href="#s1-secureserver-oldcert">Using Pre-Existing Keys and Certificates</a></dt><dt>pre-existing, <a class="indexterm" href="#s1-secureserver-oldcert">Using Pre-Existing Keys and Certificates</a></dt><dt>test vs. signed vs. self-signed, <a class="indexterm" href="#s2-secureserver-certs">Types of Certificates</a></dt></dl></dd><dt>explanation of security, <a class="indexterm" href="#s2-secureserver-overview-certs">An Overview of Certificates and Security</a></dt><dt>installing, <a class="indexterm" href="#s1-httpd-secure-server">Apache HTTP Secure Server Configuration</a></dt><dt>key</dt><dd><dl><dt>generating, <a class="indexterm" href="#s2-secureserver-generatingkey">Generating a Key</a></dt></dl></dd><dt>packages, <a class="indexterm" href="#s2-secureserver-optionalpackages">An Overview of Security-Related Packages</a></dt><dt>provi
ding a certificate for, <a class="indexterm" href="#s2-secureserver-overview-certs">An Overview of Certificates and Security</a></dt><dt>security</dt><dd><dl><dt>explanation of, <a class="indexterm" href="#s2-secureserver-overview-certs">An Overview of Certificates and Security</a></dt></dl></dd><dt>upgrading from, <a class="indexterm" href="#s1-secureserver-oldcert">Using Pre-Existing Keys and Certificates</a></dt></dl></dd><dt>security</dt><dd><dl><dt>running Apache without, <a class="indexterm" href="#s1-apache-virtualhosts">Virtual Hosts</a></dt></dl></dd><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">Addit
ional 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-email-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 S
endmail Configuration Changes</a></dt></dl></dd><dt>sendmail, <a class="indexterm" href="#s1-email-switchmail">Mail Transport Agent (MTA) Configuration</a></dt><dt>server side includes, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerAdmin </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ServerName </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ServerRoot </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ServerSignature </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ServerTokens </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apac
he-tips">General Configuration Tips</a></dt></dl></dd><dt> service (see services configuration)</dt><dt>services configuration, <a class="indexterm" href="#ch-Controlling_Access_to_Services">Controlling Access to Services</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> SetEnvIf </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-sslcommands">Configuration Directives for SSL</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> slapadd command, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> slapcat command, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> slapd command, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> slapindex command, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> slappasswd command, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt>slave nameserver (see BIND)</dt><dt> s
lurpd command, <a class="indexterm" href="#s1-ldap-daemonsutils">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> smbcacls program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbclient , <a class="indexterm" href="#s2-samba-connect-share-cmdline">Command Line</a></dt><dt> smbclient program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbcontrol program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbpasswd program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbspool program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbstatus program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> smbtar program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></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>authentication, <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 Layer</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-configur
ation-keypairs-agent">Configuring ssh-agent</a></dt><dt>SSL configuration, <a class="indexterm" href="#s2-apache-sslcommands">Configuration Directives for SSL</a></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 Authentication</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> StartServers </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-mpm-containers">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> startx , <a class="indexterm" href="#s2-x-runlevels-3">Runlevel 3</a> (see X)</dt><dd><dl><dt>(see also X)</dt></dl></dd><dt> stunnel , <a class="indexterm" href="#s3-email-security-servers">Securing Email Client Communications</a></dt><dt> SuexecUserGroup </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s3-httpd-v2-mig-mod-suexec">The suexec Module</a>, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> sy
sconfig 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/ Directory</a></dt><dt> /etc/sysconfig/clock , <a class="indexterm" href="#s2-sysconfig-clock"> /etc/sysconfig/clock </a></dt><dt> /etc/sysconfig/desktop , <a class="indexterm" href="#s2-sysconfig-desktop"> /etc/sysconfig/desktop </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/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/sysconfig/network </a></dt><dt> /etc/sysconfig/network-scripts/ directory, <a class="indexterm" href="#ch-Network_Interfaces">Network Interfaces</a></dt><dt> /etc/sysconfig/ntpd , <a class="indexterm" href="#s2-sysconfig-ntpd"> /etc/sysconfig/ntpd </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-sysconfig-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/sys
config/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> sysconfig/ directory</dt><dd><dl><dt> /etc/sysconfig/network-scripts/ directory, <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></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 analysis</dt><dd><dl><dt>OProfile (see OProfile)</dt></dl></dd><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 Log 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> System Log Viewer - Filter </dt><dd><dl><dt>System Log Filter, <a class="indexterm" href="#s1-logfiles-viewing">Viewing Log Files</a></dt></dl></dd><dt> System Log Viewer - View Menu </dt><dd><dl><dt>View Menu, <a class="indexterm" href="#s1-logfiles-viewing">Viewing Log Files</a></dt></dl></dd><dt>system request key</dt><dd><dl><dt>enabl
ing, <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 Configuration Tool )</dt><dt> system-config-date (see time configuration, date configuration)</dt><dt> system-config-httpd (see HTTP Configuration Tool)</dt><dt> system-config-printer (see printer configuration)</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> testparm program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt> ThreadsPerChild </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-m
pm-containers">MPM Specific Server-Pool Directives</a></dt></dl></dd><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="indexterm" href="#sect-Date_and_Time_Configuration-Time_Zone">Time Zone Properties</a></dt><dt> Timeout </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>TLB cache
(see hugepages)</dt><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><dt>troubleshooting</dt><dd><dl><dt>error log, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> twm , <a class="indexterm" href="#s2-x-clients-winmanagers">Window Managers</a></dt><dd><dl><dt>(see also X)</dt></dl></dd><dt> TypesConfig </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd></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 p
ackages 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> UseCanonicalName </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> User </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</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-configui">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 Conf
iguration</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> UserDir </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>users (see user configuration)</dt><dd><dl><dt> /etc/passwd , <a class="indexterm" 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="i
ndexterm" href="#ers_and_Groups">Users and Groups</a></dt><dt>personal HTML directories, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</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="#ers_and_Groups">Users and Groups</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>VeriSign</dt><dd><dl><dt>using existing certificate, <a class="indexterm" href="#s1-secureserver-oldcert">Using Pre-Existing Keys and Certificates</a></dt></dl></dd><dt>virtual file system (see proc file system)</dt><dt>virtual files (see proc file system)</dt><dt>virtual hosts</dt><dd><dl><dt>configuring, <a class="indexterm" h
ref="#s1-apache-virtualhosts">Virtual Hosts</a></dt><dt> Listen command, <a class="indexterm" href="#s2-apache-settingupvhosts">Setting Up Virtual Hosts</a></dt><dt>name-based, <a class="indexterm" href="#s1-apache-virtualhosts">Virtual Hosts</a></dt><dt> Options , <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt><dt>server side includes, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> VirtualHost </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> vsftpd , <a class="indexterm" href="#s1-ftp-servers">FTP Servers</a></dt><dd><dl><dt>(see also FTP)</dt><dt>additional resources, <a class="indexterm" href="#s1-ftp-resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-ftp-installed-documentation">Installed Documentation</a></dt><dt>useful websites, <a class="inde
xterm" href="#s2-ftp-useful-websites">Useful Websites</a></dt></dl></dd><dt>condrestart, <a class="indexterm" href="#s1-ftp-vsftpd-start">Starting and Stopping vsftpd </a></dt><dt>configuration file</dt><dd><dl><dt> /etc/vsftpd/vsftpd.conf , <a class="indexterm" href="#s1-ftp-vsftpd-conf"> vsftpd Configuration Options</a></dt><dt>access controls, <a class="indexterm" href="#s2-ftp-vsftpd-conf-opt-login">Log In Options and Access Controls</a></dt><dt>anonymous user options, <a class="indexterm" href="#s2-ftp-vsftpd-conf-opt-anon">Anonymous User Options</a></dt><dt>daemon options, <a class="indexterm" href="#s2-ftp-vsftpd-conf-opt-daemon">Daemon Options</a></dt><dt>directory options, <a class="indexterm" href="#s2-ftp-vsftpd-conf-opt-dir">Directory Options</a></dt><dt>file transfer options, <a class="indexterm" href="#s2-ftp-vsftpd-conf-opt-file">File Transfer Options</a></dt><dt>format of, <a class="indexterm" href="#s1-ftp-vsftpd-conf"> vsftpd Configuration Options</a></dt><
dt>local user options, <a class="indexterm" href="#s2-ftp-vsftpd-conf-opt-usr">Local User Options</a></dt><dt>logging options, <a class="indexterm" href="#s2-ftp-vsftpd-conf-opt-log">Logging Options</a></dt><dt>login options, <a class="indexterm" href="#s2-ftp-vsftpd-conf-opt-login">Log In Options and Access Controls</a></dt><dt>network options, <a class="indexterm" href="#s2-ftp-vsftpd-conf-opt-net">Network Options</a></dt></dl></dd><dt>multihome configuration, <a class="indexterm" href="#s2-ftp-vsftpd-start-multi">Starting Multiple Copies of vsftpd </a></dt><dt>restarting, <a class="indexterm" href="#s1-ftp-vsftpd-start">Starting and Stopping vsftpd </a></dt><dt>RPM</dt><dd><dl><dt>files installed by, <a class="indexterm" href="#s2-ftp-vsftpd-conf">Files Installed with vsftpd </a></dt></dl></dd><dt>security features, <a class="indexterm" href="#s1-ftp-servers">FTP Servers</a></dt><dt>starting, <a class="indexterm" href="#s1-ftp-vsftpd-start">Starting and Stopping vsftpd </
a></dt><dt>starting multiple copies of, <a class="indexterm" href="#s2-ftp-vsftpd-start-multi">Starting Multiple Copies of vsftpd </a></dt><dt>status, <a class="indexterm" href="#s1-ftp-vsftpd-start">Starting and Stopping vsftpd </a></dt><dt>stopping, <a class="indexterm" href="#s1-ftp-vsftpd-start">Starting and Stopping vsftpd </a></dt></dl></dd></dl></div><div class="indexdiv"><h3>W</h3><dl><dt> wbinfo program, <a class="indexterm" href="#s1-samba-programs">Samba Distribution Programs</a></dt><dt>webmaster</dt><dd><dl><dt>email address for, <a class="indexterm" href="#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>window managers (see X)</dt><dt>Windows 2000</dt><dd><dl><dt>connecting to shares using Samba, <a class="indexterm" href="#s2-samba-encrypted-passwords">Encrypted Passwords</a></dt></dl></dd><dt>Windows 98</dt><dd><dl><dt>connecting to shares using Samba, <a class="indexterm" href="#s2-samba-encrypted-passwords">Encrypted Passwords</a></dt></dl>
</dd><dt>Windows ME</dt><dd><dl><dt>connecting to shares using Samba, <a class="indexterm" href="#s2-samba-encrypted-passwords">Encrypted Passwords</a></dt></dl></dd><dt>Windows NT 4.0</dt><dd><dl><dt>connecting to shares using Samba, <a class="indexterm" href="#s2-samba-encrypted-passwords">Encrypted Passwords</a></dt></dl></dd><dt>Windows XP</dt><dd><dl><dt>connecting to shares using Samba, <a class="indexterm" href="#s2-samba-encrypted-passwords">Encrypted Passwords</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>X</dt><dd><dl><dt> /etc/X11/xorg.conf </dt><dd><dl><dt>boolean values for, <a class="indexterm" href="#s3-x-server-config-xorg.conf-struct">The Structure</a></dt><dt> Device , <a class="indexterm" href="#s3-x-server-config-xorg.conf-device"> Device </a></dt><dt> DRI , <a class="indexterm" href="#s3-x-server-config-xorg.conf-dri"> DRI </a></dt><dt> Files section, <a class="indexterm" href="#s3-x-server-config-xorg.conf-files"> Files </a></dt><
dt> InputDevice section, <a class="indexterm" href="#s3-x-server-config-xorg.conf-inputd"> InputDevice </a></dt><dt>introducing, <a class="indexterm" href="#s2-x-server-config-xorg.conf"> xorg.conf </a></dt><dt> Module section, <a class="indexterm" href="#s3-x-server-config-xorg.conf-modules"> Module </a></dt><dt> Monitor , <a class="indexterm" href="#s3-x-server-config-xorg.conf-monitor"> Monitor </a></dt><dt> Screen , <a class="indexterm" href="#s3-x-server-config-xorg.conf-screen"> Screen </a></dt><dt> Section tag, <a class="indexterm" href="#s3-x-server-config-xorg.conf-struct">The Structure</a></dt><dt> ServerFlags section, <a class="indexterm" href="#s3-x-server-config-xorg.conf-serverf"> ServerFlags </a></dt><dt> ServerLayout section, <a class="indexterm" href="#s3-x-server-config-xorg.conf-serverl"> ServerLayout </a></dt><dt>structure of, <a class="indexterm" href="#s3-x-server-config-xorg.conf-struct">The Structure</a></dt></dl></dd><dt>additional resources, <a clas
s="indexterm" href="#s1-x-additional-resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-x-installed-documentation">Installed Documentation</a></dt><dt>useful websites, <a class="indexterm" href="#s2-x-useful-websites">Useful Websites</a></dt></dl></dd><dt>configuration files</dt><dd><dl><dt> /etc/X11/ directory, <a class="indexterm" href="#s1-x-server-configuration">X Server Configuration Files</a></dt><dt> /etc/X11/xorg.conf , <a class="indexterm" href="#s2-x-server-config-xorg.conf"> xorg.conf </a></dt><dt>options within, <a class="indexterm" href="#s1-x-server-configuration">X Server Configuration Files</a></dt><dt>server options, <a class="indexterm" href="#s2-x-server-config-xorg.conf"> xorg.conf </a></dt></dl></dd><dt>desktop environments</dt><dd><dl><dt>GNOME, <a class="indexterm" href="#s2-x-clients-desktop">Desktop Environments</a></dt><dt>KDE, <a class="indexterm" href="#s2-x-clients-desktop">Desktop Environm
ents</a></dt></dl></dd><dt>display managers</dt><dd><dl><dt>configuration of preferred, <a class="indexterm" href="#s2-x-runlevels-5">Runlevel 5</a></dt><dt>definition of, <a class="indexterm" href="#s2-x-runlevels-5">Runlevel 5</a></dt><dt> GNOME , <a class="indexterm" href="#s2-x-runlevels-5">Runlevel 5</a></dt><dt> KDE , <a class="indexterm" href="#s2-x-runlevels-5">Runlevel 5</a></dt><dt> prefdm script, <a class="indexterm" href="#s2-x-runlevels-5">Runlevel 5</a></dt><dt> xdm , <a class="indexterm" href="#s2-x-runlevels-5">Runlevel 5</a></dt></dl></dd><dt>fonts</dt><dd><dl><dt>core X font subsystem, <a class="indexterm" href="#s2-x-fonts-core">Core X Font System</a></dt><dt>Fontconfig, <a class="indexterm" href="#s2-x-fonts-fontconfig">Fontconfig</a></dt><dt>Fontconfig, adding fonts to, <a class="indexterm" href="#s3-x-fonts-fontconfig-add">Adding Fonts to Fontconfig</a></dt><dt>FreeType, <a class="indexterm" href="#s2-x-fonts-fontconfig">Fontconfig</a></dt><dt>introduci
ng, <a class="indexterm" href="#s1-x-fonts">Fonts</a></dt><dt>X Font Server, <a class="indexterm" href="#s2-x-fonts-core">Core X Font System</a></dt><dt>X Render Extension, <a class="indexterm" href="#s2-x-fonts-fontconfig">Fontconfig</a></dt><dt> xfs , <a class="indexterm" href="#s2-x-fonts-core">Core X Font System</a></dt><dt> xfs configuration, <a class="indexterm" href="#s3-x-fonts-xfs-config"> xfs Configuration</a></dt><dt> xfs, adding fonts to, <a class="indexterm" href="#s2-x-fonts-xfs-add">Adding Fonts to xfs </a></dt><dt>Xft, <a class="indexterm" href="#s2-x-fonts-fontconfig">Fontconfig</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="#ch-The_X_Window_System">The X Window System</a></dt><dt>runlevels</dt><dd><dl><dt>3, <a class="indexterm" href="#s2-x-runlevels-3">Runlevel 3</a></dt><dt>5, <a class="indexterm" href="#s2-x-runlevels-5">Runlevel 5</a></dt></dl></dd><dt>runlevels and, <a class="indexterm" href="#s1-x-runlevels">Runlevels and X</a></dt><dt>
window managers</dt><dd><dl><dt> kwin , <a class="indexterm" href="#s2-x-clients-winmanagers">Window Managers</a></dt><dt> metacity , <a class="indexterm" href="#s2-x-clients-winmanagers">Window Managers</a></dt><dt> mwm , <a class="indexterm" href="#s2-x-clients-winmanagers">Window Managers</a></dt><dt> twm , <a class="indexterm" href="#s2-x-clients-winmanagers">Window Managers</a></dt></dl></dd><dt>X clients, <a class="indexterm" href="#ch-The_X_Window_System">The X Window System</a>, <a class="indexterm" href="#s1-x-clients">Desktop Environments and Window Managers</a></dt><dd><dl><dt>desktop environments, <a class="indexterm" href="#s2-x-clients-desktop">Desktop Environments</a></dt><dt> startx command, <a class="indexterm" href="#s2-x-runlevels-3">Runlevel 3</a></dt><dt>window managers, <a class="indexterm" href="#s2-x-clients-winmanagers">Window Managers</a></dt><dt> xinit command, <a class="indexterm" href="#s2-x-runlevels-3">Runlevel 3</a></dt></dl></dd><dt>X server,
<a class="indexterm" href="#ch-The_X_Window_System">The X Window System</a></dt><dd><dl><dt>features of, <a class="indexterm" href="#s1-x-server">The X11R7.1 Release</a></dt></dl></dd></dl></dd><dt>X Window System (see X)</dt><dt>X.500 (see LDAP)</dt><dt>X.500 Lite (see LDAP)</dt><dt> xinit (see X)</dt><dt>Xorg (see Xorg)</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>di
splaying 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 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_Li
sting_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, <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="indext
erm" 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>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></dl></dd><dt>repository, <a class="indexterm" href="#sec-Creating_a_Yum_Repository">Creating a Yum Re
pository</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>variables, <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 packages, <a class="ind
exterm" 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_Draft_Documentation/0.1/html/Deployment_Guide/Acknowledgements.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Acknowledgements.html
new file mode 100644
index 0000000..4c0ac92
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Acknowledgements.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="ht
tp://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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></li></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://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Deployment_Guide/index.html">http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Deployment_Guide/index.html</a>.
+ </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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..a196f22
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/common.css
@@ -0,0 +1,1467 @@
+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: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;
+}
+
+sup {
+ color:#999;
+}
+
+/* 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 {
+ background-color:#ede7c8;
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+ color:#444;
+}
+
+.guibutton, .guilabel {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+ white-space:nowrap;
+}
+
+.example {
+ background-color:#dc9f2e;
+ padding:5px;
+ margin-bottom: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:#eeeeee;
+ 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 {
+ color:white;
+}
+
+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.note, div.important, div.warning {
+ padding:1em;
+ padding-bottom:20px;
+ margin-top:.5em;
+ margin-bottom:1.5em;
+ background-repeat:no-repeat;
+ background-position:1em 1em;
+}
+
+div.note pre, div.important pre, div.warning pre {
+ background-color: #333;
+ color: white;
+ margin-left: 4.5em;
+}
+
+
+div.note {
+ background-image:url(../images/note.png);
+ background-color:#8e9f00;
+ color:white;
+}
+
+div.important {
+ background-color:#d08e13;
+ color:white;
+ background-image:url(../images/important.png);
+}
+
+div.warning {
+ background-color:#9e292b;
+ color:white;
+ background-image:url(../images/warning.png);
+}
+
+
+/* Admonition Headings */
+div.note h2, div.important h2, div.warning h2 {
+ height:32px;
+ font-size:1.3em;
+}
+
+div.note h2, div.important h2, div.warning h2 {
+ color:white;
+}
+
+/* Admonition Inlines */
+div.note .replaceable, div.important .replaceable, div.warning .replaceable {
+ color:#e3dcc0;
+}
+
+pre .replaceable, tt .replaceable {
+ color:#444;
+}
+
+div.note .guilabel, div.important .guilabel, div.warning .guilabel {
+ color:#e3dcc0;
+}
+
+
+/* Admonition Lists ... really? */
+div.note li, div.warning li, div.important li {
+ padding-left:10px;
+ margin:0em;
+}
+
+div.note ul, div.warning ul, div.important ul {
+ padding-left:40px;
+ margin:0em;
+}
+
+/* Admonition links in verbatim ... *really* */
+div.note pre pre a:visited, div.important pre pre a:visited,
+ div.warning pre pre a:visited, div.note pre a:link, div.important pre a:link, div.warning pre a:link {
+ color:#0066cc;
+}
+
+/* Admonition links */
+div.note a:visited, div.important a:visited, div.warning a:visited, div.note a:link , div.important a:link , div.warning a:link {
+ color:#f7f2d0;
+}
+
+/*notification icons*/
+div.note h2, div.note p, div.note div.para, div.warning h2, div.warning p, div.warning div.para, div.important h2, .important p, .important div.para {
+ padding:0em;
+ margin:0em;
+ padding-left:56px;
+}
+
+/*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 {
+ padding:.2em 1em;
+ background-color:#c8c5ac;
+ font-size: .7em;
+ margin:0em;
+ margin-bottom:.5em;
+ color:#222;
+}
+
+table .footnote {
+ margin:1em .5em;
+}
+
+sup {
+ padding:0em .3em;
+ 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 {
+ color:#fff;
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:5em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+ color:white;
+}
+
+/**/
+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
+{
+ color:white;
+}
+
+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:15px;
+ -webkit-border-radius:15px;
+ border-radius: 15px;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/default.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/lang.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/overrides.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..895173d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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;
+}
+
+.edition {
+ color: #3c6eb4;
+}
+
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/print.css b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..1098dab
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/1.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..3736523
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/1.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 17.993,22.013004 L 17.993,10.113004 L 15.239,10.113004 C 14.899001,11.218003 14.286999,11.643004 12.757,11.728004 L 12.757,13.819004 L 14.763,13.819004 L 14.763,22.013004 L 17.993,22.013004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/10.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..ef058e3
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/10.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/10.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..84ee18f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/10.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.252562,22 L 12.252562,10.1 L 9.4985624,10.1 C 9.1585628,11.204999 8.5465609,11.63 7.0165624,11.715 L 7.0165624,13.806 L 9.0225624,13.806 L 9.0225624,22 L 12.252562,22 M 24.983438,16.033 C 24.983438,12.072004 22.705435,9.913 19.611438,9.913 C 16.517441,9.913 14.205438,12.106004 14.205438,16.067 C 14.205438,20.027996 16.483441,22.187 19.577438,22.187 C 22.671435,22.187 24.983438,19.993996 24.983438,16.033 M 21.600438,16.067 C 21.600438,18.242998 20.886437,19.348 19.611438,19.348 C 18.336439,19.348 17.588438,18.208998 17.588438,16.033 C 17.588438,13.857002 18.302439,12.752 19.577438,12.752 C 20.852437,12.752 21.600438,13.891002 21.600438,16.067"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/11.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..fa20ec4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/11.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/11.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..47f0c80
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/11.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 14.623052,22 L 14.623052,10.1 L 11.869052,10.1 C 11.529053,11.204999 10.917051,11.63 9.3870527,11.715 L 9.3870527,13.806 L 11.393052,13.806 L 11.393052,22 L 14.623052,22 M 21.794928,22 L 21.794928,10.1 L 19.040928,10.1 C 18.700928,11.204999 18.088926,11.63 16.558928,11.715 L 16.558928,13.806 L 18.564928,13.806 L 18.564928,22 L 21.794928,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/12.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..84c132a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/12.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/12.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..94ddaac
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/12.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.677562,22 L 12.677562,10.1 L 9.9235624,10.1 C 9.5835628,11.204999 8.9715609,11.63 7.4415624,11.715 L 7.4415624,13.806 L 9.4475624,13.806 L 9.4475624,22 L 12.677562,22 M 24.558438,22 L 24.558438,19.314 L 18.353438,19.314 C 18.608438,18.600001 19.27144,17.936999 21.651438,16.832 C 23.929436,15.778001 24.473438,14.825998 24.473438,13.262 C 24.473438,11.103002 22.926435,9.913 19.968438,9.913 C 17.92844,9.913 16.381436,10.491001 14.868438,11.46 L 16.381438,13.891 C 17.571437,13.092001 18.727439,12.684 19.917438,12.684 C 20.869437,12.684 21.243438,12.973001 21.243438,13.5 C 21.243438,13.976 21.056437,14.163001 19.798438,14.724 C 16.823441,16.049999 14.936438,17.988004 14.834438,22 L 24.558438,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/13.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..f41ec8f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/13.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/13.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..040dd6c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/13.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.550062,22 L 12.550062,10.1 L 9.7960624,10.1 C 9.4560628,11.204999 8.8440609,11.63 7.3140624,11.715 L 7.3140624,13.806 L 9.3200624,13.806 L 9.3200624,22 L 12.550062,22 M 24.685938,18.226 C 24.685938,16.713002 23.716937,15.914 22.611938,15.659 C 23.427937,15.268 24.192938,14.638999 24.192938,13.33 C 24.192938,10.814003 22.288935,9.913 19.432938,9.913 C 17.35894,9.913 15.930937,10.610001 14.825938,11.46 L 16.389938,13.602 C 17.307937,12.939001 18.191939,12.582 19.347938,12.582 C 20.520937,12.582 20.996938,12.922001 20.996938,13.551 C 20.996938,14.332999 20.656937,14.554 19.619938,14.554 L 18.089938,14.554 L 18.089938,17.121 L 19.806938,17.121 C 21.013937,17.121 21.489938,17.427001 21.489938,18.26 C 21.489938,19.075999 20.911937,19.467 19.534938,19.467 C 18.225939,19.467 17.120937,18.973999 16.151938,18.226 L 14.451938,20.368 C 15.726937,21.489999 17.44394,22.187 19.466938,22.187 C 22.696935,22.187 24.685938,20.979997 24.685938,18.226"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/14.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..c491206
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/14.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/14.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..7f4fcfd
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/14.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.040062,22 L 12.040062,10.1 L 9.2860624,10.1 C 8.9460628,11.204999 8.3340609,11.63 6.8040624,11.715 L 6.8040624,13.806 L 8.8100624,13.806 L 8.8100624,22 L 12.040062,22 M 25.195938,19.96 L 25.195938,17.172 L 23.665938,17.172 L 23.665938,10.1 L 20.401938,10.1 L 13.992938,17.461 L 13.992938,19.875 L 20.707938,19.875 L 20.707938,22 L 23.665938,22 L 23.665938,19.96 L 25.195938,19.96 M 20.758938,13.432 C 20.724938,13.992999 20.707938,15.302001 20.707938,15.999 L 20.707938,17.172 L 19.823938,17.172 C 19.007939,17.172 18.191937,17.189 17.596938,17.223 C 18.038938,16.798 18.531939,16.253999 19.160938,15.489 L 19.330938,15.285 C 20.112937,14.350001 20.435938,13.925 20.758938,13.432"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/15.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..7656c94
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/15.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/15.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..a8eba4d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/15.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.388562,22 L 12.388562,10.1 L 9.6345624,10.1 C 9.2945628,11.204999 8.6825609,11.63 7.1525624,11.715 L 7.1525624,13.806 L 9.1585624,13.806 L 9.1585624,22 L 12.388562,22 M 24.847438,17.852 C 24.847438,15.200003 23.164435,13.908 20.597438,13.908 C 19.407439,13.908 18.693437,14.112 18.030438,14.435 L 18.132438,12.786 L 24.133438,12.786 L 24.133438,10.1 L 15.463438,10.1 L 15.055438,16.271 L 17.877438,17.223 C 18.472437,16.798 19.067439,16.543 20.070438,16.543 C 21.090437,16.543 21.668438,17.019001 21.668438,17.937 C 21.668438,18.888999 21.107436,19.45 19.577438,19.45 C 18.302439,19.45 16.891437,18.956999 15.752438,18.277 L 14.409438,20.742 C 15.871436,21.625999 17.43544,22.187 19.492438,22.187 C 22.875435,22.187 24.847438,20.622997 24.847438,17.852"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/16.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..1f2535a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/16.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/16.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..1adc217
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/16.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.405562,22 L 12.405562,10.1 L 9.6515624,10.1 C 9.3115628,11.204999 8.6995609,11.63 7.1695624,11.715 L 7.1695624,13.806 L 9.1755624,13.806 L 9.1755624,22 L 12.405562,22 M 24.830438,17.903 C 24.830438,15.387003 23.096435,14.214 20.631438,14.214 C 19.203439,14.214 18.336437,14.486 17.571438,14.911 C 18.472437,13.534001 20.104441,12.616 23.215438,12.616 L 23.215438,9.913 C 16.415445,9.913 14.341438,14.112003 14.341438,17.257 C 14.341438,20.537997 16.415441,22.187 19.407438,22.187 C 22.773435,22.187 24.830438,20.588997 24.830438,17.903 M 21.651438,18.124 C 21.651438,19.075999 20.818437,19.586 19.577438,19.586 C 18.132439,19.586 17.486438,18.990999 17.486438,18.141 C 17.486438,17.206001 18.183439,16.645 19.645438,16.645 C 20.903437,16.645 21.651438,17.206001 21.651438,18.124"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/17.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..67fe7ce
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/17.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/17.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..b007799
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/17.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.652062,22 L 12.652062,10.1 L 9.8980624,10.1 C 9.5580628,11.204999 8.9460609,11.63 7.4160624,11.715 L 7.4160624,13.806 L 9.4220624,13.806 L 9.4220624,22 L 12.652062,22 M 24.583938,12.48 L 24.583938,10.1 L 14.740938,10.1 L 14.740938,12.786 L 20.656938,12.786 C 18.36194,15.131998 17.239938,17.920004 17.205938,22 L 20.435938,22 C 20.435938,18.141004 21.098941,15.675997 24.583938,12.48"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/18.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..76aa05b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/18.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/18.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..140c8ec
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/18.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.176062,22 L 12.176062,10.1 L 9.4220624,10.1 C 9.0820628,11.204999 8.4700609,11.63 6.9400624,11.715 L 6.9400624,13.806 L 8.9460624,13.806 L 8.9460624,22 L 12.176062,22 M 25.059938,18.294 C 25.059938,16.764002 23.971937,15.948 23.206938,15.642 C 23.954937,15.166 24.549938,14.519999 24.549938,13.449 C 24.549938,11.171002 22.526935,9.913 19.653938,9.913 C 16.780941,9.913 14.723938,11.171002 14.723938,13.449 C 14.723938,14.519999 15.352939,15.251 16.066938,15.676 C 15.301939,15.982 14.213938,16.764002 14.213938,18.294 C 14.213938,20.707998 16.287941,22.187 19.619938,22.187 C 22.951935,22.187 25.059938,20.707998 25.059938,18.294 M 21.387938,13.5 C 21.387938,14.094999 20.945937,14.639 19.653938,14.639 C 18.361939,14.639 17.885938,14.094999 17.885938,13.5 C 17.885938,12.905001 18.327939,12.31 19.619938,12.31 C 20.911937,12.31 21.387938,12.905001 21.387938,13.5 M 21.897938,18.26 C 21.897938,19.075999 21.149936,19.688 19.653938,19.688 C 18.157939,19.688 17.375938,19.07599
9 17.375938,18.26 C 17.375938,17.444001 18.106939,16.849 19.619938,16.849 C 21.115936,16.849 21.897938,17.444001 21.897938,18.26"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/19.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..5f5ada0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/19.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/19.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..ae864c4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/19.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 12.414062,22 L 12.414062,10.1 L 9.6600624,10.1 C 9.3200628,11.204999 8.7080609,11.63 7.1780624,11.715 L 7.1780624,13.806 L 9.1840624,13.806 L 9.1840624,22 L 12.414062,22 M 24.821938,14.843 C 24.821938,11.562003 22.747935,9.913 19.755938,9.913 C 16.389941,9.913 14.332938,11.511003 14.332938,14.197 C 14.332938,16.712997 16.06694,17.886 18.531938,17.886 C 19.959937,17.886 20.826939,17.614 21.591938,17.189 C 20.690939,18.565999 19.058935,19.484 15.947938,19.484 L 15.947938,22.187 C 22.747931,22.187 24.821938,17.987997 24.821938,14.843 M 21.676938,13.959 C 21.676938,14.893999 20.979936,15.455 19.517938,15.455 C 18.259939,15.455 17.511938,14.893999 17.511938,13.976 C 17.511938,13.024001 18.344939,12.514 19.585938,12.514 C 21.030936,12.514 21.676938,13.109001 21.676938,13.959"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..8fe3709
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/2.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..ee96128
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/2.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 20.862,22.013004 L 20.862,19.327004 L 14.657,19.327004 C 14.912,18.613005 15.575003,17.950003 17.955,16.845004 C 20.232998,15.791005 20.777,14.839003 20.777,13.275004 C 20.777,11.116006 19.229997,9.9260043 16.272,9.9260043 C 14.232002,9.9260043 12.684999,10.504005 11.172,11.473004 L 12.685,13.904004 C 13.874999,13.105005 15.031001,12.697004 16.221,12.697004 C 17.172999,12.697004 17.547,12.986005 17.547,13.513004 C 17.547,13.989004 17.359999,14.176005 16.102,14.737004 C 13.127003,16.063003 11.24,18.001008 11.138,22.013004 L 20.862,22.013004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/20.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..5e2ad33
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/20.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/20.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..1678a9f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/20.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 14.685,22 L 14.685,19.314 L 8.4799999,19.314 C 8.7349997,18.600001 9.3980023,17.936999 11.778,16.832 C 14.055998,15.778001 14.6,14.825998 14.6,13.262 C 14.6,11.103002 13.052997,9.913 10.095,9.913 C 8.055002,9.913 6.5079984,10.491001 4.9949999,11.46 L 6.5079999,13.891 C 7.6979988,13.092001 8.8540011,12.684 10.044,12.684 C 10.995999,12.684 11.37,12.973001 11.37,13.5 C 11.37,13.976 11.182999,14.163001 9.9249999,14.724 C 6.9500029,16.049999 5.0629998,17.988004 4.9609999,22 L 14.685,22 M 27.421719,16.033 C 27.421719,12.072004 25.143716,9.913 22.049719,9.913 C 18.955722,9.913 16.643719,12.106004 16.643719,16.067 C 16.643719,20.027996 18.921722,22.187 22.015719,22.187 C 25.109716,22.187 27.421719,19.993996 27.421719,16.033 M 24.038719,16.067 C 24.038719,18.242998 23.324717,19.348 22.049719,19.348 C 20.77472,19.348 20.026719,18.208998 20.026719,16.033 C 20.026719,13.857002 20.74072,12.752 22.015719,12.752 C 23.290717,12.752 24.038719,13.891002 24.038719,16.067"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/21.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..cfafd1f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/21.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/21.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..4199512
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/21.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 16.648141,22 L 16.648141,19.314 L 10.44314,19.314 C 10.69814,18.600001 11.361143,17.936999 13.741141,16.832 C 16.019139,15.778001 16.563141,14.825998 16.563141,13.262 C 16.563141,11.103002 15.016138,9.913 12.058141,9.913 C 10.018143,9.913 8.471139,10.491001 6.9581405,11.46 L 8.4711405,13.891 C 9.661139,13.092001 10.817142,12.684 12.007141,12.684 C 12.95914,12.684 13.333141,12.973001 13.333141,13.5 C 13.333141,13.976 13.14614,14.163001 11.88814,14.724 C 8.9131435,16.049999 7.0261404,17.988004 6.9241405,22 L 16.648141,22 M 23.82586,22 L 23.82586,10.1 L 21.07186,10.1 C 20.73186,11.204999 20.119858,11.63 18.58986,11.715 L 18.58986,13.806 L 20.59586,13.806 L 20.59586,22 L 23.82586,22"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/22.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..5415d35
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/22.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/22.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..c1f4479
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/22.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 14.685,22 L 14.685,19.314 L 8.4799999,19.314 C 8.7349997,18.600001 9.3980023,17.936999 11.778,16.832 C 14.055998,15.778001 14.6,14.825998 14.6,13.262 C 14.6,11.103002 13.052997,9.913 10.095,9.913 C 8.055002,9.913 6.5079984,10.491001 4.9949999,11.46 L 6.5079999,13.891 C 7.6979988,13.092001 8.8540011,12.684 10.044,12.684 C 10.995999,12.684 11.37,12.973001 11.37,13.5 C 11.37,13.976 11.182999,14.163001 9.9249999,14.724 C 6.9500029,16.049999 5.0629998,17.988004 4.9609999,22 L 14.685,22 M 26.571719,22 L 26.571719,19.314 L 20.366719,19.314 C 20.621718,18.600001 21.284721,17.936999 23.664719,16.832 C 25.942716,15.778001 26.486719,14.825998 26.486719,13.262 C 26.486719,11.103002 24.939716,9.913 21.981719,9.913 C 19.941721,9.913 18.394717,10.491001 16.881719,11.46 L 18.394719,13.891 C 19.584718,13.092001 20.74072,12.684 21.930719,12.684 C 22.882718,12.684 23.256719,12.973001 23.256719,13.5 C 23.256719,13.976 23.069717,14.163001 21.811719,14.724 C 18.836722,16.049999 16.94971
9,17.988004 16.847719,22 L 26.571719,22"
+ id="number"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/23.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..658e22b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/23.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/23.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..ea3c85a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/23.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 15.32239,22.013004 L 15.32239,19.327004 L 9.1173907,19.327004 C 9.3723904,18.613005 10.035393,17.950003 12.41539,16.845004 C 14.693388,15.791005 15.23739,14.839003 15.23739,13.275004 C 15.23739,11.116006 13.690387,9.9260043 10.73239,9.9260043 C 8.6923927,9.9260043 7.1453891,10.504005 5.6323906,11.473004 L 7.1453906,13.904004 C 8.3353896,13.105005 9.4913919,12.697004 10.68139,12.697004 C 11.633389,12.697004 12.00739,12.986005 12.00739,13.513004 C 12.00739,13.989004 11.820389,14.176005 10.56239,14.737004 C 7.5873937,16.063003 5.7003905,18.001008 5.5983906,22.013004 L 15.32239,22.013004 M 26.401609,18.239004 C 26.401609,16.726006 25.432608,15.927004 24.327609,15.672004 C 25.143608,15.281005 25.908609,14.652003 25.908609,13.343004 C 25.908609,10.827007 24.004606,9.9260043 21.148609,9.9260043 C 19.074611,9.9260043 17.646608,10.623005 16.541609,11.473004 L 18.105609,13.615004 C 19.023608,12.952005 19.90761,12.595004 21.063609,12.595004 C 22.236608,12.595004 22.712609,12.
935005 22.712609,13.564004 C 22.712609,14.346004 22.372608,14.567004 21.335609,14.567004 L 19.805609,14.567004 L 19.805609,17.134004 L 21.522609,17.134004 C 22.729608,17.134004 23.205609,17.440005 23.205609,18.273004 C 23.205609,19.089003 22.627608,19.480004 21.250609,19.480004 C 19.94161,19.480004 18.836608,18.987004 17.867609,18.239004 L 16.167609,20.381004 C 17.442608,21.503003 19.159611,22.200004 21.182609,22.200004 C 24.412606,22.200004 26.401609,20.993002 26.401609,18.239004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..449ef5a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/3.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..d3a7e73
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/3.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 21.117,18.239004 C 21.117,16.726006 20.147999,15.927004 19.043,15.672004 C 19.858999,15.281005 20.624,14.652003 20.624,13.343004 C 20.624,10.827007 18.719997,9.9260043 15.864,9.9260043 C 13.790002,9.9260043 12.361999,10.623005 11.257,11.473004 L 12.821,13.615004 C 13.738999,12.952005 14.623001,12.595004 15.779,12.595004 C 16.951999,12.595004 17.428,12.935005 17.428,13.564004 C 17.428,14.346004 17.087999,14.567004 16.051,14.567004 L 14.521,14.567004 L 14.521,17.134004 L 16.238,17.134004 C 17.444999,17.134004 17.921,17.440005 17.921,18.273004 C 17.921,19.089003 17.342999,19.480004 15.966,19.480004 C 14.657002,19.480004 13.551999,18.987004 12.583,18.239004 L 10.883,20.381004 C 12.157999,21.503003 13.875002,22.200004 15.898,22.200004 C 19.127997,22.200004 21.117,20.993002 21.117,18.239004"
+ id="text2207"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..0a2634a
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/4.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..e6bbe8e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/4.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 20.573772,19.96 L 20.573772,17.172 L 19.043772,17.172 L 19.043772,10.1 L 15.779772,10.1 L 9.3707718,17.461 L 9.3707718,19.875 L 16.085772,19.875 L 16.085772,22 L 19.043772,22 L 19.043772,19.96 L 20.573772,19.96 M 16.136772,13.432 C 16.102772,13.992999 16.085772,15.302001 16.085772,15.999 L 16.085772,17.172 L 15.201772,17.172 C 14.385773,17.172 13.569771,17.189 12.974772,17.223 C 13.416772,16.798 13.909773,16.253999 14.538772,15.489 L 14.708772,15.285 C 15.490771,14.350001 15.813772,13.925 16.136772,13.432"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..bc1d337
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/5.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..d8578f2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/5.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 21.219,17.852 C 21.219,15.200003 19.535997,13.908 16.969,13.908 C 15.779001,13.908 15.064999,14.112 14.402,14.435 L 14.504,12.786 L 20.505,12.786 L 20.505,10.1 L 11.835,10.1 L 11.427,16.271 L 14.249,17.223 C 14.843999,16.798 15.439001,16.543 16.442,16.543 C 17.461999,16.543 18.04,17.019001 18.04,17.937 C 18.04,18.888999 17.478998,19.45 15.949,19.45 C 14.674001,19.45 13.262999,18.956999 12.124,18.277 L 10.781,20.742 C 12.242999,21.625999 13.807002,22.187 15.864,22.187 C 19.246997,22.187 21.219,20.622997 21.219,17.852"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..68cb4b6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/6.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..14d62e0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/6.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 21.2445,17.903 C 21.2445,15.387003 19.510497,14.214 17.0455,14.214 C 15.617501,14.214 14.750499,14.486 13.9855,14.911 C 14.886499,13.534001 16.518503,12.616 19.6295,12.616 L 19.6295,9.913 C 12.829507,9.913 10.7555,14.112003 10.7555,17.257 C 10.7555,20.537997 12.829503,22.187 15.8215,22.187 C 19.187497,22.187 21.2445,20.588997 21.2445,17.903 M 18.0655,18.124 C 18.0655,19.075999 17.232499,19.586 15.9915,19.586 C 14.546501,19.586 13.9005,18.990999 13.9005,18.141 C 13.9005,17.206001 14.597501,16.645 16.0595,16.645 C 17.317499,16.645 18.0655,17.206001 18.0655,18.124"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..3b6cc72
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/7.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..8d71ee3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/7.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 20.9215,12.48 L 20.9215,10.1 L 11.0785,10.1 L 11.0785,12.786 L 16.9945,12.786 C 14.699502,15.131998 13.5775,17.920004 13.5435,22 L 16.7735,22 C 16.7735,18.141004 17.436503,15.675997 20.9215,12.48"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/8.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..b092185
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/8.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..1c31e86
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/8.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 21.423,18.294 C 21.423,16.764002 20.334999,15.948 19.57,15.642 C 20.317999,15.166 20.913,14.519999 20.913,13.449 C 20.913,11.171002 18.889997,9.913 16.017,9.913 C 13.144003,9.913 11.087,11.171002 11.087,13.449 C 11.087,14.519999 11.716001,15.251 12.43,15.676 C 11.665001,15.982 10.577,16.764002 10.577,18.294 C 10.577,20.707998 12.651003,22.187 15.983,22.187 C 19.314997,22.187 21.423,20.707998 21.423,18.294 M 17.751,13.5 C 17.751,14.094999 17.308999,14.639 16.017,14.639 C 14.725001,14.639 14.249,14.094999 14.249,13.5 C 14.249,12.905001 14.691001,12.31 15.983,12.31 C 17.274999,12.31 17.751,12.905001 17.751,13.5 M 18.261,18.26 C 18.261,19.075999 17.512998,19.688 16.017,19.688 C 14.521001,19.688 13.739,19.075999 13.739,18.26 C 13.739,17.444001 14.470002,16.849 15.983,16.849 C 17.478998,16.849 18.261,17.444001 18.261,18.26"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/9.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..7706583
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/9.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..851e9a3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/9.svg
@@ -0,0 +1,22 @@
+<?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:#aa0000" />
+ <path
+ d="M 22.128383,14.843 C 22.128383,11.562003 20.05438,9.913 17.062383,9.913 C 13.696386,9.913 11.639383,11.511003 11.639383,14.197 C 11.639383,16.712997 13.373385,17.886 15.838383,17.886 C 17.266382,17.886 18.133384,17.614 18.898383,17.189 C 17.997384,18.565999 16.36538,19.484 13.254383,19.484 L 13.254383,22.187 C 20.054376,22.187 22.128383,17.987997 22.128383,14.843 M 18.983383,13.959 C 18.983383,14.893999 18.286381,15.455 16.824383,15.455 C 15.566384,15.455 14.818383,14.893999 14.818383,13.976 C 14.818383,13.024001 15.651384,12.514 16.892383,12.514 C 18.337381,12.514 18.983383,13.109001 18.983383,13.959"
+ id="text2219"
+ style="fill:#ffffff" />
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/documentation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/dot.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/dot2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/h1-bg.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/image_left.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/image_right.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/important.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/important.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/important.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/logo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/note.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/note.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/note.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/redhat-logo.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/redhat-logo.svg
new file mode 100644
index 0000000..1001776
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/redhat-logo.svg
@@ -0,0 +1,94 @@
+<?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://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"
+ width="300"
+ height="140"
+ id="svg2812"
+ sodipodi:version="0.32"
+ inkscape:version="0.45+devel"
+ version="1.0"
+ sodipodi:docname="redhat-logo.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape">
+ <defs
+ id="defs3" />
+ <sodipodi:namedview
+ inkscape:document-units="mm"
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="1"
+ inkscape:cx="174.26394"
+ inkscape:cy="40.358463"
+ inkscape:current-layer="layer1"
+ inkscape:window-width="722"
+ inkscape:window-height="523"
+ inkscape:window-x="71"
+ inkscape:window-y="636"
+ width="300px"
+ height="140px" />
+ <metadata
+ id="metadata4">
+ <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>
+ <g
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ id="layer1"
+ transform="translate(-13.714282,-252.57246)">
+ <g
+ transform="matrix(2.1166666,0,0,2.1166666,-32.193429,187.76029)"
+ id="shadowman">
+ <path
+ d="M 55.68466,68.503937 C 55.68466,79.688581 46.617715,88.755526 35.433071,88.755526 C 24.248427,88.755526 15.181482,79.688581 15.181482,68.503937 C 15.181482,57.319293 24.248427,48.252348 35.433071,48.252348 C 46.617715,48.252348 55.68466,57.319293 55.68466,68.503937 z"
+ transform="matrix(1.10693,0,0,1.10693,5.005761,-12.00975)"
+ style="fill:#ffffff"
+ id="path4548" />
+ <path
+ d="M 147.81332,72.126073 C 147.81332,73.329962 147.86057,74.57586 148.03519,75.740362 L 146.64882,75.740362 L 146.42826,73.559712 L 146.35605,73.559712 C 145.61822,74.733404 143.92333,76.086957 141.50635,76.086957 C 138.4461,76.086957 137.02164,73.933874 137.02164,71.904202 C 137.02164,68.394942 140.11998,66.27862 146.30878,66.34295 L 146.30878,65.937278 C 146.30878,64.432747 146.01471,61.431561 142.41879,61.45388 C 141.08756,61.45388 139.70118,61.810976 138.5997,62.588186 L 138.1205,61.494579 C 139.51083,60.551948 141.20703,60.180411 142.58291,60.180411 C 146.97178,60.180411 147.81201,63.475677 147.81201,66.194597 L 147.81201,72.126073 L 147.81332,72.126073 z M 146.30878,67.609855 C 142.99645,67.514016 138.62333,68.015527 138.62333,71.667888 C 138.62333,73.853791 140.06616,74.835806 141.65077,74.835806 C 144.1859,74.835806 145.62742,73.266945 146.15124,71.786044 C 146.26152,71.460456 146.3101,71.134869 146.3101,70.874924 L 146.3101,67.609855 L 146.30878,67.609855 z
M 153.80387,57.175286 L 153.80387,60.527004 L 158.13891,60.527004 L 158.13891,61.747959 L 153.80387,61.747959 L 153.80387,71.635066 C 153.80387,73.568902 154.40385,74.780665 156.03835,74.780665 C 156.82343,74.780665 157.37877,74.676951 157.76606,74.541727 L 157.94856,75.707542 C 157.45754,75.912347 156.76567,76.072514 155.84798,76.072514 C 154.73862,76.072514 153.81831,75.723296 153.22358,74.994662 C 152.53566,74.195133 152.29934,72.917726 152.29934,71.365932 L 152.29934,61.746646 L 149.7314,61.746646 L 149.7314,60.525692 L 152.29934,60.525692 L 152.29934,57.729312 L 153.80387,57.175286 z M 129.02767,60.179099 C 127.87105,60.179099 126.8339,60.512563 125.96348,61.052146 C 125.05891,61.581226 124.3224,62.399135 123.88522,63.247239 L 123.8222,63.247239 L 123.8222,55.719331 L 122.31767,55.309721 L 122.31767,75.740362 L 123.8222,75.740362 L 123.8222,66.437475 C 123.8222,65.819121 123.86947,65.39113 124.02832,64.938196 C 124.67818,63.046372 126.45974,61.493265 128.61545,61.49326
5 C 131.72953,61.493265 132.80739,63.990315 132.80739,66.730242 L 132.80739,75.73905 L 134.31191,75.73905 L 134.31191,66.564822 C 134.31191,60.899855 130.4692,60.179099 129.02767,60.179099 z"
+ id="path620" />
+ <path
+ d="M 78.208384,65.270348 C 78.208384,63.205228 78.16506,61.686255 78.08235,60.311696 L 81.460325,60.311696 L 81.604739,63.240675 L 81.713705,63.240675 C 82.473849,61.069213 84.273772,59.961164 85.938472,59.961164 C 86.319199,59.961164 86.541071,59.976918 86.853532,60.045187 L 86.853532,63.719867 C 86.488557,63.648972 86.147215,63.609587 85.677213,63.609587 C 83.819525,63.609587 82.528988,64.792469 82.181081,66.560884 C 82.115438,66.904852 82.079992,67.318401 82.079992,67.738514 L 82.079992,75.73905 L 78.176875,75.73905 L 78.208384,65.270348 z M 91.56274,69.076313 C 91.666455,71.871381 93.83004,73.093647 96.328402,73.093647 C 98.123074,73.093647 99.405732,72.814009 100.58599,72.379455 L 101.16365,75.064243 C 99.842914,75.623519 98.010169,76.042319 95.771752,76.042319 C 90.763211,76.042319 87.82767,72.949234 87.82767,68.220332 C 87.82767,63.961432 90.411366,59.933594 95.372644,59.933594 C 100.38906,59.933594 102.02225,64.059896 102.02225,67.436558 C 102.02225,68.16256
6 101.95792,68.744161 101.88309,69.103883 L 91.56274,69.076313 z M 98.348885,66.358704 C 98.365952,64.929006 97.743659,62.59869 95.129766,62.59869 C 92.728556,62.59869 91.730785,64.778027 91.554863,66.358704 L 98.348885,66.358704 z M 118.82942,54.363153 L 114.93024,53.307617 L 114.93024,61.97377 L 114.8659,61.97377 C 114.17665,60.834212 112.65375,59.962477 110.54268,59.962477 C 106.83386,59.962477 103.60162,63.033244 103.62656,68.201952 C 103.62656,72.945296 106.54372,76.086957 110.22759,76.086957 C 112.45288,76.086957 114.31582,75.024857 115.23745,73.297141 L 115.30703,73.297141 L 115.48164,75.73905 L 118.95675,75.73905 C 118.88586,74.690078 118.82809,72.991246 118.82809,71.411881 L 118.82809,54.363153 L 118.82942,54.363153 z M 114.92893,69.050056 C 114.92893,69.459667 114.90136,69.840395 114.81077,70.189614 C 114.41823,71.877945 113.0371,72.966301 111.44198,72.966301 C 108.98563,72.966301 107.57957,70.894617 107.57957,68.060164 C 107.57957,65.198141 108.97382,62.983355 111
.48662,62.983355 C 113.2406,62.983355 114.49568,64.220064 114.84228,65.72197 C 114.90922,66.038368 114.92893,66.428286 114.92893,66.738119 L 114.92893,69.050056 L 114.92893,69.050056 z"
+ id="path616" />
+ <path
+ d="M 161.80517,73.528501 C 160.90479,73.528501 160.18937,74.243893 160.18939,75.144292 C 160.18939,76.044668 160.90478,76.760094 161.80517,76.760081 C 162.70554,76.760081 163.42095,76.041202 163.42097,75.144292 C 163.42097,74.24046 162.70554,73.528501 161.80517,73.528501 z M 161.80517,73.803529 C 162.54687,73.803529 163.14594,74.402585 163.14593,75.144292 C 163.14593,75.882533 162.54342,76.485053 161.80517,76.485053 C 161.06348,76.485053 160.46441,75.882523 160.46441,75.144292 C 160.46441,74.402596 161.06346,73.80354 161.80517,73.803529 z M 161.25512,74.319207 L 161.25512,75.969376 L 161.49577,75.969376 L 161.49577,75.247426 L 161.80517,75.247426 L 162.2521,75.969376 L 162.52712,75.969376 L 162.04582,75.247426 C 162.29078,75.216382 162.49274,75.06625 162.49274,74.766128 C 162.49273,74.438393 162.30159,74.319207 161.90832,74.319207 L 161.25512,74.319207 z M 161.49577,74.525479 L 161.83955,74.525479 C 162.0155,74.525467 162.21771,74.562596 162.21771,74.766128 C 162.21
773,75.02142 162.01906,75.041156 161.80517,75.041156 L 161.49577,75.041156 L 161.49577,74.525479 z"
+ id="path650" />
+ <path
+ d="M 63.115808,76.090895 C 60.810796,75.504093 58.522203,75.797079 56.285026,76.486064 C 56.010655,76.526189 56.159301,76.830359 56.114355,76.953441 C 56.240389,77.319727 56.032958,77.717522 54.998429,77.944646 C 53.465014,78.282048 52.496128,79.864039 51.942103,80.389181 C 51.290927,81.007536 49.45293,81.388262 49.729943,81.01935 C 49.946565,80.730522 50.773662,79.83253 51.276485,78.861018 C 51.726795,77.99322 52.127215,77.746405 52.678614,76.919305 C 52.841408,76.676428 53.46764,75.824385 53.650127,75.149578 C 53.854932,74.490525 53.786663,73.663427 53.865435,73.323398 C 53.97834,72.83239 54.440465,71.767665 54.477226,71.166377 C 54.496918,70.825035 53.056716,71.650821 52.372719,71.650821 C 51.688722,71.650821 51.024417,71.242523 50.412627,71.21364 C 49.657736,71.17688 49.17198,71.795235 48.489295,71.68758 C 48.098065,71.625877 47.769852,71.281909 47.087167,71.255652 C 46.115654,71.220205 44.928834,71.795235 42.698294,71.724341 C 40.507139,71.653447 38.480092,68.9
52905 38.204394,68.523601 C 37.880118,68.019465 37.484949,68.019465 37.054333,68.414634 C 36.622404,68.809804 36.090697,68.498657 35.939718,68.234773 C 35.652203,67.73195 34.882871,66.258927 33.692111,65.951719 C 32.044479,65.523729 31.210817,66.864153 31.31847,67.928878 C 31.427438,69.010669 32.127189,69.31394 32.451465,69.887656 C 32.77574,70.462687 32.94116,70.834225 33.54901,71.088919 C 33.980939,71.267467 34.142421,71.53529 34.013762,71.888448 C 33.900856,72.198281 33.451859,72.269175 33.156467,72.282304 C 31.933813,72.291845 31.468231,71.67907 30.76576,70.807968 C 30.388969,70.188301 29.79556,69.919166 29.103685,69.919166 C 28.774159,69.919166 28.465638,70.005814 28.191252,70.147603 C 27.106833,70.710817 25.817611,71.045595 24.429922,71.045595 L 22.863688,71.045595 C 22.102232,68.784859 21.688683,66.365268 21.688683,63.847213 C 21.688683,51.409229 31.770093,41.32782 44.208077,41.32782 C 56.646061,41.32782 66.72747,51.410542 66.72747,63.847213 C 66.730097,68.36212 65.40
1488,72.565881 63.115808,76.090895 z M 49.170707,74.025807 C 49.286239,74.138712 49.485793,74.518127 49.241602,75.001258 C 49.105065,75.257265 48.956712,75.437126 48.694141,75.647183 C 48.37643,75.900564 47.758075,76.194643 46.908658,75.65506 C 46.451785,75.364919 46.424215,75.267768 45.794044,75.349165 C 45.343735,75.408243 45.163874,74.953995 45.326668,74.575893 C 45.488149,74.199104 46.152454,73.893208 46.980865,74.378965 C 47.353716,74.598211 47.932685,75.059024 48.44076,74.649413 C 48.65213,74.481367 48.778164,74.368462 49.069618,74.031058 C 49.082746,74.015304 49.101126,74.007427 49.122132,74.007427 C 49.140512,74.007427 49.157579,74.013991 49.170707,74.025807 z"
+ id="path632" />
+ <path
+ d="M 63.115853,76.089615 C 65.401534,72.564599 66.72883,68.36215 66.72883,63.849868 C 66.72883,51.411879 56.647417,41.330466 44.209428,41.330466 C 31.77144,41.330466 21.690027,51.413192 21.690027,63.849868 C 21.690027,66.367923 22.103576,68.787515 22.865032,71.046939 C 25.868844,79.95466 34.290809,86.367957 44.209428,86.367957 C 52.133821,86.367957 59.101143,82.275788 63.115853,76.089615 z"
+ style="fill:none"
+ id="path646" />
+ <path
+ d="M 56.917822,57.857972 C 56.694636,58.606299 56.378238,59.562056 54.970858,60.285439 C 54.766053,60.390468 54.687282,60.218483 54.781807,60.057003 C 55.313513,59.151133 55.409352,58.925322 55.562956,58.568226 C 55.779577,58.047022 55.892482,57.303946 55.463179,55.754779 C 54.615075,52.707643 52.849285,48.633855 51.564001,47.31181 C 50.32598,46.037029 48.079686,45.677306 46.050011,46.19851 C 45.302998,46.390186 43.839164,47.151642 41.126807,46.539852 C 36.433353,45.483004 35.738853,47.833013 35.468405,48.857041 C 35.197956,49.881066 34.552032,52.791666 34.552032,52.791666 C 34.33541,53.977174 34.05446,56.038354 41.342116,57.426043 C 44.737158,58.071966 44.910455,58.950266 45.060119,59.58175 C 45.329254,60.712117 45.761183,61.360667 46.245627,61.682316 C 46.731383,62.006591 46.245627,62.274414 45.707356,62.329554 C 44.260592,62.480532 38.917273,60.947118 35.754607,59.151133 C 33.168283,57.570457 33.124958,56.147322 33.717056,54.939495 C 29.808689,54.516756 26.877084
,55.304469 26.345378,57.155594 C 25.431631,60.330077 33.324513,65.752165 42.311003,68.473712 C 51.741236,71.329172 61.440606,69.336258 62.519772,63.40872 C 63.012093,60.71343 60.74348,58.721829 56.917822,57.857972 z M 42.458041,52.053841 C 39.857276,52.241579 39.586829,52.52253 39.099759,53.041108 C 38.411824,53.772368 37.507268,52.090601 37.507268,52.090601 C 36.965059,51.976382 36.306006,51.100708 36.661789,50.2828 C 37.012321,49.474082 37.658246,49.71696 37.860425,49.969029 C 38.107242,50.274923 38.633697,50.777747 39.315068,50.759366 C 39.997753,50.7423 40.785465,50.597886 41.884324,50.597886 C 42.998938,50.597886 43.745953,51.014061 43.789276,51.371156 C 43.823411,51.675739 43.698689,51.964567 42.458041,52.053841 z M 45.191406,47.754243 C 45.187466,47.754243 45.183528,47.755556 45.179589,47.755556 C 45.138891,47.755556 45.107383,47.72536 45.107383,47.687287 C 45.107383,47.659717 45.123137,47.636085 45.14808,47.625583 C 45.652218,47.359073 46.404482,47.147704 47.265715,4
7.059743 C 47.524347,47.032172 47.776416,47.019045 48.019294,47.016418 C 48.062617,47.016418 48.103316,47.016418 48.147954,47.017731 C 49.592094,47.04924 50.746092,47.622957 50.729025,48.299078 C 50.711958,48.973884 49.527763,49.495088 48.084936,49.46358 C 47.617561,49.453076 47.179067,49.384807 46.800965,49.275842 C 46.756328,49.264025 46.723506,49.225952 46.723506,49.181315 C 46.723506,49.135365 46.756328,49.097292 46.802278,49.08679 C 47.702895,48.878046 48.310747,48.538016 48.268737,48.215055 C 48.212283,47.788376 47.03334,47.557315 45.637776,47.696476 C 45.484171,47.713544 45.334507,47.733237 45.191406,47.754243 z"
+ style="fill:#cc0000"
+ id="path648" />
+ <use
+ transform="translate(-94.61853,1.913321)"
+ id="use4312"
+ x="0"
+ y="0"
+ width="744.09448"
+ height="1052.3622"
+ xlink:href="#path650" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/rhlogo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/rhlogo.png
new file mode 100644
index 0000000..ecd4856
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/rhlogo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/shade.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/shine.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/stock-go-back.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/stock-go-forward.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/stock-go-up.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/stock-home.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/title_logo.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/title_logo.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/warning.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/warning.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/watermark-draft.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/app-Revision_History.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/app-Revision_History.html
new file mode 100644
index 0000000..1abe145
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/app-Revision_History.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="s1-kernel-modules-additional-resources.html" title="30.6. Additional Resources" /><link rel="next" href="ix01.html" title="Index" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"
><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="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 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 Deployment Guide</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-modules-additional-resources.html"><strong>Prev</strong>30.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="ix01.html"><strong>Next</strong>Index</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Authentication_Configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Authentication_Configuration.html
new file mode 100644
index 0000000..500fbc8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Authentication_Configuration.html
@@ -0,0 +1,421 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-ldap-related-books.html" title="14.9.3. Related Books" /><link rel="next" href="chap-SSSD_User_Guide-Introduction.html" title="15.2. The System Security Services Daemon (SSSD)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.htm
l">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-related-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 15. Authentication Configuration" id="ch-Authentication_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Authentication Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configurat
ion_Tool">15.1. The Authentication Configuration Tool</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">15.1.1. Identity & Authentication</a></span></dt><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">15.1.2. Advanced Options</a></span></dt><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">15.1.3. Command Line Version</a></span></dt></dl></dd><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html">15.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html#sect-SSSD_User_Guide-Introduction-What_is_SSSD">15.2.1. What is SSSD?</a></span></dt><dt><span class="section"><a href="sect-SSSD_
User_Guide-Introduction-SSSD_Features.html">15.2.2. SSSD Features</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Setting_Up_SSSD.html">15.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Services.html">15.2.4. Configuring Services</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Domains.html">15.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">15.2.6. Setting up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Troubleshooting.html">15.2.7. Troubleshooting</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html">15.2.8. SSSD Configuration File Format</a></span></dt></dl></dd></dl></div><div class="section" title="15.1. The Authent
ication 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">15.1. The Authentication Configuration Tool</h2></div></div></div><a id="id932338" class="indexterm"></a><a id="id932177" 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"><h2>Note</h2><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 section <em class="citetitle">Firewalls</em> of the <em class="citetitle">Security Guide</em>
+ </div></div><a id="id932253" class="indexterm"></a><a id="id932230" 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"><h2>Important</h2><div class="para">
+ After exiting the authentication program, any changes you made take effect immediately.
+ </div></div><div class="section" title="15.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">15.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 15.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 15.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>LDAP</h4><a id="id932116" 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"><h2>Important</h2><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 class="para">
+ For more information about CA Certificates, refer to <a class="xref" href="s2-secureserver-overview-certs.html" title="11.8.2. An Overview of Certificates and Security">Section 11.8.2, “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">
+ For more information about LDAP, refer to <a class="xref" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)">Chapter 14, <i>Lightweight Directory Access Protocol (LDAP)</i></a>
+ </div><div class="para">
+ LDAP provides the following methods of authentication:
+ </div><div class="itemizedlist"><ul><li class="listitem"><a id="id676179" 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"> "Kerberos"</em> of the <em class="citetitle">Security Guide</em>.
+ </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"><h2>Note</h2><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="15.2. The System Security Services Daemon (SSSD)">Section 15.2, “The System Security Services Daemon (SSSD)”</a>
+ </div></div><h4>NIS</h4><a id="id727599" 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 section <em class="citetitle">"Securing NIS"</em> of the <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="id727503" 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>Winbind</h4><a id="id727471" 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. For more information about domain controllers, please refer to <a class="xref" href="s2-samba-domain-controller.html" title="9.6.3. Domain Controller">Section 9.6.3, “Domain Controller”</a>.
+ </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><div class="para">
+ For more information about the <code class="command">winbindd</code> service, refer to <a class="xref" href="s1-samba-daemons.html" title="9.2. Samba Daemons and Related Services">Section 9.2, “Samba Daemons and Related Services”</a>.
+ </div><a id="id974426" 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="15.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">15.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 15.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 15.2. <span class="guilabel">Advanced Options</span></h6></div><br class="figure-break" /><h4>Local Authentication Options</h4><div class="itemizedlist"><ul><li class="listitem"><a id="id974330" 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>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>Smart Card Authentication Options</h4><a id="id974249" 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 <em class="citetitle">Managing Smart Cards with the Enterprise Security Client</em> guide. <div class="note"><h2>Note</h2><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 class="section" title="15.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">15.1.3. Command Line Version</h3></div></div></div><a id="id743341" 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 15.1. Command Line Options">Table 15.1, “Command Line Options”</a>.
+ </div><div class="note"><h2>Tip</h2><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 class="table" title="Table 15.1. Command Line Options" id="tb-authconfig-cmd-line"><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><h6>Table 15.1. Command Line Options</h6></div><br class="table-break" /></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ldap-related-books.html"><strong>Prev</strong>14.9.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="chap-SSSD_User_Guide-Introduction.html"><strong>Next</strong>15.2. The System Security Services Daemon (SSSD)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Automated_Tasks.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Automated_Tasks.html
new file mode 100644
index 0000000..dc6daf6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Automated_Tasks.html
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-printing-useful-websites.html" title="23.9.2. Useful Websites" /><link rel="next" href="s1-autotasks-at-batch.html" title="24.2. At and Batch" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifra
me display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-printing-useful-websites.html"><strong>Prev</strong></a></li><li class="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 24. Automated Tasks" id="ch-Automated_Tasks" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 24. Automated Tasks</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Automated_Tasks.html#s1-autotasks-cron">24.1. Cron</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Automated_Tasks.html#s2-autotasks-cron-configuring">24.1.1. Configuri
ng Cron Tasks</a></span></dt><dt><span class="section"><a href="ch-Automated_Tasks.html#s2-autotasks-cron-access">24.1.2. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="ch-Automated_Tasks.html#s2-autotasks-cron-service">24.1.3. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-at-batch.html">24.2. At and Batch</a></span></dt><dd><dl><dt><span class="section"><a href="s1-autotasks-at-batch.html#s2-autotasks-at-configuring">24.2.1. Configuring At Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">24.2.2. Configuring Batch Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-viewing.html">24.2.3. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-commandline-options.html">24.2.4. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-controlling-ac
cess.html">24.2.5. Controlling Access to At and Batch</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-service.html">24.2.6. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">24.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-autotasks-additional-resources.html#s2-autotasks-installed-docs">24.3.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id761545" class="indexterm"></a><div class="para">
+ In Linux, tasks 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="id718369" class="indexterm"></a><div class="section" title="24.1. Cron" id="s1-autotasks-cron"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-autotasks-cron">24.1. Cron</h2></div></div></div><div class="para">
+ Cron is a daemon 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 task is scheduled, it is not executed. To schedule one-time tasks, refer to <a class="xref" href="s1-autotasks-at-batch.html" title="24.2. At and Batch">Section 24.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. To determine if the package is installed, use the <code class="command">rpm -q cronie</code> command. To determine if the service is running, use the command <code class="command">/sbin/service crond status</code>.
+ </div><div class="section" title="24.1.1. Configuring Cron Tasks" id="s2-autotasks-cron-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-cron-configuring">24.1.1. Configuring Cron Tasks</h3></div></div></div><a id="id1010936" class="indexterm"></a><a id="id861848" class="indexterm"></a><div class="para">
+ The main configuration file for cron, <code class="filename">/etc/crontab</code>, contains the following lines:
+ </div><pre class="screen">
+SHELL=/bin/bash
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root HOME=/
+# run-parts
+01 * * * * root run-parts /etc/cron.hourly
+02 4 * * * root run-parts /etc/cron.daily
+22 4 * * 0 root run-parts /etc/cron.weekly
+42 4 1 * * root run-parts /etc/cron.monthly
+</pre><div class="para">
+ The first four lines are variables used to configure the environment in which the cron tasks are run. The <code class="computeroutput">SHELL</code> variable tells the system which shell environment to use (in this example the bash shell), while the <code class="computeroutput">PATH</code> variable defines the path used to execute commands. The output of the cron tasks are emailed to the username defined with the <code class="computeroutput">MAILTO</code> variable. If the <code class="computeroutput">MAILTO</code> variable is defined as an empty string (<code class="computeroutput">MAILTO=""</code>), email is not sent. 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">
+ Each line in the <code class="filename">/etc/crontab</code> file represents a task and has the following format:
+ </div><pre class="screen">
+minute hour day month dayofweek 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">dayofweek</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">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 mark (#) are comments and are not processed.
+ </div><div class="para">
+ As shown in the <code class="filename">/etc/crontab</code> file, the <code class="command">run-parts</code> script executes the scripts in the <code class="filename">/etc/cron.hourly/</code>, <code class="filename">/etc/cron.daily/</code>, <code class="filename">/etc/cron.weekly/</code>, and <code class="filename">/etc/cron.monthly/</code> directories on an hourly, daily, weekly, or monthly basis respectively. The files in these directories should be shell scripts.
+ </div><div class="para">
+ If a cron task is required to be executed on a schedule other than hourly, daily, weekly, or monthly, it can be added to the <code class="filename">/etc/cron.d/</code> directory. All files in this directory use the same syntax as <code class="filename">/etc/crontab</code>. Refer to <a class="xref" href="ch-Automated_Tasks.html#crontab-examples" title="Example 24.1. Crontab Examples">Example 24.1, “Crontab Examples”</a> for examples.
+ </div><a id="id885824" class="indexterm"></a><div class="example" title="Example 24.1. Crontab Examples" id="crontab-examples"><div class="example-contents"><pre class="screen">
+# record the memory usage of the system every monday
+# at 3:30AM in the file /tmp/meminfo
+30 3 * * mon cat /proc/meminfo >> /tmp/meminfo
+# run custom script the first day of every month at 4:10AM
+10 4 1 * * /root/scripts/backup.sh
+</pre></div><h6>Example 24.1. Crontab Examples</h6></div><br class="example-break" /><a id="id828299" class="indexterm"></a><a id="id828312" class="indexterm"></a><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>.
+ </div><div class="para">
+ The cron daemon checks 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 a crontab file is changed.
+ </div></div><div class="section" title="24.1.2. 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">24.1.2. 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 read each time a user tries to add or delete a cron task.
+ </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><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN" class="section" title="24.1.3. Starting and Stopping the Service" id="s2-autotasks-cron-service" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-cron-service">24.1.3. Starting and Stopping the Service</h3></div></div></div><div class="para">
+ 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 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a> for details on starting the cron service automatically at boot time.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-printing-useful-websites.html"><strong>Prev</strong>23.9.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-autotasks-at-batch.html"><strong>Next</strong>24.2. At and Batch</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Console_Access.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Console_Access.html
new file mode 100644
index 0000000..d89f25c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Console_Access.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 16. Console Access</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="s1-access-console-program.html" title="16.2. Disabling Console Program Access" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browse
r or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="s1-access-console-program.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 16. Console Access" id="ch-Console_Access" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 16. Console Access</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Console_Access.html#s1-access-console-ctrlaltdel">16.1. Disabling Shutdown Via <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<
span class="keycap"><strong>Del</strong></span></a></span></dt><dt><span class="section"><a href="s1-access-console-program.html">16.2. Disabling Console Program Access</a></span></dt><dt><span class="section"><a href="s1-access-console-define.html">16.3. Defining the Console</a></span></dt><dt><span class="section"><a href="s1-access-console-files.html">16.4. Making Files Accessible From the Console</a></span></dt><dt><span class="section"><a href="s1-access-console-enable.html">16.5. Enabling Console Access for Other Applications</a></span></dt><dt><span class="section"><a href="s1-access-floppy.html">16.6. The <code class="filename">floppy</code> Group</a></span></dt></dl></div><div class="para">
+ When non-root users log into a computer locally, they are given two types of special permissions:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="emphasis"><em>They can run certain commands that they would otherwise be unable to run.</em></span> By default, every user who logs in at the console is allowed to run selected commands that accomplish tasks normally restricted to the superuser only. These include <code class="command">halt</code>, <code class="command">poweroff</code>, and <code class="command">reboot</code>. In graphical user interface, these actions are accessible from the <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Shut Down...</strong></span> menu option.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>They can access certain files that they would othherwise be unable to access.</em></span> This usually means special device files located in <code class="filename">/dev</code> that are used to access CD-ROM drives, USB media, etc.
+ </div></li></ol></div><div class="para">
+ Note that in order to perform actions described in this chapter, you have to be logged in as a superuser:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="section" title="16.1. Disabling Shutdown Via Ctrl+Alt+Del" id="s1-access-console-ctrlaltdel"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-console-ctrlaltdel">16.1. Disabling Shutdown Via <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span></h2></div></div></div><div class="para">
+ By default, pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Delete</strong></span> at the console causes system to reboot immediately. To disable this behavior, open the <code class="filename">/etc/init/control-alt-delete.conf</code> configuration file in a text editor such as <code class="command">vi</code> or <code class="command">nano</code>:
+ </div><pre class="screen">~]# <code class="command">nano /etc/init/control-alt-delete.conf</code></pre><div class="para">
+ Then find a line containing the following text and add a hash mark at its very beginning like this:
+ </div><pre class="screen">#start on control-alt-delete</pre><div class="para">
+ Finally, save your changes, and exit the editor. The changes will take effect next time you reboot the computer.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Being part of the <span class="package">initscripts</span> package, <code class="filename">/etc/init/control-alt-delete.conf</code> will most likely be restored to its initial state the next time this package is upgraded. If that happens, repeat the process described in this section, or make a backup.
+ </div></div><div class="para">
+ Alternatively, you may want to allow certain non-root users the right to shutdown or reboot the system from the console using <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span> . You can restrict this privilege to certain users, by taking the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Add the <code class="command">-a</code> option to the <code class="filename">/etc/inittab</code> line shown above, so that it reads:
+ </div><pre class="screen">ca::ctrlaltdel:/sbin/shutdown -a -t3 -r now</pre><div class="para">
+ The <code class="command">-a</code> flag tells <code class="command">shutdown</code> to look for the <code class="filename">/etc/shutdown.allow</code> file.
+ </div></li><li class="listitem"><div class="para">
+ Create a file named <code class="filename">shutdown.allow</code> in <code class="filename">/etc</code>. The <code class="filename">shutdown.allow</code> file should list the usernames of any users who are allowed to shutdown the system using <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span> . The format of the <code class="filename">shutdown.allow</code> file is a list of usernames, one per line, like the following:
+ </div><pre class="screen">stephen jack sophie</pre></li></ol></div><div class="para">
+ According to this example <code class="filename">shutdown.allow</code> file, the users <code class="command">stephen</code>, <code class="command">jack</code>, and <code class="command">sophie</code> are allowed to shutdown the system from the console using <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span> . When that key combination is used, the <code class="filename">shutdown -a</code> command in <code class="filename">/etc/inittab</code> checks to see if any of the users in <code class="filename">/etc/shutdown.allow</code> (or root) are logged in on a virtual console. If one of them is, the shutdown of the system continues; if not, an error message is written to the system console instead.
+ </div><div class="para">
+ For more information on <code class="filename">shutdown.allow</code>, refer to the <code class="command">shutdown</code> man page.
+ </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="s1-access-console-program.html"><strong>Next</strong>16.2. Disabling Console Program Access</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Controlling_Access_to_Services.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Controlling_Access_to_Services.html
new file mode 100644
index 0000000..f34ed54
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Controlling_Access_to_Services.html
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-NetworkManager_Architecture.html" title="5.5. NetworkManager Architecture" /><link rel="next" href="s1-services-configuring.html" title="6.2. Configuring the Services" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-NetworkManager_Architecture.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 6. Controlling Access to Services" id="ch-Controlling_Access_to_Services" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. 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">6.1. Configu
ring the Default Runlevel</a></span></dt><dt><span class="section"><a href="s1-services-configuring.html">6.2. Configuring the Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-configuring.html#s2-services-serviceconf">6.2.1. Using the <span class="application"><strong>Service Configuration</strong></span> Utility</a></span></dt><dt><span class="section"><a href="s2-services-ntsysv.html">6.2.2. Using the <span class="application"><strong>ntsysv</strong></span> Utility</a></span></dt><dt><span class="section"><a href="s2-services-chkconfig.html">6.2.3. Using the <code class="command">chkconfig</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">6.3. Running the Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-running.html#s2-services-service">6.3.1. Using the <span class="application"><strong>service</strong></span> Utility</a></span></dt></dl></dd><dt><span class="sect
ion"><a href="s1-services-additional-resources.html">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">6.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">6.4.2. Related Books</a></span></dt></dl></dd></dl></div><a id="id985449" 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"><h2>Important</h2><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="6.4. Additional Resources">Section 6.4, “Additional Resources”</a>) for more information.
+ </div></div><div class="section" title="6.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">6.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 6.1. Runlevels in Fedora" id="table-services-runlevels"><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><h6>Table 6.1. Runlevels in Fedora</h6></div><br class="table-break" /><div class="para">
+ To check in which runlevel you are operating, type the following:
+ </div><a id="id899999" class="indexterm"></a><a id="id900017" 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="sec-NetworkManager_Architecture.html"><strong>Prev</strong>5.5. NetworkManager 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="s1-services-configuring.html"><strong>Next</strong>6.2. Configuring the Services</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Dynamic_Host_Configuration_Protocol_DHCP.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Dynamic_Host_Configuration_Protocol_DHCP.html
new file mode 100644
index 0000000..55594a6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Dynamic_Host_Configuration_Protocol_DHCP.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-samba-resources-community.html" title="9.12.3. Useful Websites" /><link rel="next" href="s1-dhcp-configuring-server.html" title="10.2. Configuring a DHCP Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html
">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-resources-community.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 10. Dynamic Host Configuration Protocol (DHCP)" id="ch-Dynamic_Host_Configuration_Protocol_DHCP" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. Dynamic Host Configuration Protocol (DHCP)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Dynamic_Host_Configuration_Pr
otocol_DHCP.html#s1-dhcp-why">10.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-server.html">10.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-configuring-server.html#config-file">10.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="lease-database.html">10.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="ch10s02s03.html">10.2.3. Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="dhcp-relay-agent.html">10.2.4. DHCP Relay Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp-configuring-client.html">10.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html">10.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html#sect-dns_Host_Configura
tion">10.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">10.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="s1-dhcp-additional-resources.html">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-additional-resources.html#s2-dhcp-installed-docs">10.6.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id650258" class="indexterm"></a><a id="id905488" 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="10.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">10.1. Why Use DHCP?</h2></div></div></div><a id="id994598" 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="s2-samba-resources-community.html"><strong>Prev</strong>9.12.3. 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-dhcp-configuring-server.html"><strong>Next</strong>10.2. Configuring a DHCP Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-FTP.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-FTP.html
new file mode 100644
index 0000000..5d49d9e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-FTP.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>Chapter 12. FTP</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-apache-additional-resources.html" title="11.9. Additional Resources" /><link rel="next" href="s1-ftp-servers.html" title="12.2. FTP Servers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enab
le iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-additional-resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ftp-servers.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 12. FTP" id="ch-FTP" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 12. FTP</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-FTP.html#s1-ftp-protocol">12.1. The File Transfer Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-FTP.html#s2-ftp-protocol-multiport">12.1.1. Multiple Ports, Multiple Modes</a></span></dt></dl
></dd><dt><span class="section"><a href="s1-ftp-servers.html">12.2. FTP Servers</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-servers.html#s2-ftp-servers-vsftpd">12.2.1. <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s2-ftp-vsftpd-conf.html">12.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s1-ftp-vsftpd-start.html">12.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-vsftpd-start.html#s2-ftp-vsftpd-start-multi">12.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-ftp-vsftpd-conf.html">12.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-vsftpd-conf.html#s2-ftp-vsftpd-conf-opt-daemon">12.5.1. Daemon Options</a>
</span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-login.html">12.5.2. Log In Options and Access Controls</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-anon.html">12.5.3. Anonymous User Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-usr.html">12.5.4. Local User Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-dir.html">12.5.5. Directory Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-file.html">12.5.6. File Transfer Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-log.html">12.5.7. Logging Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-net.html">12.5.8. Network Options</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ftp-resources.html">12.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-resources.html#s2-ftp-insta
lled-documentation">12.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-ftp-useful-websites.html">12.6.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id710880" class="indexterm"></a><a id="id729490" class="indexterm"></a><div class="para">
+ File Transfer Protocol (FTP) is one of the oldest and most commonly used protocols found on the Internet today. Its purpose is to reliably transfer files between computer hosts on a network without requiring the user to log directly into the remote host or have knowledge of how to use the remote system. It allows users to access files on remote systems using a standard set of simple commands.
+ </div><div class="para">
+ This chapter outlines the basics of the FTP protocol, as well as configuration options for the primary FTP server shipped with Fedora, <code class="command">vsftpd</code>.
+ </div><div class="section" title="12.1. The File Transfer Protocol" id="s1-ftp-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ftp-protocol">12.1. The File Transfer Protocol</h2></div></div></div><a id="id590341" class="indexterm"></a><div class="para">
+ However, because FTP is so prevalent on the Internet, it is often required to share files to the public. System administrators, therefore, should be aware of the FTP protocol's unique characteristics.
+ </div><div class="section" title="12.1.1. Multiple Ports, Multiple Modes" id="s2-ftp-protocol-multiport"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-protocol-multiport">12.1.1. Multiple Ports, Multiple Modes</h3></div></div></div><a id="id903987" class="indexterm"></a><a id="id742814" class="indexterm"></a><a id="id727987" class="indexterm"></a><a id="id575015" class="indexterm"></a><div class="para">
+ Unlike most protocols used on the Internet, FTP requires multiple network ports to work properly. When an FTP client application initiates a connection to an FTP server, it opens port 21 on the server — known as the <em class="firstterm">command port</em>. This port is used to issue all commands to the server. Any data requested from the server is returned to the client via a <em class="firstterm">data port</em>. The port number for data connections, and the way in which data connections are initialized, vary depending upon whether the client requests the data in <em class="firstterm">active</em> or <em class="firstterm">passive</em> mode.
+ </div><div class="para">
+ The following defines these modes:
+ </div><div class="variablelist"><dl><dt><span class="term">active mode</span></dt><dd><div class="para">
+ Active mode is the original method used by the FTP protocol for transferring data to the client application. When an active mode data transfer is initiated by the FTP client, the server opens a connection from port 20 on the server to the IP address and a random, unprivileged port (greater than 1024) specified by the client. This arrangement means that the client machine must be allowed to accept connections over any port above 1024. With the growth of insecure networks, such as the Internet, the use of firewalls to protect client machines is now prevalent. Because these client-side firewalls often deny incoming connections from active mode FTP servers, passive mode was devised.
+ </div></dd><dt><span class="term">passive mode</span></dt><dd><div class="para">
+ Passive mode, like active mode, is initiated by the FTP client application. When requesting data from the server, the FTP client indicates it wants to access the data in passive mode and the server provides the IP address and a random, unprivileged port (greater than 1024) on the server. The client then connects to that port on the server to download the requested information.
+ </div><div class="para">
+ While passive mode resolves issues for client-side firewall interference with data connections, it can complicate administration of the server-side firewall. You can reduce the number of open ports on a server by limiting the range of unprivileged ports on the FTP server. This also simplifies the process of configuring firewall rules for the server. Refer to <a class="xref" href="s2-ftp-vsftpd-conf-opt-net.html" title="12.5.8. Network Options">Section 12.5.8, “Network Options”</a> for more about limiting passive ports.
+ </div></dd></dl></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-additional-resources.html"><strong>Prev</strong>11.9. 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-ftp-servers.html"><strong>Next</strong>12.2. FTP Servers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Gathering_System_Information.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Gathering_System_Information.html
new file mode 100644
index 0000000..1556cfc
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Gathering_System_Information.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>Chapter 26. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="26.2. Memory Usage" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browse
r or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 26. Gathering System Information" id="ch-Gathering_System_Information" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 26. 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">26.1. System Processes</a></span></dt><dt><span class="section"><a h
ref="s1-sysinfo-memory-usage.html">26.2. Memory Usage</a></span></dt><dt><span class="section"><a href="s1-sysinfo-filesystems.html">26.3. File Systems</a></span></dt><dt><span class="section"><a href="s1-sysinfo-hardware.html">26.4. Hardware</a></span></dt><dt><span class="section"><a href="s1-sysinfo-additional-resources.html">26.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">26.5.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id581075" class="indexterm"></a><a id="id882223" 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="26.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">26.1. System Processes</h2></div></div></div><a id="id762248" class="indexterm"></a><a id="id573869" class="indexterm"></a><a id="id582194" 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="id907311" class="indexterm"></a><a id="id661570" 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 26.1. Interactive top commands">Table 26.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 26.1. Interactive top commands" id="interactive-top-command"><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><h6>Table 26.1. Interactive <code class="command">top</code> commands</h6></div><br class="table-break" /><a id="id786223" class="indexterm"></a><a id="id786236" 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>System</strong></span> > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>System Monitor</strong></span> or type <code class="command">gnome-system-monitor</code> at a shell prompt (such as an XTerm). Select the <span class="guilabel"><strong>Process Listing</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 Gnome System Monitor, 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">
+ Hide a process.
+ </div></li><li class="listitem"><div class="para">
+ View hidden processes.
+ </div></li><li class="listitem"><div class="para">
+ View memory maps.
+ </div></li><li class="listitem"><div class="para">
+ View the files opened by the selected process.
+ </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 26.1. GNOME System Monitor" id="fig-sysinfo-processes"><div class="figure-contents"><div class="mediaobject"><img src="images/gnome-system-monitor-processes.png" width="444" alt="GNOME System Monitor" /><div class="longdesc"><div class="para">
+ Process Listing of GNOME System Monitor
+ </div></div></div></div><h6>Figure 26.1. <span class="application">GNOME System Monitor</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>26.2. Memory Usage</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-General_Parameters_and_Modules.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-General_Parameters_and_Modules.html
new file mode 100644
index 0000000..999f423
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-General_Parameters_and_Modules.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>Chapter 30. General Parameters and 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-kernel-configuration.html" title="Part V. Kernel and Driver Configuration" /><link rel="prev" href="s2-kernel-boot-loader-pseries.html" title="29.6.3. Configuring the YABOOT Boot Loader" /><link rel="next" href="s1-kernel-modules-persistant.html" title="30.2. Persistent Module Loading" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../..
/toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kernel-modules-persistant.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 30. General Parameters and Modules" id="ch-General_Parameters_and_Modules" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 30. General Parameters and Modules</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-General_Parameters_and_Modules.html#s1-kernel-modul
e-utils">30.1. Kernel Module Utilities</a></span></dt><dt><span class="section"><a href="s1-kernel-modules-persistant.html">30.2. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="s1-modules-parameters-specifying.html">30.3. Specifying Module Parameters</a></span></dt><dt><span class="section"><a href="s1-modules-scsi.html">30.4. Storage parameters</a></span></dt><dt><span class="section"><a href="s1-modules-ethernet.html">30.5. Ethernet Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="s1-modules-ethernet.html#s2-modules-multiple-eth">30.5.1. Using Multiple Ethernet Cards</a></span></dt><dt><span class="section"><a href="s2-modules-bonding.html">30.5.2. The Channel Bonding Module</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">30.6. Additional Resources</a></span></dt></dl></div><a id="id725310" class="indexterm"></a><a id="id622512" class="indexterm"></a><a id="id871622" c
lass="indexterm"></a><a id="id739723" class="indexterm"></a><div class="para">
+ This chapter is provided to illustrate <span class="emphasis"><em>some</em></span> of the possible parameters available for common hardware device <em class="firstterm">drivers</em><sup>[<a id="id874765" href="#ftn.id874765" class="footnote">5</a>]</sup>, which under Fedora are called <em class="firstterm">kernel module</em>s . In most cases, the default parameters do work. However, there may be times when extra module parameters are necessary for a device to function properly or to override the module's default parameters for the device.
+ </div><div class="para">
+ During installation, Fedora uses a limited subset of device drivers to create a stable installation environment. Although the installation program supports installation on many different types of hardware, some drivers (including those for SCSI adapters and network adapters) are not included in the installation kernel. Rather, they must be loaded as modules by the user at boot time.
+ </div><div class="para">
+ Once installation is completed, support exists for a large number of devices through kernel modules.
+ </div><div class="section" title="30.1. Kernel Module Utilities" id="s1-kernel-module-utils"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-module-utils">30.1. Kernel Module Utilities</h2></div></div></div><a id="id647065" class="indexterm"></a><div class="para">
+ A group of commands for managing kernel modules is available if the <code class="filename">module-init-tools</code>
+ <a id="id989736" class="indexterm"></a>
+ <a id="id994634" class="indexterm"></a>
+ package is installed. Use these commands to determine if a module has been loaded successfully or when trying different modules for a piece of new hardware.
+ </div><a id="id941103" class="indexterm"></a><a id="id858288" class="indexterm"></a><div class="para">
+ The command <code class="command">/sbin/lsmod</code> displays a list of currently loaded modules. For example:
+ </div><pre class="screen">
+~]$ <code class="command">/sbin/lsmod</code>
+Module Size Used by
+autofs4 25618 3
+sunrpc 231823 1
+bonding 115826 0
+ip6t_REJECT 4641 2
+nf_conntrack_ipv6 19623 2
+ip6table_filter 2895 1
+ip6_tables 19232 1 ip6table_filter
+ipv6 322766 61 bonding,ip6t_REJECT,nf_conntrack_ipv6
+dm_mirror 13723 0
+dm_region_hash 11920 1 dm_mirror
+dm_log 9944 2 dm_mirror,dm_region_hash
+uinput 8126 0
+sg 30478 0
+sr_mod 16066 0
+snd_ens1370 23085 4
+gameport 10783 1 snd_ens1370
+snd_rawmidi 22955 1 snd_ens1370
+cdrom 39833 1 sr_mod
+snd_seq 56461 0
+snd_seq_device 6634 2 snd_rawmidi,snd_seq
+snd_pcm 83399 1 snd_ens1370
+snd_timer 22304 4 snd_seq,snd_pcm
+snd 70077 12 snd_ens1370,snd_rawmidi,snd_seq,snd_seq_device,snd_pcm,snd_timer
+virtio_net 15937 0
+i2c_piix4 12707 0
+soundcore 7892 1 snd
+joydev 10514 0
+snd_page_alloc 8604 2 snd_ens1370,snd_pcm
+i2c_core 31338 1 i2c_piix4
+virtio_balloon 3599 0
+ext4 362885 2
+mbcache 7510 1 ext4
+jbd2 98427 1 ext4
+virtio_blk 5159 3
+ata_generic 3619 0
+pata_acpi 3675 0
+virtio_pci 6741 0
+virtio_ring 6026 1 virtio_pci
+virtio 4864 4 virtio_net,virtio_balloon,virtio_blk,virtio_pci
+ata_piix 22532 0
+dm_mod 73839 8 dm_mirror,dm_log</pre><div class="para">
+ The first column lists the names of modules; the second column lists the sizes of the modules, and the third column lists the use counts. The output from the <code class="command">/sbin/lsmod</code> command is less verbose and easier to read than the output of <code class="filename">cat /proc/modules</code>.
+ </div><a id="id793327" class="indexterm"></a><a id="id793341" class="indexterm"></a><div class="para">
+ To load a kernel module, use the <code class="command">/sbin/modprobe</code> command followed by the kernel module name. By default, <code class="command">modprobe</code> attempts to load the module from the <code class="filename">/lib/modules/<em class="replaceable"><code><kernel-version></code></em>/kernel/drivers/</code> subdirectories. There is a subdirectory for each type of module, such as the <code class="filename">net/</code> subdirectory for network interface drivers. Some kernel modules have module dependencies, meaning that other modules must be loaded first for it to load. The <code class="command">/sbin/modprobe</code> command checks for these dependencies and loads the module dependencies before loading the specified module.
+ </div><div class="para">
+ For example, the command:
+ </div><pre class="screen">~]# <code class="command">/sbin/modprobe e100</code>
+</pre><div class="para">
+ …first loads all module dependencies of the <code class="systemitem">e100</code> module before loading the <code class="systemitem">e100</code> module itself.
+ </div><div class="para">
+ To print to the screen all commands as <code class="command">/sbin/modprobe</code> executes them, use the <code class="option">-v</code> option. For example:
+ </div><pre class="screen">~]# <code class="command">/sbin/modprobe -v e100</code>
+</pre><div class="para">
+ Output similar to the following is displayed:
+ </div><pre class="screen">
+/sbin/insmod /lib/modules/2.6.9-5.EL/kernel/drivers/net/e100.ko
+Using /lib/modules/2.6.9-5.EL/kernel/drivers/net/e100.ko
+Symbol version prefix 'smp_'
+</pre><a id="id1004566" class="indexterm"></a><div class="para">
+ The <code class="command">/sbin/insmod</code> command can also be used to load kernel modules; however, it does not resolve dependencies. You should thus always use <code class="command">/sbin/modprobe</code> instead of the <code class="command">insmod</code> command to load kernel modules.
+ </div><a id="id1004597" class="indexterm"></a><a id="id1004610" class="indexterm"></a><div class="para">
+ To unload kernel modules, use the <code class="command">/sbin/rmmod</code> command followed by the module name. The <code class="command">rmmod</code> utility only unloads modules that are not in use and that are not a dependency of other modules in use.
+ </div><div class="para">
+ For example, the command:
+ </div><pre class="screen">~]# <code class="command">/sbin/rmmod e100</code>
+</pre><div class="para">
+ …unloads the <code class="systemitem">e100</code> kernel module.
+ </div><div class="para">
+ Another useful kernel module utility is <code class="command">modinfo</code>. Use the command <code class="command">/sbin/modinfo</code> to display information about a kernel module. The general syntax is:
+ </div><pre class="screen">~]# <code class="command">/sbin/modinfo <em class="replaceable"><code>[<span class="optional">options</span>] </code></em> <em class="replaceable"><code><kernel_module_name></code></em> </code>
+</pre><div class="para">
+ Options include <code class="option">-d</code>, which displays a brief description of the module, and <code class="option">-p</code>, which lists the parameters the module supports. The <code class="command">modinfo</code> command is useful for listing information such as version, dependencies, paramater options, and aliases of modules.For a complete list of options, refer to the <code class="command">modinfo</code> man page.
+ </div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id874765" href="#id874765" class="para">5</a>] </sup>
+ A <em class="firstterm">driver</em> is software that enables Linux to use a particular hardware device. Without a driver, the kernel cannot communicate with attached devices.
+ </p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kernel-boot-loader-pseries.html"><strong>Prev</strong>29.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-kernel-modules-persistant.html"><strong>Next</strong>30.2. Persistent Module Loading</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.html
new file mode 100644
index 0000000..aab4c76
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></di
v><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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.html"><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><span class="term"> <span class="application"><strong>PackageKit</strong></span> home page — <a href="http://www.packagekit.org/index.html">ht
tp://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><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><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_Draft_Documentation/0.1/html/Deployment_Guide/ch-Keyboard_Configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Keyboard_Configuration.html
new file mode 100644
index 0000000..a91cbab
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Keyboard_Configuration.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>Chapter 20. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="19.2.2. Network Time Protocol Setup" /><link rel="next" href="s1-keyboard-indicator.html" title="20.2. Adding the Keyboard Layout Indicator" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="
toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-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 20. Keyboard Configuration" id="ch-Keyboard_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. Keyboard Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Keyboard_
Configuration.html#s1-keyboard-layout">20.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="s1-keyboard-indicator.html">20.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="s1-keyboard-break.html">20.3. Setting Up a Typing Break</a></span></dt></dl></div><a id="id905476" 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="20.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">20.1. Changing the Keyboard Layout</h2></div></div></div><a id="id638859" class="indexterm"></a><a id="id899754" class="indexterm"></a><a id="id788791" 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 20.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 20.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 20.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 20.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 20.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 20.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 20.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 20.4. Testing the layout</h6></div><br class="figure-break" /><div class="note"><h2>Suggestion: Disable Separate Layout for Each Window</h2><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 20.3. Selecting the default layout">Figure 20.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><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>19.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>20.2. Adding the Keyboard Layout Indicator</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Lightweight_Directory_Access_Protocol_LDAP.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Lightweight_Directory_Access_Protocol_LDAP.html
new file mode 100644
index 0000000..7716f60
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Lightweight_Directory_Access_Protocol_LDAP.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>Chapter 14. Lightweight Directory Access Protocol (LDAP)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-email-related-books.html" title="13.7.3. Related Books" /><link rel="next" href="s1-ldap-terminology.html" title="14.2. LDAP Terminology" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, t
o view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="s1-ldap-terminology.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" id="ch-Lightweight_Directory_Access_Protocol_LDAP" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 14. Lightweight Directory Access Protocol (LDAP)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Lightweight_Directory_Access_Protocol_LDAP.html#s1-ldap-ad
v">14.1. Why Use LDAP?</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Lightweight_Directory_Access_Protocol_LDAP.html#s1-ldap-v3">14.1.1. OpenLDAP Features</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-terminology.html">14.2. LDAP Terminology</a></span></dt><dt><span class="section"><a href="s1-ldap-daemonsutils.html">14.3. OpenLDAP Daemons and Utilities</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ldap-daemonsutils.html#s2-ldap-pam-nss">14.3.1. NSS, PAM, and LDAP</a></span></dt><dt><span class="section"><a href="s2-ldap-other-apps.html">14.3.2. PHP4, LDAP, and the Apache HTTP Server</a></span></dt><dt><span class="section"><a href="s2-ldap-applications.html">14.3.3. LDAP Client Applications</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-files.html">14.4. OpenLDAP Configuration Files</a></span></dt><dt><span class="section"><a href="s1-ldap-files-schemas.html">14.5. The <code class="filename">/etc/openl
dap/schema/</code> Directory</a></span></dt><dt><span class="section"><a href="s1-ldap-quickstart.html">14.6. OpenLDAP Setup Overview</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ldap-quickstart.html#s2-ldap-files-slapd-conf">14.6.1. Editing <code class="filename">/etc/openldap/slapd.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-pam.html">14.7. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ldap-pam.html#s2-ldap-pamd">14.7.1. PAM and LDAP</a></span></dt><dt><span class="section"><a href="s2-ldap-migrate.html">14.7.2. Migrating Old Authentication Information to LDAP Format</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-migrate.html">14.8. Migrating Directories from Earlier Releases</a></span></dt><dt><span class="section"><a href="s1-ldap-additional-resources.html">14.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section">
<a href="s1-ldap-additional-resources.html#s2-ldap-installed-docs">14.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-ldap-additional-resources-web.html">14.9.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-ldap-related-books.html">14.9.3. Related Books</a></span></dt></dl></dd></dl></div><a id="id790176" class="indexterm"></a><a id="id877647" class="indexterm"></a><a id="id621808" class="indexterm"></a><a id="id812216" class="indexterm"></a><a id="id600867" class="indexterm"></a><a id="id621436" class="indexterm"></a><a id="id954664" class="indexterm"></a><div class="para">
+ The <em class="firstterm">Lightweight Directory Access Protocol</em> (<em class="firstterm">LDAP</em>) is a set of open protocols used to access centrally stored information over a network. It is based on the <em class="firstterm">X.500</em> standard for directory sharing, but is less complex and resource-intensive. For this reason, LDAP is sometimes referred to as "<em class="firstterm">X.500 Lite</em>." The X.500 standard is a directory that contains hierarchical and categorized information, which could include information such as names, addresses, and phone numbers.
+ </div><div class="para">
+ Like X.500, LDAP organizes information in a hierarchal manner using directories. These directories can store a variety of information and can even be used in a manner similar to the Network Information Service (NIS), enabling anyone to access their account from any machine on the LDAP enabled network.
+ </div><div class="para">
+ In many cases, LDAP is used as a virtual phone directory, allowing users to easily access contact information for other users. But LDAP is more flexible than a traditional phone directory, as it is capable of referring a querent to other LDAP servers throughout the world, providing an ad-hoc global repository of information. Currently, however, LDAP is more commonly used within individual organizations, like universities, government departments, and private companies.
+ </div><div class="para">
+ LDAP is a client/server system. The server can use a variety of databases to store a directory, each optimized for quick and copious read operations. When an LDAP client application connects to an LDAP server, it can either query a directory or attempt to modify it. In the event of a query, the server either answers the query locally, or it can refer the querent to an LDAP server which does have the answer. If the client application is attempting to modify information within an LDAP directory, the server verifies that the user has permission to make the change and then adds or updates the information.
+ </div><div class="para">
+ This chapter refers to the configuration and use of OpenLDAP 2.0, an open source implementation of the LDAPv2 and LDAPv3 protocols.
+ </div><div class="section" title="14.1. Why Use LDAP?" id="s1-ldap-adv"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-adv">14.1. Why Use LDAP?</h2></div></div></div><a id="id709172" class="indexterm"></a><div class="para">
+ The main benefit of using LDAP is that information for an entire organization can be consolidated into a central repository. For example, rather than managing user lists for each group within an organization, LDAP can be used as a central directory accessible from anywhere on the network. And because LDAP supports Secure Sockets Layer (SSL) and Transport Layer Security (TLS), sensitive data can be protected from prying eyes.
+ </div><div class="para">
+ LDAP also supports a number of back-end databases in which to store directories. This allows administrators the flexibility to deploy the database best suited for the type of information the server is to disseminate. Because LDAP also has a well-defined client Application Programming Interface (API), the number of LDAP-enabled applications are numerous and increasing in quantity and quality.
+ </div><div class="section" title="14.1.1. OpenLDAP Features" id="s1-ldap-v3"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-ldap-v3">14.1.1. OpenLDAP Features</h3></div></div></div><a id="id850914" class="indexterm"></a><div class="para">
+ OpenLDAP includes a number of important features.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>LDAPv3 Support</em></span> — OpenLDAP supports Simple Authentication and Security Layer (SASL), Transport Layer Security (TLS), and Secure Sockets Layer (SSL), among other improvements. Many of the changes in the protocol since LDAPv2 are designed to make LDAP more secure.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>IPv6 Support</em></span> — OpenLDAP supports the next generation Internet Protocol version 6.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>LDAP Over IPC</em></span> — OpenLDAP can communicate within a system using interprocess communication (IPC). This enhances security by eliminating the need to communicate over a network.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Updated C API</em></span> — Improves the way programmers can connect to and use LDAP directory servers.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>LDIFv1 Support</em></span> — Provides full compliance with the LDAP Data Interchange Format (LDIF) version 1.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Enhanced Stand-Alone LDAP Server</em></span> — Includes an updated access control system, thread pooling, better tools, and much more.
+ </div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-related-books.html"><strong>Prev</strong>13.7.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-ldap-terminology.html"><strong>Next</strong>14.2. LDAP Terminology</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Log_Files.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Log_Files.html
new file mode 100644
index 0000000..98d4d01
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Log_Files.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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 25. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="24.3. Additional Resources" /><link rel="next" href="s1-logfiles-viewing.html" title="25.2. Viewing Log Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enabl
e iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="next"><a accesskey="n" href="s1-logfiles-viewing.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 25. Log Files" id="ch-Log_Files" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 25. Log Files</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Log_Files.html#s1-logfiles-locating">25.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="s1-logfiles-viewing.html">25.2. Viewing Log Files</a></span></dt><dt><span cl
ass="section"><a href="s1-logfiles-adding.html">25.3. Adding a Log File</a></span></dt><dt><span class="section"><a href="s1-logfiles-examining.html">25.4. Monitoring Log Files</a></span></dt></dl></div><a id="id885234" class="indexterm"></a><a id="id644061" 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="id715279" class="indexterm"></a><a id="id638368" class="indexterm"></a><div class="para">
+ Some log files are controlled by a daemon called <code class="command">rsyslog</code>. A list of log messages maintained by <code class="command">rsyslog</code> can be found in the <code class="filename">/etc/rsyslog.conf</code> configuration file.
+ </div><div class="section" title="25.1. Locating Log Files" id="s1-logfiles-locating"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-locating">25.1. Locating Log Files</h2></div></div></div><a id="id636257" 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="id569340" class="indexterm"></a><a id="id655041" class="indexterm"></a><div class="para">
+ You may notice multiple files in the log file directory with numbers after them. These are created when the log files are rotated. 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. By default, it is configured to rotate every week and keep four weeks worth of previous log files.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-autotasks-additional-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="s1-logfiles-viewing.html"><strong>Next</strong>25.2. Viewing Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Manually_Upgrading_the_Kernel.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Manually_Upgrading_the_Kernel.html
new file mode 100644
index 0000000..ab75c8c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Manually_Upgrading_the_Kernel.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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 29. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-kernel-configuration.html" title="Part V. Kernel and Driver Configuration" /><link rel="prev" href="pt-kernel-configuration.html" title="Part V. Kernel and Driver Configuration" /><link rel="next" href="s1-kernel-preparing.html" title="29.2. Preparing to Upgrade" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an i
frame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="s1-kernel-preparing.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 29. Manually Upgrading the Kernel" id="ch-Manually_Upgrading_the_Kernel" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 29. 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">29.1. Overview of Kernel Packages</a>
</span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">29.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">29.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">29.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">29.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">29.6. Verifying the Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">29.6.1. Configuring the GRUB Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-iseries.html">29.6.2. Configuring the <span class="trademark">OS/400</span>® Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-pseries.html">29.6.3. Confi
guring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></div><a id="id825153" 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
+ <a id="id860262" class="indexterm"></a>
+ <a id="id576580" class="indexterm"></a>
+ <a id="id718288" class="indexterm"></a>
+ 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><div class="warning"><h2>Use Yum to Install Kernels Whenever Possible</h2><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
+ <a id="id721252" class="indexterm"></a>
+ <a id="id601085" class="indexterm"></a>
+ 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 class="para">
+ For more information on installing kernel packages
+ <a id="id677622" class="indexterm"></a>
+ 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="29.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">29.1. Overview of Kernel Packages</h2></div></div></div><div class="para">
+ Fedora contains the following kernel packages:
+ <a id="id810665" class="indexterm"></a>
+
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">kernel</span> —
+ <a id="id792597" class="indexterm"></a>
+ <a id="id792613" class="indexterm"></a>
+ Contains the kernel for single, multicore and multiprocessor systems.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-devel</span> —
+ <a id="id792640" class="indexterm"></a>
+ <a id="id792656" class="indexterm"></a>
+ 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-doc</span> —
+ <a id="id792520" class="indexterm"></a>
+ <a id="id792536" class="indexterm"></a>
+ 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> —
+ <a id="id912862" class="indexterm"></a>
+ <a id="id912878" class="indexterm"></a>
+ 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> —
+ <a id="id912908" class="indexterm"></a>
+ <a id="id912924" class="indexterm"></a>
+ 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> — <span class="package">kernel-firmware</span> —
+ <a id="id912956" class="indexterm"></a>
+ <a id="id912972" class="indexterm"></a>
+ Technically a documentation instead of kernel package, <span class="package">perf</span> contains supporting documentation for the perf tool shipped in each kernel image subpackage.
+ </div></li></ul></div><div class="note"><h2>Note: kernel-source package availability</h2><div class="para">
+ The <span class="package">kernel-source</span> package has been removed and replaced with a source RPM package that can only be retrieved from Red Hat Network. This SRPM package must then be built locally using the <code class="command">rpmbuild</code> command. For more information on obtaining and installing the kernel source package, refer to the latest updated Fedora 13 Release Notes (and their updates) at <a href="http://www.redhat.com/docs/manuals/enterprise/">http://www.redhat.com/docs/manuals/enterprise/</a>
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-kernel-configuration.html"><strong>Prev</strong>Part V. Kernel 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="s1-kernel-preparing.html"><strong>Next</strong>29.2. Preparing to Upgrade</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Network_Configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Network_Configuration.html
new file mode 100644
index 0000000..6424dca
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Network_Configuration.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>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><dd><dl><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network">5.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="sec-Configuring_New_and_Editing_Existing_Connections.html">5.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Automatically.html">5.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="sec-User_and_System_Connections.html">5.2.4. User and System Connections</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Establishing_Connections.html">5.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Establishing_Connections.html#sec-Establishing_a_Wired_Ethernet_Connection">5.3.1. Es
tablishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Wireless_Connection.html">5.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Mobile_Broadband_Connection.html">5.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_VPN_Connection.html">5.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_DSL_Connection.html">5.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_Routes.html">5.3.6. Establishing Routes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html">5.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html#sec-Configuring_802.1x_Security">5.4.1. Configuring 802.1x
Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_Wireless_Security.html">5.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_PPP_Point-to-Point_Settings.html">5.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv4_Settings.html">5.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv6_Settings.html">5.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="sec-NetworkManager_Architecture.html">5.5. NetworkManager Architecture</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 13, <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 13 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 6. Controlling Access to Services">Chapter 6, <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_Draft_Documentation/0.1/html/Deployment_Guide/ch-Network_Interfaces.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Network_Interfaces.html
new file mode 100644
index 0000000..328403d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Network_Interfaces.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>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 cl
ass="section"><a href="s1-networkscripts-interfaces.html">4.2. Interface Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">4.2.1. Ethernet Interfaces</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-chan.html">4.2.2. Channel Bonding Interfaces</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-alias.html">4.2.3. Alias and Clone Files</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-ppp0.html">4.2.4. Dialup Interfaces</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-other.html">4.2.5. Other Interfaces</a></span></dt></dl></dd><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 c
lass="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><dd><dl><dt><span class="section"><a href="s1-networkscripts-resources.html#s2-networkscripts-docs-inst">4.6.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id562235" class="indexterm"></a><a id="id877597" 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="id912837" 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><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><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><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><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"><h2>Warning</h2><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><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_Draft_Documentation/0.1/html/Deployment_Guide/ch-OProfile.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-OProfile.html
new file mode 100644
index 0000000..7fadf3e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-OProfile.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>Chapter 27. OProfile</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="26.5. Additional Resources" /><link rel="next" href="s1-oprofile-configuring.html" title="27.2. Configuring OProfile" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="next"><a accesskey="n" href="s1-oprofile-configuring.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 27. OProfile" id="ch-OProfile" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 27. OProfile</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-OProfile.html#s1-oprofile-overview-tools">27.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="s1-oprofile-configuring.html">27.2. Configuring OProfile</a></span
></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">27.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">27.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-starting-separate.html">27.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-starting.html">27.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">27.4. Saving Data</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">27.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">27.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">27.5.2. Using <code c
lass="command">opreport</code> on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">27.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">27.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">27.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">27.7. Example Usage</a></span></dt><dt><span class="section"><a href="s1-oprofile-gui.html">27.8. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-additional-resources.html">27.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-additional-resources.html#s1-oprofile-installed-docs">27.9.1. Installed Docs</a></span></dt><dt><span class="section
"><a href="s2-oprofile-useful-websites.html">27.9.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id867334" class="indexterm"></a><a id="id555544" class="indexterm"></a><div class="para">
+ OProfile is a low overhead, system-wide performance monitoring tool. It uses the performance monitoring hardware on the processor to retrieve information about the kernel and executables on the system, such as when memory is referenced, the number of L2 cache requests, and the number of hardware interrupts received. On a Fedora system, the <code class="filename">oprofile</code> RPM package must be installed to use this tool.
+ </div><div class="para">
+ Many processors include dedicated performance monitoring hardware. This hardware makes it possible to detect when certain events happen (such as the requested data not being in cache). The hardware normally takes the form of one or more <em class="firstterm">counters</em> that are incremented each time an event takes place. When the counter value, essentially rolls over, an interrupt is generated, making it possible to control the amount of detail (and therefore, overhead) produced by performance monitoring.
+ </div><div class="para">
+ OProfile uses this hardware (or a timer-based substitute in cases where performance monitoring hardware is not present) to collect <em class="firstterm">samples</em> of performance-related data each time a counter generates an interrupt. These samples are periodically written out to disk; later, the data contained in these samples can then be used to generate reports on system-level and application-level performance.
+ </div><div class="para">
+ OProfile is a useful tool, but be aware of some limitations when using it:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Use of shared libraries</em></span> — Samples for code in shared libraries are not attributed to the particular application unless the <code class="option">--separate=library</code> option is used.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Performance monitoring samples are inexact</em></span> — When a performance monitoring register triggers a sample, the interrupt handling is not precise like a divide by zero exception. Due to the out-of-order execution of instructions by the processor, the sample may be recorded on a nearby instruction.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em> <code class="command">opreport</code> does not associate samples for inline functions' properly</em></span> — <code class="command">opreport</code> uses a simple address range mechanism to determine which function an address is in. Inline function samples are not attributed to the inline function but rather to the function the inline function was inserted into.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>OProfile accumulates data from multiple runs</em></span> — OProfile is a system-wide profiler and expects processes to start up and shut down multiple times. Thus, samples from multiple runs accumulate. Use the command <code class="command">opcontrol --reset</code> to clear out the samples from previous runs.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Non-CPU-limited performance problems</em></span> — OProfile is oriented to finding problems with CPU-limited processes. OProfile does not identify processes that are asleep because they are waiting on locks or for some other event to occur (for example an I/O device to finish an operation).
+ </div></li></ul></div><div class="section" title="27.1. Overview of Tools" id="s1-oprofile-overview-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-overview-tools">27.1. Overview of Tools</h2></div></div></div><a id="id862086" class="indexterm"></a><div class="para">
+ <a class="xref" href="ch-OProfile.html#tb-oprofile-tools" title="Table 27.1. OProfile Commands">Table 27.1, “OProfile Commands”</a> provides a brief overview of the tools provided with the <code class="filename">oprofile</code> package.
+ </div><div class="table" title="Table 27.1. OProfile Commands" id="tb-oprofile-tools"><div class="table-contents"><table summary="OProfile Commands" border="1"><colgroup><col width="29%" /><col width="71%" /></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">ophelp</code>
+ </td><td>
+ <div class="para">
+ Displays available events for the system's processor along with a brief description of each.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="command">opimport</code>
+ </td><td>
+ <div class="para">
+ Converts sample database files from a foreign binary format to the native format for the system. Only use this option when analyzing a sample database from a different architecture.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="command">opannotate</code>
+ </td><td>
+ Creates annotated source for an executable if the application was compiled with debugging symbols. Refer to <a class="xref" href="s2-oprofile-reading-opannotate.html" title="27.5.4. Using opannotate">Section 27.5.4, “Using <code class="command">opannotate</code> ”</a> for details.
+ </td></tr><tr><td>
+ <code class="command">opcontrol</code>
+ </td><td>
+ <div class="para">
+ Configures what data is collected. Refer to <a class="xref" href="s1-oprofile-configuring.html" title="27.2. Configuring OProfile">Section 27.2, “Configuring OProfile”</a> for details.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="command">opreport</code>
+ </td><td>
+ <div class="para">
+ Retrieves profile data. Refer to <a class="xref" href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport" title="27.5.1. Using opreport">Section 27.5.1, “Using <code class="command">opreport</code> ”</a> for details.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="command">oprofiled</code>
+ </td><td>
+ <div class="para">
+ Runs as a daemon to periodically write sample data to disk.
+ </div>
+
+ </td></tr></tbody></table></div><h6>Table 27.1. OProfile Commands</h6></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-additional-resources.html"><strong>Prev</strong>26.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="s1-oprofile-configuring.html"><strong>Next</strong>27.2. Configuring OProfile</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-OpenSSH.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-OpenSSH.html
new file mode 100644
index 0000000..6ddac51
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-OpenSSH.html
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="7.7.3. Related Books" /><link rel="next" href="s1-ssh-configuration.html" title="8.2. An OpenSSH Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser o
r enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="next"><a accesskey="n" href="s1-ssh-configuration.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 8. OpenSSH" id="ch-OpenSSH" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. OpenSSH</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">8.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">8.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a
href="ch-OpenSSH.html#s2-ssh-features">8.1.2. Main Features</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">8.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">8.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">8.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">8.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">8.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">8.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">8.2.4. Using a Key-Based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-
clients.html">8.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">8.3.1. Using the <code class="command">ssh</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">8.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">8.3.3. Using the <code class="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-beyondshell.html">8.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">8.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">8.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">8.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s
1-openssh-additional-resources.html#s2-openssh-installed-docs">8.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-openssh-useful-websites.html">8.5.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id910008" 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="8.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">8.1. The SSH Protocol</h2></div></div></div><div class="section" title="8.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">8.1.1. Why Use SSH?</h3></div></div></div><a id="id751713" 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><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><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="8.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">8.1.2. Main Features</h3></div></div></div><a id="id933114" class="indexterm"></a><a id="id933126" class="indexterm"></a><div class="para">
+ The SSH protocol provides the following safeguards:
+ </div><div class="variablelist"><dl><dt><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><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><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><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><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><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><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="8.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">8.1.3. Protocol Versions</h3></div></div></div><a id="id592310" class="indexterm"></a><a id="id644093" 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"><h2>Important: Avoid Using SSH Version 1</h2><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 class="section" title="8.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">8.1.4. Event Sequence of an SSH Connection</h3></div></div></div><a id="id644134" 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="8.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">8.1.4.1. Transport Layer</h4></div></div></div><a id="id644197" 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"><h2>Caution</h2><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 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="8.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">8.1.4.2. Authentication</h4></div></div></div><a id="id764752" 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="8.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">8.1.4.3. Channels</h4></div></div></div><a id="id764787" 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="id764809" href="#ftn.id764809" class="footnote">4</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.id764809" href="#id764809" class="para">4</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="s2-bind-related-books.html"><strong>Prev</strong>7.7.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-ssh-configuration.html"><strong>Next</strong>8.2. An OpenSSH Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-PackageKit.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-PackageKit.html
new file mode 100644
index 0000000..933aaab
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-PackageKit.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="next"><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_Soft
ware.html">2.2. Using Add/Remove Software</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html#sec-Refreshing_Software_Sources_Yum_Repositories">2.2.1. Refreshing Software Sources (Yum Repositories)</a></span></dt><dt><span class="section"><a href="sec-Finding_Packages_with_Filters.html">2.2.2. Finding Packages with Filters</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Packages_and_Dependencies.html">2.2.3. Installing and Removing Packages (and Dependencies)</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Package_Groups.html">2.2.4. Installing and Removing Package Groups</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Transaction_Log.html">2.2.5. Viewing the Transaction Log</a></span></dt></dl></dd><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="id870753" 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="id581942" class="indexterm"></a>
+ <a id="id569016" class="indexterm"></a>
+ <a id="id754542" class="indexterm"></a>
+ <a id="id884388" class="indexterm"></a>
+ <a id="id585791" class="indexterm"></a>
+ <a id="id872798" class="indexterm"></a>
+ <a id="id577137" class="indexterm"></a>
+ <a id="id756771" class="indexterm"></a>
+ <a id="id894210" class="indexterm"></a>
+ <a id="id954769" 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="id609845" class="indexterm"></a>
+ <a id="id609861" 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="id885586" class="indexterm"></a>
+ <a id="id636444" 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="id636468" class="indexterm"></a>
+ <a id="id636484" class="indexterm"></a>
+ <a id="id636496" class="indexterm"></a>
+ utilizes the fine-grained user authentication
+ <a id="id636504" 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="id759701" 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_Draft_Documentation/0.1/html/Deployment_Guide/ch-Printer_Configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Printer_Configuration.html
new file mode 100644
index 0000000..c3b1819
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Printer_Configuration.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>Chapter 23. Printer 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="22.7. Additional Resources" /><link rel="next" href="s1-printing-ipp-printer.html" title="23.2. Adding an IPP Printer" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrad
e your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="next"><a accesskey="n" href="s1-printing-ipp-printer.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 23. Printer Configuration" id="ch-Printer_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 23. Printer Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Printer_Configuration.html#s1-printing-local-printer">23.1. Adding a Local Printer</a></span></dt><dt><span class="section"
><a href="s1-printing-ipp-printer.html">23.2. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">23.3. Adding a Samba (SMB) Printer</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">23.4. Adding a JetDirect Printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">23.5. Selecting the Printer Model and Finishing</a></span></dt><dd><dl><dt><span class="section"><a href="s1-printing-select-model.html#s2-printing-confirm">23.5.1. Confirming Printer Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-printing-test-page.html">23.6. Printing a Test Page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">23.7. Modifying Existing Printers</a></span></dt><dd><dl><dt><span class="section"><a href="s1-printing-edit.html#id969412">23.7.1. The <span class="guilabel"><strong>Settings</strong></span> Tab</a></span></dt><dt><span
class="section"><a href="ch23s07s02.html">23.7.2. The <span class="guilabel"><strong>Policies</strong></span> Tab</a></span></dt><dt><span class="section"><a href="ch23s07s03.html">23.7.3. The <span class="guilabel"><strong>Access Control</strong></span> Tab</a></span></dt><dt><span class="section"><a href="ch23s07s04.html">23.7.4. The <span class="guilabel"><strong>Printer</strong></span> and <span class="guilabel"><strong>Job Options</strong></span>Tab</a></span></dt></dl></dd><dt><span class="section"><a href="s1-printing-managing.html">23.8. Managing Print Jobs</a></span></dt><dt><span class="section"><a href="s1-printing-additional-resources.html">23.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-printing-additional-resources.html#s2-printing-installed-docs">23.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-printing-useful-websites.html">23.9.2. Useful Websites</a></span></dt></dl></dd></dl></div>
<a id="id988928" class="indexterm"></a><a id="id874890" class="indexterm"></a><a id="id652776" class="indexterm"></a><a id="id588444" class="indexterm"></a><a id="id752692" class="indexterm"></a><div class="para">
+ <span class="application"><strong>Printer Configuration Tool</strong></span> allows users to configure a printer. This tool helps maintain the printer configuration file, print spool directories, print filters, and printer classes.
+ </div><a id="id912833" class="indexterm"></a><a id="id646504" class="indexterm"></a><div class="para">
+ Fedora 13 uses the Common Unix Printing System (<acronym class="acronym">CUPS</acronym>). If a system was upgraded from a previous Fedora version that used CUPS, the upgrade process preserves the configured queues.
+ </div><div class="para">
+ Using <span class="application"><strong>Printer Configuration Tool</strong></span> requires root privileges. To start the application, select System (on the panel) > <span class="guimenu"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>Printing</strong></span>, or type the command <code class="command">system-config-printer</code> at a shell prompt.
+ </div><div class="figure" title="Figure 23.1. Printer Configuration Tool" id="fig-printconf-main"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-main.png" alt="Printer Configuration Tool" /><div class="longdesc"><div class="para">
+ Main window
+ </div></div></div></div><h6>Figure 23.1. <span class="application">Printer Configuration Tool</span> </h6></div><br class="figure-break" /><div class="para">
+ The following types of print queues can be configured:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guimenuitem"><strong>AppSocket/HP JetDirect</strong></span> — a printer connected directly to the network through HP JetDirect or Appsocket interface instead of a computer.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guimenuitem"><strong>Internet Printing Protocol (IPP)</strong></span> — a printer that can be accessed over a TCP/IP network via the Internet Printing Protocol (for example, a printer attached to another Fedora system running CUPS on the network).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guimenuitem"><strong>LPD/LPR Host or Printer</strong></span> — a printer attached to a different UNIX system that can be accessed over a TCP/IP network (for example, a printer attached to another Fedora system running LPD on the network).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guimenuitem"><strong>Networked Windows (SMB)</strong></span> — a printer attached to a different system which is sharing a printer over an SMB network (for example, a printer attached to a Microsoft <span class="trademark">Windows</span>™ machine).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guimenuitem"><strong>Networked JetDirect</strong></span> — a printer connected directly to the network through HP JetDirect instead of a computer.
+ </div></li></ul></div><div class="important"><h2>Important</h2><a id="id670324" class="indexterm"></a><div class="para">
+ If you add a new print queue or modify an existing one, you must apply the changes for them to take effect.
+ </div></div><div class="para">
+ Clicking the <span class="guibutton"><strong>Apply</strong></span> button prompts the printer daemon to restart with the changes you have configured.
+ </div><div class="para">
+ Clicking the <span class="guibutton"><strong>Revert</strong></span> button discards unapplied changes.
+ </div><div class="section" title="23.1. Adding a Local Printer" id="s1-printing-local-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-local-printer">23.1. Adding a Local Printer</h2></div></div></div><a id="id670368" class="indexterm"></a><a id="id670381" class="indexterm"></a><div class="para">
+ To add a local printer, such as one attached through a parallel port or USB port on your computer, click the <span class="guibutton"><strong>New Printer</strong></span> button in the main <span class="application"><strong>Printer Configuration Tool</strong></span> window to display the window in <a class="xref" href="ch-Printer_Configuration.html#fig-printconf-add" title="Figure 23.2. Adding a Printer">Figure 23.2, “ <span class="application">Adding a Printer</span> ”</a>.
+ </div><div class="figure" title="Figure 23.2. Adding a Printer" id="fig-printconf-add"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-add-printer.png" width="444" alt="Adding a Printer" /><div class="longdesc"><div class="para">
+ Adding a printer
+ </div></div></div></div><h6>Figure 23.2. <span class="application">Adding a Printer</span> </h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to proceed.
+ </div><div class="para">
+ Enter a unique name for the printer in the <span class="guilabel"><strong>Printer Name</strong></span> field. The printer name can contain letters, numbers, dashes (-), and underscores (_); it <span class="emphasis"><em>must not</em></span> contain any spaces.
+ </div><div class="para">
+ You can also use the <span class="guilabel"><strong>Description</strong></span> and <span class="guilabel"><strong>Location</strong></span> fields to further distinguish this printer from others that may be configured on your system. Both of these fields are optional, and may contain spaces.
+ </div><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to open the <span class="guilabel"><strong>New Printer</strong></span> dialog (refer to <a class="xref" href="ch-Printer_Configuration.html#fig-printconf-local" title="Figure 23.3. Adding a Local Printer">Figure 23.3, “Adding a Local Printer”</a>). If the printer has been automatically detected, the printer model appears in <span class="guilabel"><strong>Select Connection</strong></span>. Select the printer model and click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div><div class="para">
+ If the device does not automatically appear, select the device to which the printer is connected (such as <span class="guilabel"><strong>LPT #1</strong></span> or <span class="guilabel"><strong>Serial Port #1</strong></span>) in <span class="guilabel"><strong>Select Connection</strong></span>.
+ </div><div class="figure" title="Figure 23.3. Adding a Local Printer" id="fig-printconf-local"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-local.png" width="444" alt="Adding a Local Printer" /><div class="longdesc"><div class="para">
+ Adding a local printer
+ </div></div></div></div><h6>Figure 23.3. Adding a Local Printer</h6></div><br class="figure-break" /><div class="para">
+ Next, select the printer type. Refer to <a class="xref" href="s1-printing-select-model.html" title="23.5. Selecting the Printer Model and Finishing">Section 23.5, “Selecting the Printer Model and Finishing”</a> for details.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-additional-resources.html"><strong>Prev</strong>22.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-printing-ipp-printer.html"><strong>Next</strong>23.2. Adding an IPP Printer</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-RPM.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-RPM.html
new file mode 100644
index 0000000..653e322
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-RPM.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enabl
e iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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>Prev</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><dd><dl><dt><span class="section"><a href="s1-rp
m-using.html#s2-rpm-finding">3.2.1. Finding RPM Packages</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Upgrading.html">3.2.2. Installing and Upgrading</a></span></dt><dt><span class="section"><a href="sec-Configuration_File_Changes.html">3.2.3. Configuration File Changes</a></span></dt><dt><span class="section"><a href="s2-rpm-uninstalling.html">3.2.4. Uninstalling</a></span></dt><dt><span class="section"><a href="s2-rpm-freshening.html">3.2.5. Freshening</a></span></dt><dt><span class="section"><a href="s2-rpm-querying.html">3.2.6. Querying</a></span></dt><dt><span class="section"><a href="s2-rpm-verifying.html">3.2.7. Verifying</a></span></dt></dl></dd><dt><span class="section"><a href="s1-check-rpm-sig.html">3.3. Checking a Package's Signature</a></span></dt><dd><dl><dt><span class="section"><a href="s1-check-rpm-sig.html#s2-keys-importing">3.3.1. Importing Keys</a></span></dt><dt><span class="section"><a href="s2-keys-checking.html">3.3.2. Verifyin
g Signature of Packages</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="s1-rpm-additional-resources.html#s2-rpm-installed-docs">3.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-rpm-useful-websites.html">3.5.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-rpm-related-books.html">3.5.3. Related Books</a></span></dt></dl></dd></dl></div><a id="id654159" class="indexterm"></a><a id="id654153" class="indexterm"></a><div class="para">
+ The <em class="firstterm">RPM Package Manager</em> (RPM) is an open packaging system
+ <a id="id654140" 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 13. 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"><h2>Use Yum Instead of RPM Whenever Possible</h2><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="id994725" 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 class="important"><h2>Important</h2><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 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="id610678" 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"><h2>Note</h2><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 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="id827558" 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><span class="term">Upgradability
+ <a id="id999469" 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><span class="term">Powerful Querying
+ <a id="id638795" 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><span class="term"> System Verification
+ <a id="id901647" 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><span class="term">Pristine Sources
+ <a id="id715310" 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_Draft_Documentation/0.1/html/Deployment_Guide/ch-Samba.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Samba.html
new file mode 100644
index 0000000..a7c522b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-Samba.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>Chapter 9. Samba</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="8.5.2. Useful Websites" /><link rel="next" href="s1-samba-daemons.html" title="9.2. Samba Daemons and Related Services" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade you
r browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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></li><li class="next"><a accesskey="n" href="s1-samba-daemons.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 9. Samba" id="ch-Samba" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. Samba</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Samba.html#samba-rgs-overview">9.1. Introduction to Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Samba.html#s2-samba-abilities">9.1.1. Samba Features</a></span></dt></dl></d
d><dt><span class="section"><a href="s1-samba-daemons.html">9.2. Samba Daemons and Related Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-daemons.html#s2-samba-services">9.2.1. Samba Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-connect-share.html">9.3. Connecting to a Samba Share</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-connect-share.html#s2-samba-connect-share-cmdline">9.3.1. Command Line</a></span></dt><dt><span class="section"><a href="s1-samba-mounting.html">9.3.2. Mounting the Share</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-configuring.html">9.4. Configuring a Samba Server</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-configuring.html#s2-samba-configuring-gui">9.4.1. Graphical Configuration</a></span></dt><dt><span class="section"><a href="s2-samba-configuring-cmdline.html">9.4.2. Command Line Configuration</a></span></dt><dt><span class
="section"><a href="s2-samba-encrypted-passwords.html">9.4.3. Encrypted Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-startstop.html">9.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="s1-samba-servers.html">9.6. Samba Server Types and the <code class="command">smb.conf</code> File</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-servers.html#s2-samba-standalone">9.6.1. Stand-alone Server</a></span></dt><dt><span class="section"><a href="s2-samba-domain-member.html">9.6.2. Domain Member Server</a></span></dt><dt><span class="section"><a href="s2-samba-domain-controller.html">9.6.3. Domain Controller</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-security-modes.html">9.7. Samba Security Modes</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-security-modes.html#s2-samba-user-level">9.7.1. User-Level Security</a></span></dt><dt><span class="section"><a href
="s2-samba-share-level.html">9.7.2. Share-Level Security</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-account-info-dbs.html">9.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="s1-samba-network-browsing.html">9.9. Samba Network Browsing</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-network-browsing.html#s2-samba-domain-browsing">9.9.1. Domain Browsing</a></span></dt><dt><span class="section"><a href="s2-samba-wins.html">9.9.2. WINS (Windows Internetworking Name Server)</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-cups.html">9.10. Samba with CUPS Printing Support</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-cups.html#s2-samba-cups-smb.conf">9.10.1. Simple <code class="filename">smb.conf</code> Settings</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-programs.html">9.11. Samba Distribution Programs</a></span></dt><dt><span class
="section"><a href="s1-samba-resources.html">9.12. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-resources.html#s2-samba-resources-installed">9.12.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-samba-resources-published.html">9.12.2. Related Books</a></span></dt><dt><span class="section"><a href="s2-samba-resources-community.html">9.12.3. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id756774" class="indexterm"></a><a id="id954762" class="indexterm"></a><div class="para">
+ <em class="firstterm">Samba</em> is an open source implementation of the Server Message Block (SMB) protocol. It allows the networking of Microsoft <span class="trademark">Windows</span>®, Linux, UNIX, and other operating systems together, enabling access to Windows-based file and printer shares. Samba's use of SMB allows it to appear as a Windows server to Windows clients.
+ </div><div class="section" title="9.1. Introduction to Samba" id="samba-rgs-overview"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="samba-rgs-overview">9.1. Introduction to Samba</h2></div></div></div><a id="id895939" class="indexterm"></a><div class="para">
+ The third major release of Samba, version 3.0.0, introduced numerous improvements from prior versions, including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The ability to join an Active Directory domain by means of LDAP and Kerberos
+ </div></li><li class="listitem"><div class="para">
+ Built in Unicode support for internationalization
+ </div></li><li class="listitem"><div class="para">
+ Support for Microsoft Windows XP Professional client connections to Samba servers without needing local registry hacking
+ </div></li><li class="listitem"><div class="para">
+ Two new documents developed by the Samba.org team, which include a 400+ page reference manual, and a 300+ page implementation and integration manual. For more information about these published titles, refer to <a class="xref" href="s2-samba-resources-published.html" title="9.12.2. Related Books">Section 9.12.2, “Related Books”</a>.
+ </div></li></ul></div><div class="section" title="9.1.1. Samba Features" id="s2-samba-abilities"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-abilities">9.1.1. Samba Features</h3></div></div></div><a id="id713401" class="indexterm"></a><div class="para">
+ Samba is a powerful and versatile server application. Even seasoned system administrators must know its abilities and limitations before attempting installation and configuration.
+ </div><div class="para">
+ What Samba can do:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Serve directory trees and printers to Linux, UNIX, and Windows clients
+ </div></li><li class="listitem"><div class="para">
+ Assist in network browsing (with or without NetBIOS)
+ </div></li><li class="listitem"><div class="para">
+ Authenticate Windows domain logins
+ </div></li><li class="listitem"><div class="para">
+ Provide Windows Internet Name Service (WINS) name server resolution
+ </div></li><li class="listitem"><div class="para">
+ Act as a Windows <span class="trademark">NT</span>®-style Primary Domain Controller (PDC)
+ </div></li><li class="listitem"><div class="para">
+ Act as a Backup Domain Controller (BDC) for a Samba-based PDC
+ </div></li><li class="listitem"><div class="para">
+ Act as an Active Directory domain member server
+ </div></li><li class="listitem"><div class="para">
+ Join a Windows NT/2000/2003 PDC
+ </div></li></ul></div><div class="para">
+ What Samba cannot do:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Act as a BDC for a Windows PDC (and vice versa)
+ </div></li><li class="listitem"><div class="para">
+ Act as an Active Directory domain controller
+ </div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-openssh-useful-websites.html"><strong>Prev</strong>8.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-samba-daemons.html"><strong>Next</strong>9.2. Samba Daemons and Related Services</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_Apache_HTTP_Server.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_Apache_HTTP_Server.html
new file mode 100644
index 0000000..f4ded1d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_Apache_HTTP_Server.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="10.6. Additional Resources" /><link rel="next" href="s1-httpd-mig.html" title="11.2. Migrating Apache HTTP Server Configuration Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This i
s an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-httpd-mig.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-httpd-v2">11.1. Apache HTTP Server 2.2</a></span></dt><dd><dl><dt><span class=
"section"><a href="ch-The_Apache_HTTP_Server.html#s2-httpd-v2-features">11.1.1. Features of Apache HTTP Server 2.2</a></span></dt></dl></dd><dt><span class="section"><a href="s1-httpd-mig.html">11.2. Migrating Apache HTTP Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="s1-httpd-mig.html#s1-httpd-v22-mig">11.2.1. Migrating Apache HTTP Server 2.0 Configuration Files</a></span></dt><dt><span class="section"><a href="s3-httpd-v2-mig.html">11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-startstop.html">11.3. Starting and Stopping <code class="command">httpd</code> </a></span></dt><dt><span class="section"><a href="s1-apache-config-ui.html">11.4. Apache HTTP Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-apache-config-ui.html#s2-httpd-basic-settings">11.4.1. Basic Settings</a></span></dt><dt><span class="section"><a href=
"s2-httpd-default-settings.html">11.4.2. Default Settings</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-config.html">11.5. Configuration Directives in <code class="filename">httpd.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-apache-config.html#s2-apache-tips">11.5.1. General Configuration Tips</a></span></dt><dt><span class="section"><a href="s2-apache-sslcommands.html">11.5.2. Configuration Directives for SSL</a></span></dt><dt><span class="section"><a href="s2-apache-mpm-containers.html">11.5.3. MPM Specific Server-Pool Directives</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-addmods.html">11.6. Adding Modules</a></span></dt><dt><span class="section"><a href="s1-apache-virtualhosts.html">11.7. Virtual Hosts</a></span></dt><dd><dl><dt><span class="section"><a href="s1-apache-virtualhosts.html#s2-apache-settingupvhosts">11.7.1. Setting Up Virtual Hosts</a></span></dt></dl></dd><dt><span class="secti
on"><a href="s1-httpd-secure-server.html">11.8. Apache HTTP Secure Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-httpd-secure-server.html#s2-secureserver-optionalpackages">11.8.1. An Overview of Security-Related Packages</a></span></dt><dt><span class="section"><a href="s2-secureserver-overview-certs.html">11.8.2. An Overview of Certificates and Security</a></span></dt><dt><span class="section"><a href="s1-secureserver-oldcert.html">11.8.3. Using Pre-Existing Keys and Certificates</a></span></dt><dt><span class="section"><a href="s2-secureserver-certs.html">11.8.4. Types of Certificates</a></span></dt><dt><span class="section"><a href="s2-secureserver-generatingkey.html">11.8.5. Generating a Key</a></span></dt><dt><span class="section"><a href="s1-use-new-key.html">11.8.6. How to configure the server to use the new key</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-additional-resources.html">11.9. Additional Resource
s</a></span></dt><dd><dl><dt><span class="section"><a href="s1-apache-additional-resources.html#s2-apache-additional-resources-web">11.9.1. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id958607" class="indexterm"></a><a id="id917242" class="indexterm"></a><div class="para">
+ The Apache HTTP Server is a robust, commercial-grade open source Web server developed by the Apache Software Foundation (<a href="http://www.apache.org/">http://www.apache.org/</a>). Fedora 13 includes the Apache HTTP Server 2.2 as well as a number of server modules designed to enhance its functionality.
+ </div><div class="para">
+ The default configuration file installed with the Apache HTTP Server works without alteration for most situations. This chapter outlines many of the directives found within its configuration file (<code class="filename">/etc/httpd/conf/httpd.conf</code>) to aid those who require a custom configuration or need to convert a configuration file from the older Apache HTTP Server 1.3 format.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ If using the graphical <span class="application"><strong>HTTP Configuration Tool</strong></span> (<span class="emphasis"><em>system-config-httpd </em></span>), <span class="emphasis"><em>do not</em></span> hand edit the Apache HTTP Server's configuration file as the <span class="application"><strong>HTTP Configuration Tool</strong></span> regenerates this file whenever it is used.
+ </div></div><div class="section" title="11.1. Apache HTTP Server 2.2" id="s1-httpd-v2"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-httpd-v2">11.1. 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.
+ </div><div class="para">
+ This section reviews some of the features of Apache HTTP Server 2.2 and outlines important changes. If you are upgrading from version 1.3, you should also read the instructions on migrating from version 1.3 to version 2.0. For instructions on migrating a version 1.3 configuration file to the 2.0 format, refer to <a class="xref" href="s3-httpd-v2-mig.html" title="11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0">Section 11.2.2, “Migrating Apache HTTP Server 1.3 Configuration Files to 2.0”</a>.
+ </div><div class="section" title="11.1.1. Features of Apache HTTP Server 2.2" id="s2-httpd-v2-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-httpd-v2-features">11.1.1. Features of Apache HTTP Server 2.2</h3></div></div></div><a id="id989419" class="indexterm"></a><div class="para">
+ Apache HTTP Server 2.2 features the following improvements over version 2.0 :
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Improved caching modules (mod_cache, mod_disk_cache, mod_mem_cache).
+ </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><li class="listitem"><div class="para">
+ Support for proxy load balancing (mod_proxy_balancer)
+ </div></li><li class="listitem"><div class="para">
+ support for handling large files (namely, greater than 2GB) on 32-bit platforms
+ </div></li></ul></div><div class="para">
+ The following changes have been made to the default httpd configuration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The mod_cern_meta and mod_asis modules are no longer loaded by default.
+ </div></li><li class="listitem"><div class="para">
+ The mod_ext_filter module is now loaded by default.
+ </div></li></ul></div><div class="para">
+ If upgrading from a previous release of Fedora, the httpd configuration will need to be updated for httpd 2.2. For more information, refer to http://httpd.apache.org/docs/2.2/upgrading.html
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp-additional-resources.html"><strong>Prev</strong>10.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-httpd-mig.html"><strong>Next</strong>11.2. Migrating Apache HTTP Server Configuration ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_BIND_DNS_Server.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_BIND_DNS_Server.html
new file mode 100644
index 0000000..7be5b47
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_BIND_DNS_Server.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>Chapter 7. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="6.4.2. Related Books" /><link rel="next" href="s1-bind-namedconf.html" title="7.2. /etc/named.conf" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgr
ade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="s1-bind-namedconf.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 7. The BIND DNS Server" id="ch-The_BIND_DNS_Server" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. 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">7.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="ch-
The_BIND_DNS_Server.html#s2-bind-introduction-zones">7.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">7.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-bind">7.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-namedconf.html">7.2. <code class="filename">/etc/named.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-namedconf.html#s2-bind-namedconf-state">7.2.1. Common Statement Types</a></span></dt><dt><span class="section"><a href="s2-bind-namedconf-state-other.html">7.2.2. Other Statement Types</a></span></dt><dt><span class="section"><a href="s2-bind-namedconf-comm.html">7.2.3. Comment Tags</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-zone.html">7.3. Zone Files</a></span></dt><dd><dl><dt><span class="section"><a href="s1-
bind-zone.html#s2-bind-zone-directives">7.3.1. Zone File Directives</a></span></dt><dt><span class="section"><a href="s3-bind-zone-rr.html">7.3.2. Zone File Resource Records</a></span></dt><dt><span class="section"><a href="s2-bind-zone-examples.html">7.3.3. Example Zone File</a></span></dt><dt><span class="section"><a href="s2-bind-configuration-zone-reverse.html">7.3.4. Reverse Name Resolution Zone Files</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-rndc.html">7.4. Using <code class="command">rndc</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-rndc.html#s2-bind-rndc-configuration-namedconf">7.4.1. Configuring <code class="filename">/etc/named.conf</code> </a></span></dt><dt><span class="section"><a href="s2-bind-rndc-configuration-rndcconf.html">7.4.2. Configuring <code class="filename">/etc/rndc.conf</code> </a></span></dt><dt><span class="section"><a href="s2-bind-rndc-options.html">7.4.3. Command Line Options</a></span></
dt></dl></dd><dt><span class="section"><a href="s1-bind-features.html">7.5. Advanced Features of BIND</a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-features.html#s2-bind-features-protocol">7.5.1. DNS Protocol Enhancements</a></span></dt><dt><span class="section"><a href="s2-bind-features-views.html">7.5.2. Multiple Views</a></span></dt><dt><span class="section"><a href="s2-bind-features-security.html">7.5.3. Security</a></span></dt><dt><span class="section"><a href="s2-bind-features-ipv6.html">7.5.4. IP version 6</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-mistakes.html">7.6. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="s1-bind-additional-resources.html">7.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-additional-resources.html#s2-bind-installed-docs">7.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-bind-useful-websites.html"
>7.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-bind-related-books.html">7.7.3. Related Books</a></span></dt></dl></dd></dl></div><a id="id919952" class="indexterm"></a><a id="id856779" class="indexterm"></a><div class="para">
+ On most modern networks, including the Internet, users locate other computers by name. This frees users from the daunting task of remembering the numerical network address of network resources. The most effective way to configure a network to allow such name-based connections is to set up a <em class="firstterm">Domain Name Service</em> (<em class="firstterm">DNS</em>) or a <em class="firstterm">nameserver</em>, which resolves hostnames on the network to numerical addresses and vice versa.
+ </div><div class="para">
+ This chapter reviews the nameserver included in Fedora and the <em class="firstterm">Berkeley Internet Name Domain</em> (<em class="firstterm">BIND</em>) DNS server, with an emphasis on the structure of its configuration files and how it may be administered both locally and remotely.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ BIND is also known as the service <code class="command">named</code> in Fedora. You can manage it via the Services Configuration Tool (<code class="command">system-config-service</code>).
+ </div></div><div class="section" title="7.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">7.1. Introduction to DNS</h2></div></div></div><a id="id964521" class="indexterm"></a><a id="id856722" class="indexterm"></a><a id="id920938" class="indexterm"></a><a id="id871580" class="indexterm"></a><a id="id587982" class="indexterm"></a><a id="id621542" class="indexterm"></a><a id="id621560" class="indexterm"></a><div class="para">
+ DNS associates hostnames with their respective IP addresses, so that when users want to connect to other machines on the network, they can refer to them by name, without having to remember IP addresses.
+ </div><div class="para">
+ Use of DNS also has advantages for system administrators, allowing the flexibility to change the IP address for a host without affecting name-based queries to the machine. Conversely, administrators can shuffle which machines handle a name-based query.
+ </div><div class="para">
+ DNS is normally implemented using centralized servers that are authoritative for some domains and refer to other DNS servers for other domains.
+ </div><div class="para">
+ 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 the nameserver does not have an authoritative answer about the name the which host requested, 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. Then, with that information, it queries the authoritative nameservers to get the requested name.
+ </div><div class="section" title="7.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">7.1.1. Nameserver Zones</h3></div></div></div><a id="id571077" 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>. A resource record is usually the <em class="firstterm">fully qualified domain name</em> (FQDN) of a host. Resource records are broken down into multiple sections. These sections are organized into a tree-like hierarchy consisting of a main trunk, primary branches, secondary branches, and so forth. Consider the following resource record:
+ </div><pre class="screen">bob.sales.example.com</pre><div class="para">
+ When looking at how a resource record is resolved to find, for example, the IP address that relates to a particular system, read the name from right to left. Each level of the hierarchy is divided by a period (often called a "dot": <span class="quote">“<span class="quote"><code class="computeroutput">.</code> </span>”</span>). In this example, therefore, <code class="computeroutput">com</code> defines the <em class="firstterm">top-level domain</em> for this resource record. The name <code class="computeroutput">example</code> is a sub-domain under <code class="computeroutput">com</code>, while <code class="computeroutput">sales</code> is a sub-domain under <code class="computeroutput">example</code>. The name furthest to the left, <code class="computeroutput">bob</code>, identifies a resource record which is part of the <code class="computeroutput">sales.example.com</code> domain.
+ </div><div class="para">
+ Except for the first (leftmost) part of the resource record (<code class="computeroutput">bob</code>), each section is called a <em class="firstterm">zone</em>. Zone defines a specific <em class="firstterm">namespace</em>. A zone contains definitions of resource records, which usually contain host-to-IP address mappings and IP address-to-host mappings, which are called <em class="firstterm">reverse records</em>).
+ </div><div class="para">
+ Zones are defined on authoritative nameservers through the use of <em class="firstterm">zone files</em>, which define the resource records in that 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. Any nameserver can be a primary or secondary nameserver for multiple zones at the same time. It all depends on how the nameserver is configured.
+ </div></div><div class="section" title="7.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">7.1.2. Nameserver Types</h3></div></div></div><a id="id727733" class="indexterm"></a><a id="id727751" class="indexterm"></a><a id="id727768" class="indexterm"></a><a id="id727786" class="indexterm"></a><a id="id727804" class="indexterm"></a><a id="id855339" class="indexterm"></a><a id="id855352" class="indexterm"></a><a id="id855366" class="indexterm"></a><div class="para">
+ There are two nameserver configuration types:
+ </div><div class="variablelist"><dl><dt><span class="term">authoritative</span></dt><dd><div class="para">
+ This category includes both primary (master) and secondary (slave) servers. Those servers answer only for resource records which are part of their zones.
+ </div></dd><dt><span class="term">recursive</span></dt><dd><div class="para">
+ Offers resolution services, but is not authoritative for any zones. Answers for all resolutions are cached in memory for a fixed period of time, which is specified by the retrieved RR.
+ </div></dd></dl></div><div class="para">
+ A nameserver may be one or both of these types. For example, a nameserver can be a master for some zones, a slave for others, and offer recursive services for others. However the best practice is not to combine authoritative and recursive servers due their absolutely different requirements. Authoritative servers are available for all clients and they should be available all the time otherwise it is not possible to resolve particular subtree of the DNS database. Recursive lookups take far more time than authoritative responses thus recursive servers should be available for a restricted number of clients. Otherwise recursive server could be easy target for <em class="firstterm">distributed denial of service (DDoS)</em> attack.
+ </div></div><div class="section" title="7.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">7.1.3. BIND as a Nameserver</h3></div></div></div><a id="id855445" class="indexterm"></a><a id="id985835" class="indexterm"></a><a id="id985852" class="indexterm"></a><a id="id985874" class="indexterm"></a><a id="id985896" class="indexterm"></a><div class="para">
+ BIND is set of DNS related programs. It contains a monolithic nameserver called <code class="command">/usr/sbin/named</code>, an administration utility called <code class="command">/usr/sbin/rndc</code> and DNS debugging utility called <code class="command">/usr/bin/dig</code>. More information about <code class="command">rndc</code> can be found in <a class="xref" href="s1-bind-rndc.html" title="7.4. Using rndc">Section 7.4, “Using <code class="command">rndc</code> ”</a>.
+ </div><div class="para">
+ BIND stores its configuration files in the following locations:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="filename">/etc/named.conf</code> </span></dt><dd><div class="para">
+ The configuration file for the <code class="command">named</code> daemon
+ </div></dd><dt><span class="term"> <code class="filename">/var/named/</code> directory</span></dt><dd><div class="para">
+ The <code class="command">named</code> working directory which stores zone and statistic files
+ </div></dd></dl></div><div class="note"><h2>Note</h2><div class="para">
+ If you have installed the <code class="filename">bind-chroot</code> package, the BIND service will run in the <code class="command">/var/named/chroot</code> environment. All configuration files will be moved there. As such, <code class="filename">named.conf</code> will be located in <code class="filename">/var/named/chroot/etc/named.conf</code>, and so on.
+ </div></div><div class="para">
+ The next few sections review the BIND configuration in more detail.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-services-additional-resources-books.html"><strong>Prev</strong>6.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="s1-bind-namedconf.html"><strong>Next</strong>7.2. /etc/named.conf </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_X_Window_System.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_X_Window_System.html
new file mode 100644
index 0000000..09e5b6a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_X_Window_System.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>Chapter 21. The X Window 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="20.3. Setting Up a Typing Break" /><link rel="next" href="s1-x-clients.html" title="21.2. Desktop Environments and Window Managers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your b
rowser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-clients.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 21. The X Window System" id="ch-The_X_Window_System" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. The X Window System</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-The_X_Window_System.html#s1-x-server">21.1. The X11R7.1 Release</a></span></dt><dt><span class="section"><a href="s1-x-clients.html">21.2. Desktop Environments and Win
dow Managers</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-clients.html#s2-x-clients-desktop">21.2.1. Desktop Environments</a></span></dt><dt><span class="section"><a href="s2-x-clients-winmanagers.html">21.2.2. Window Managers</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-server-configuration.html">21.3. X Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-server-configuration.html#s2-x-server-config-xorg.conf">21.3.1. <code class="filename">xorg.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-fonts.html">21.4. Fonts</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-fonts.html#s2-x-fonts-fontconfig">21.4.1. Fontconfig</a></span></dt><dt><span class="section"><a href="s2-x-fonts-core.html">21.4.2. Core X Font System</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-runlevels.html">21.5. Runlevels and X</a></span></dt><dd><dl><dt><span class="s
ection"><a href="s1-x-runlevels.html#s2-x-runlevels-3">21.5.1. Runlevel 3</a></span></dt><dt><span class="section"><a href="s2-x-runlevels-5.html">21.5.2. Runlevel 5</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-additional-resources.html">21.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-additional-resources.html#s2-x-installed-documentation">21.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-x-useful-websites.html">21.6.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="id755800" class="indexterm"></a><a id="id881522" class="indexterm"></a><a id="id992330" class="indexterm"></a><a id="id739509" class="indexterm"></a><a id="id1015441" class="indexterm"></a><div class="para">
+ While the heart of Fedora is the kernel, for many users, the face of the operating system is the graphical environment provided by the <em class="firstterm">X Window System</em>, also called <em class="firstterm">X</em>.
+ </div><div class="para">
+ Other windowing environments have existed in the UNIX world, including some that predate the release of the X Window System in June 1984. Nonetheless, X has been the default graphical environment for most UNIX-like operating systems, including Fedora, for many years.
+ </div><div class="para">
+ The graphical environment for Fedora is supplied by the <em class="firstterm">X.Org Foundation</em>, an open source organization created to manage development and strategy for the X Window System and related technologies. X.Org is a large-scale, rapidly developing project with hundreds of developers around the world. It features a wide degree of support for a variety of hardware devices and architectures, and can run on a variety of different operating systems and platforms. This release for Fedora specifically includes the X11R7.1 release of the X Window System.
+ </div><div class="para">
+ The X Window System uses a client-server architecture. The <em class="firstterm">X server</em> (the <code class="command">Xorg</code> binary) listens for connections from <em class="firstterm">X client</em> applications via a network or local loopback interface. The server communicates with the hardware, such as the video card, monitor, keyboard, and mouse. X client applications exist in the user-space, creating a <em class="firstterm">graphical user interface</em> (<em class="firstterm">GUI</em>) for the user and passing user requests to the X server.
+ </div><div class="section" title="21.1. The X11R7.1 Release" id="s1-x-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-server">21.1. The X11R7.1 Release</h2></div></div></div><a id="id751442" class="indexterm"></a><div class="para">
+ Fedora 13 uses the X11R7.1 release as the base X Window System, which includes several video driver, EXA, and platform support enhancements over the previous release, among others. In addition, this release also includes several automatic configuration features for the X server.
+ </div><div class="para">
+ X11R7.1 is the first release to take specific advantage of the modularization of the X Window System. This modularization, which splits X into logically distinct modules, makes it easier for open source developers to contribute code to the system.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Fedora no longer provides the <span class="trademark">XFree86</span>™ server packages. Before upgrading a system to the latest version of Fedora, be sure that the system's video card is compatible with the X11R7.1 release by checking the Red Hat Hardware Compatibility List located online at <a href="http://hardware.redhat.com/">http://hardware.redhat.com/</a>.
+ </div></div><div class="para">
+ In the X11R7.1 release, all libraries, headers, and binaries now live under <code class="filename">/usr/</code> instead of <code class="filename">/usr/X11R6</code>. The <code class="filename">/etc/X11/</code> directory contains configuration files for X client and server applications. This includes configuration files for the X server itself, the <code class="command">xfs</code> font server, the X display managers, and many other base components.
+ </div><div class="para">
+ The configuration file for the newer Fontconfig-based font architecture is still <code class="filename">/etc/fonts/fonts.conf</code>. For more on configuring and adding fonts, refer to <a class="xref" href="s1-x-fonts.html" title="21.4. Fonts">Section 21.4, “Fonts”</a>.
+ </div><div class="para">
+ Because the X server performs advanced tasks on a wide array of hardware, it requires detailed information about the hardware it works on. The X server automatically detects some of this information; other details must be configured.
+ </div><div class="para">
+ The installation program installs and configures X automatically, unless the X11R7.1 release packages are not selected for installation. However, if there are any changes to the monitor, video card or other devices managed by the X server, X must be reconfigured.
+ </div><div class="para">
+ In some situations, reconfiguring the X server may require manually editing its configuration file, <code class="filename">/etc/X11/xorg.conf</code>. For information about the structure of this file, refer to <a class="xref" href="s1-x-server-configuration.html" title="21.3. X Server Configuration Files">Section 21.3, “X Server Configuration Files”</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-keyboard-break.html"><strong>Prev</strong>20.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-x-clients.html"><strong>Next</strong>21.2. Desktop Environments and Window Managers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_sysconfig_Directory.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_sysconfig_Directory.html
new file mode 100644
index 0000000..f813b5e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-The_sysconfig_Directory.html
@@ -0,0 +1,243 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-proc-additional-resources.html" title="17.5. References" /><link rel="next" href="s1-sysconfig-etcsysconf-dir.html" title="18.2. Directories in the /etc/sysconfig/ Directory" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to vie
w it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 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/</co
de> Directory</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-arpwatch">18.1.1. <code class="filename">/etc/sysconfig/arpwatch</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-authconfig">18.1.2. <code class="filename">/etc/sysconfig/authconfig</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-autofs">18.1.3. <code class="filename">/etc/sysconfig/autofs</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-clock">18.1.4. <code class="filename">/etc/sysconfig/clock</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-desktop">18.1.5. <code class="filename">/etc/sysconfig/desktop</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-dhcpd">18.1.6. <code class="filena
me">/etc/sysconfig/dhcpd</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-firewall">18.1.7. <code class="filename">/etc/sysconfig/firstboot</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-i18n">18.1.8. <code class="filename">/etc/sysconfig/i18n</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-init">18.1.9. <code class="filename">/etc/sysconfig/init</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-ip6tables">18.1.10. <code class="filename">/etc/sysconfig/ip6tables-config</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-kybd">18.1.11. <code class="filename">/etc/sysconfig/keyboard</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-named">18.1.12. <code c
lass="filename">/etc/sysconfig/named</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-network">18.1.13. <code class="filename">/etc/sysconfig/network</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-ntpd">18.1.14. <code class="filename">/etc/sysconfig/ntpd</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-radvd">18.1.15. <code class="filename">/etc/sysconfig/radvd</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-samba">18.1.16. <code class="filename">/etc/sysconfig/samba</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-selinux">18.1.17. <code class="filename">/etc/sysconfig/selinux</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-sendmail">18.1.18. <co
de class="filename">/etc/sysconfig/sendmail</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-spamd">18.1.19. <code class="filename">/etc/sysconfig/spamassassin</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-squid">18.1.20. <code class="filename">/etc/sysconfig/squid</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-rcu">18.1.21. <code class="filename">/etc/sysconfig/system-config-users</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-vncservers">18.1.22. <code class="filename">/etc/sysconfig/vncservers</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-xinetd">18.1.23. <code class="filename">/etc/sysconfig/xinetd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysconfig-etcsysconf-di
r.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><dd><dl><dt><span class="section"><a href="s1-sysconfig-additional-resources.html#s2-sysconfig-installed-documentation">18.3.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id715404" class="indexterm"></a><a id="id905602" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/</code> directory contains a variety of system configuration files for Fedora.
+ </div><div class="para">
+ This chapter outlines some of the files 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="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="id828591" class="indexterm"></a><div class="para">
+ The following sections offer descriptions of files normally found in the <code class="filename">/etc/sysconfig/</code> directory. Files not listed here, as well as extra file options, are found in the <code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code><version-number></code></em>/sysconfig.txt</code> file (replace <em class="replaceable"><code><version-number></code></em> with the version of the <code class="filename">initscripts</code> package). Alternatively, looking through the initscripts in the <code class="filename">/etc/rc.d/</code> directory can prove helpful.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ If some of the files listed here are not present in the <code class="filename">/etc/sysconfig/</code> directory, then the corresponding program may not be installed.
+ </div></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="id855235" 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. The <code class="command">arpwatch</code> daemon maintains a table of Ethernet MAC addresses and their IP address pairings. By default, this file sets the owner of the <code class="command">arpwatch</code> process to the user <code class="computeroutput">pcap</code> and sends any messages to the <code class="command">root</code> mail queue. For more information regarding available parameters for this file, refer to the <code class="command">arpwatch</code> man page.
+ </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="id824177" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/authconfig</code> file sets the authorization to be used on the host. It contains one or more of the following lines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">PASSWORDALGORITHM=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">descrypt</code> — DESCRYPT is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">bigcrypt</code> — BIGCRYPT is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">md5</code> — MD5 is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sha256</code> — SHA256 is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">sha512</code> — SHA512 is used for authentication.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">USEKERBEROS=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Kerberos is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Kerberos is not used for authentication.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">USELDAPAUTH=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — LDAP is used for authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — LDAP is not used for authentication.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">FORCELEGACY=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — The implicit use of SSSD by the <span class="application"><strong>Authentication Configuration Tool</strong></span> is disabled.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — The implicit use of SSSD by the <span class="application"><strong>Authentication Configuration Tool</strong></span> is enabled.
+ </div></li></ul></div></li></ul></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="id656213" 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-ROMs, diskettes, and other media.
+ </div><div class="para">
+ The <code class="filename">/etc/sysconfig/autofs</code> file may contain the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">LOCALOPTIONS="<em class="replaceable"><code><value></code></em>"</code>, where <em class="replaceable"><code><value></code></em> is a string for defining machine-specific automount rules. The default value is an empty string (<code class="command">""</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">DAEMONOPTIONS="<em class="replaceable"><code><value></code></em>"</code>, where <em class="replaceable"><code><value></code></em> is the timeout length in seconds before unmounting the device. The default value is 60 seconds (<code class="command">"--timeout=60"</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">UNDERSCORETODOT=<em class="replaceable"><code><value></code></em> </code>, where <em class="replaceable"><code><value></code></em> is a binary value that controls whether to convert underscores in file names into dots. For example, <code class="command">auto_home</code> to <code class="command">auto.home</code> and <code class="command">auto_mnt</code> to <code class="command">auto.mnt</code>. The default value is 1 (true).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">DISABLE_DIRECT=<em class="replaceable"><code><value></code></em> </code>, where <em class="replaceable"><code><value></code></em> is a binary value that controls whether to disable direct mount support, as the Linux implementation does not conform to the Sun Microsystems' automounter behavior. The default value is 1 (true), and allows for compatibility with the Sun automounter options specification syntax.
+ </div></li></ul></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="id949506" 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.
+ </div><div class="para">
+ The correct values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">UTC=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following boolean values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">true</code> or <code class="command">yes</code> — The hardware clock is set to Universal Time.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">false</code> or <code class="command">no</code> — The hardware clock is set to local time.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">ARC=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the following:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">false</code> or <code class="command">no</code> — This value indicates that the normal UNIX epoch is in use. Other values are used by systems not supported by Fedora.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SRM=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the following:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">false</code> or <code class="command">no</code> — This value indicates that the normal UNIX epoch is in use. Other values are used by systems not supported by Fedora.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ZONE=<code class="filename"><em class="replaceable"><code><filename></code></em> </code> </code> — The time zone file under <code class="filename">/usr/share/zoneinfo</code> that <code class="filename">/etc/localtime</code> is a copy of. The file contains information such as:
+ </div><pre class="screen">ZONE="America/New York"
+</pre><div class="para">
+ Note that the <code class="command">ZONE</code> parameter is read by the <span class="application"><strong>Time and Date Properties Tool</strong></span> (<code class="command">system-config-date</code>), and manually editing it does not change the system timezone.
+ </div></li></ul></div><div class="para">
+ Earlier releases of Fedora used the following values (which are deprecated):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">CLOCKMODE=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">GMT</code> — The clock is set to Universal Time (Greenwich Mean Time).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ARC</code> — The ARC console's 42-year time offset is in effect (for Alpha-based systems only).
+ </div></li></ul></div></li></ul></div></div><div class="section" title="18.1.5. /etc/sysconfig/desktop" id="s2-sysconfig-desktop"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-desktop">18.1.5. <code class="filename">/etc/sysconfig/desktop</code> </h3></div></div></div><a id="id764548" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/desktop</code> file specifies the desktop for new users and the display manager to run when entering runlevel 5.
+ </div><div class="para">
+ Correct values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">DESKTOP="<em class="replaceable"><code><value></code></em>"</code>, where <code class="command">"<em class="replaceable"><code><value></code></em>"</code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">GNOME</code> — Selects the <span class="application"><strong>GNOME</strong></span> desktop environment.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">KDE</code> — Selects the <span class="application"><strong>KDE</strong></span> desktop environment.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">DISPLAYMANAGER="<em class="replaceable"><code><value></code></em>"</code>, where <code class="command">"<em class="replaceable"><code><value></code></em>"</code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">GNOME</code> — Selects the <span class="application"><strong>GNOME Display Manager</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">KDE</code> — Selects the <span class="application"><strong>KDE Display Manager</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">XDM</code> — Selects the <span class="application"><strong>X Display Manager</strong></span>.
+ </div></li></ul></div></li></ul></div><div class="para">
+ For more information, refer to <a class="xref" href="ch-The_X_Window_System.html" title="Chapter 21. The X Window System">Chapter 21, <i>The X Window System</i></a>.
+ </div></div><div class="section" title="18.1.6. /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.6. <code class="filename">/etc/sysconfig/dhcpd</code> </h3></div></div></div><a id="id742189" 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. The <code class="command">dhcpd</code> daemon implements the Dynamic Host Configuration Protocol (DHCP) and the Internet Bootstrap Protocol (BOOTP). DHCP and BOOTP assign IP addresses and other configuration information to machines on the network. For more information about what parameters are available in this file, refer to the <code class="command">dhcpd</code> man page.
+ </div></div><div class="section" title="18.1.7. /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.7. <code class="filename">/etc/sysconfig/firstboot</code> </h3></div></div></div><a id="id1999041" class="indexterm"></a><div class="para">
+ The first time the system boots, the <code class="command">/sbin/init</code> program calls the <code class="filename">etc/rc.d/init.d/firstboot</code> script, which in turn launches the <span class="application"><strong> Setup Agent</strong></span>. This application allows the user to install the latest updates as well as additional applications and documentation.
+ </div><div class="para">
+ The <code class="filename">/etc/sysconfig/firstboot</code> file tells the <span class="application"><strong> Setup Agent</strong></span> application not to run on subsequent reboots. To run it the next time the system boots, remove <code class="filename">/etc/sysconfig/firstboot</code> and execute <code class="command">chkconfig --level 5 firstboot on</code>.
+ </div></div><div class="section" title="18.1.8. /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.8. <code class="filename">/etc/sysconfig/i18n</code> </h3></div></div></div><div class="para">
+ The <code class="filename">/etc/sysconfig/i18n</code> file sets the default language, any supported languages, and the default system font. For example:
+ </div><pre class="screen">LANG="en_US.UTF-8"
+SUPPORTED="en_US.UTF-8:en_US:en"
+SYSFONT="latarcyrheb-sun16"
+</pre></div><div class="section" title="18.1.9. /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.9. <code class="filename">/etc/sysconfig/init</code> </h3></div></div></div><a id="id889008" 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.
+ </div><div class="para">
+ The following values may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">BOOTUP=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">color</code> — The standard color boot display, where the success or failure of devices and services starting up is shown in different colors.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">verbose</code> — An old style display which provides more information than purely a message of success or failure.
+ </div></li><li class="listitem"><div class="para">
+ Anything else means a new display, but without ANSI-formatting.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">RES_COL=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the number of the column of the screen to start status labels. The default is set to 60.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MOVE_TO_COL=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> moves the cursor to the value in the <code class="filename">RES_COL</code> line via the <code class="command">echo -en</code> command.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SETCOLOR_SUCCESS=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> sets the success color via the <code class="command">echo -en</code> command. The default color is set to green.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SETCOLOR_FAILURE=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> sets the failure color via the <code class="command">echo -en</code> command. The default color is set to red.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SETCOLOR_WARNING=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> sets the warning color via the <code class="command">echo -en</code> command. The default color is set to yellow.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SETCOLOR_NORMAL=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> resets the color to "normal" via the <code class="command">echo -en</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">LOGLEVEL=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> sets the initial console logging level for the kernel. The default is 3; 8 means everything (including debugging), while 1 means only kernel panics. The <code class="command">rsyslog</code> daemon overrides this setting once started.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">PROMPT=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following boolean values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Enables the key check for interactive mode.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Disables the key check for interactive mode.
+ </div></li></ul></div></li></ul></div></div><div class="section" title="18.1.10. /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.10. <code class="filename">/etc/sysconfig/ip6tables-config</code> </h3></div></div></div><a id="id934756" 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.
+ </div><div class="para">
+ Do not modify this file by hand unless familiar with how to construct <code class="command">ip6tables</code> rules. Rules also can be created manually using the <code class="command">/sbin/ip6tables</code> command. Once created, add the rules to the <code class="filename">/etc/sysconfig/ip6tables</code> file by typing the following command:
+ </div><pre class="screen">
+<code class="command">/sbin/service ip6tables save</code>
+</pre><div class="para">
+ Once this file exists, any firewall rules saved in it persists through a system reboot or a service restart.
+ </div><div class="para">
+ For more information on <code class="command">ip6tables</code>, refer to .
+ </div></div><div class="section" title="18.1.11. /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.11. <code class="filename">/etc/sysconfig/keyboard</code> </h3></div></div></div><a id="id686686" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/keyboard</code> file controls the behavior of the keyboard. The following values may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">KEYBOARDTYPE="sun|pc"</code> where <code class="command">sun</code> means a Sun keyboard is attached on <code class="filename">/dev/kbd</code>, or <code class="command">pc</code> means a PS/2 keyboard connected to a PS/2 port.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">KEYTABLE="<em class="replaceable"><code><file></code></em>"</code>, where <code class="command"><em class="replaceable"><code><file></code></em> </code> is the name of a keytable file.
+ </div><div class="para">
+ For example: <code class="command">KEYTABLE="us"</code>. The files that can be used as keytables start in <code class="filename">/lib/kbd/keymaps/i386</code> and branch into different keyboard layouts from there, all labeled <code class="filename"><em class="replaceable"><code><file></code></em>.kmap.gz</code>. The first file found beneath <code class="filename">/lib/kbd/keymaps/i386</code> that matches the <code class="command">KEYTABLE</code> setting is used.
+ </div></li></ul></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="id788023" 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. The <code class="command">named</code> daemon is a <em class="firstterm">Domain Name System</em> (<em class="firstterm">DNS</em>) server which implements the <em class="firstterm">Berkeley Internet Name Domain</em> (<em class="firstterm">BIND</em>) version 9 distribution. This server maintains a table of which hostnames are associated with IP addresses on the network.
+ </div><div class="para">
+ Currently, only the following values may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">ROOTDIR=<em class="replaceable"><code>"</some/where>"</code></em> </code>, where <code class="command"><em class="replaceable"><code></some/where></code></em> </code> refers to the full directory path of a configured chroot environment under which <code class="command">named</code> runs. This chroot environment must first be configured. Type <code class="command">info chroot</code> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">OPTIONS=<em class="replaceable"><code>"<value>"</code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is any option listed in the man page for <code class="command">named</code> except <code class="option">-t</code>. In place of <code class="option">-t</code>, use the <code class="command">ROOTDIR</code> line above.
+ </div></li></ul></div><div class="para">
+ For more information about available parameters for this file, refer to the <code class="command">named</code> man page. For detailed information on how to configure a BIND DNS server, refer to <a class="xref" href="ch-The_BIND_DNS_Server.html" title="Chapter 7. The BIND DNS Server">Chapter 7, <i>The BIND DNS Server</i></a>. By default, the file contains no parameters.
+ </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="id758112" 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. The following values may be used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">NETWORKING=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following boolean values:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Networking should be configured.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Networking should not be configured.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">HOSTNAME=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> should be the <em class="firstterm">Fully Qualified Domain Name</em> (<em class="firstterm">FQDN</em>), such as <code class="filename">hostname.expample.com</code>, but can be whatever hostname is necessary.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">GATEWAY=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the IP address of the network's gateway.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">GATEWAYDEV=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the gateway device, such as <code class="filename">eth0</code>. Configure this option if you have multiple interfaces on the same subnet, and require one of those interfaces to be the preferred route to the default gateway.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">NISDOMAIN=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the NIS domain name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">NOZEROCONF=<em class="replaceable"><code><value></code></em> </code>, where setting <code class="command"><em class="replaceable"><code><value></code></em> </code> to <code class="command">true</code> disables the zeroconf route.
+ </div><div class="para">
+ By default, the zeroconf route (169.254.0.0) is enabled when the system boots. For more information about zeroconf, refer to <a href="http://www.zeroconf.org/">http://www.zeroconf.org/</a>.
+ </div></li></ul></div><div class="warning"><h2>Warning</h2><div class="para">
+ Do not use custom initscripts to configure network settings. When performing a post-boot network service restart, custom initscripts configuring network settings that are run outside of the network init script lead to unpredictable results.
+ </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="id720400" 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. The <code class="command">ntpd</code> daemon sets and maintains the system clock to synchronize with an Internet standard time server. It implements version 4 of the Network Time Protocol (NTP). For more information about what parameters are available for this file, use a Web browser to view the following file: <code class="filename">/usr/share/doc/ntp-<em class="replaceable"><code><version></code></em>/ntpd.htm</code> (where <em class="replaceable"><code><version></code></em> is the version number of <code class="command">ntpd</code>). By default, this file sets the owner of the <code class="command">ntpd</code> process to the user <code class="computeroutput">ntp</code>.
+ </div></div><div class="section" title="18.1.15. /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.15. <code class="filename">/etc/sysconfig/radvd</code> </h3></div></div></div><a id="id720477" 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. The <code class="command">radvd</code> daemon listens for router requests and sends router advertisements for the IP version 6 protocol. This service allows hosts on a network to dynamically change their default routers based on these router advertisements. For more information about available parameters for this file, refer to the <code class="command">radvd</code> man page. By default, this file sets the owner of the <code class="command">radvd</code> process to the user <code class="computeroutput">radvd</code>.
+ </div></div><div class="section" title="18.1.16. /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.16. <code class="filename">/etc/sysconfig/samba</code> </h3></div></div></div><a id="id965417" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/samba</code> file is used to pass arguments to the <code class="command">smbd</code> and the <code class="command">nmbd</code> daemons at boot time. The <code class="command">smbd</code> daemon offers file sharing connectivity for Windows clients on the network. The <code class="command">nmbd</code> daemon offers NetBIOS over IP naming services. For more information about what parameters are available for this file, refer to the <code class="command">smbd</code> man page. By default, this file sets <code class="command">smbd</code> and <code class="command">nmbd</code> to run in daemon mode.
+ </div></div><div class="section" title="18.1.17. /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.17. <code class="filename">/etc/sysconfig/selinux</code> </h3></div></div></div><a id="id600444" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/selinux</code> file contains the basic configuration options for SELinux. This file is a symbolic link to <code class="filename">/etc/selinux/config</code>.
+ </div></div><div class="section" title="18.1.18. /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.18. <code class="filename">/etc/sysconfig/sendmail</code> </h3></div></div></div><a id="id600491" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/sendmail</code> file allows messages to be sent to one or more clients, routing the messages over whatever networks are necessary. The file sets the default values for the <span class="application"><strong>Sendmail</strong></span> application to run. Its default values are set to run as a background daemon and to check its queue each hour in case something has backed up.
+ </div><div class="para">
+ Values include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">DAEMON=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — <span class="application"><strong>Sendmail</strong></span> should be configured to listen to port 25 for incoming mail. <code class="command">yes</code> implies the use of <span class="application"><strong>Sendmail</strong></span>'s <code class="command">-bd</code> options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — <span class="application"><strong>Sendmail</strong></span> should not be configured to listen to port 25 for incoming mail.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="command">QUEUE=1h</code> which is given to <span class="application"><strong>Sendmail</strong></span> as <code class="command">-q$QUEUE</code>. The <code class="command">-q</code> option is not given to <span class="application"><strong>Sendmail</strong></span> if <code class="filename">/etc/sysconfig/sendmail</code> exists and <code class="filename">QUEUE</code> is empty or undefined.
+ </div></li></ul></div></div><div class="section" title="18.1.19. /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.19. <code class="filename">/etc/sysconfig/spamassassin</code> </h3></div></div></div><a id="id800860" 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. <span class="application"><strong>Spamassassin</strong></span> is an email spam filter application. For a list of available options, refer to the <code class="command">spamd</code> man page. By default, it configures <code class="command">spamd</code> to run in daemon mode, create user preferences, and auto-create whitelists (allowed bulk senders).
+ </div><div class="para">
+ For more information about <span class="application"><strong>Spamassassin</strong></span>, refer to <a class="xref" href="s2-email-procmail-recipes.html#s3-email-mda-spam" title="13.5.2.6. Spam Filters">Section 13.5.2.6, “Spam Filters”</a>.
+ </div></div><div class="section" title="18.1.20. /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.20. <code class="filename">/etc/sysconfig/squid</code> </h3></div></div></div><a id="id867834" 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. The <code class="command">squid</code> daemon is a proxy caching server for Web client applications. For more information on configuring a <code class="command">squid</code> proxy server, use a Web browser to open the <code class="filename">/usr/share/doc/squid-<em class="replaceable"><code><version></code></em>/</code> directory (replace <em class="replaceable"><code><version></code></em> with the <code class="command">squid</code> version number installed on the system). By default, this file sets <code class="command">squid</code> to start in daemon mode and sets the amount of time before it shuts itself down.
+ </div></div><div class="section" title="18.1.21. /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.21. <code class="filename">/etc/sysconfig/system-config-users</code> </h3></div></div></div><a id="id867921" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/system-config-users</code> file is the configuration file for the graphical application, <span class="application"><strong> User Manager</strong></span>. This file is used to filter out system users such as <code class="command">root</code>, <code class="command">daemon</code>, or <code class="command">lp</code>. This file is edited by the <span class="guimenu"><strong>Preferences</strong></span> > <span class="guimenuitem"><strong>Filter system users and groups</strong></span> pull-down menu in the <span class="application"><strong> User Manager</strong></span> application and should never be edited by hand. For more information on using this application, refer to <a class="xref" href="ers_and_Groups.html#s1-users-configui" title="22.1. User and Group Configuration">Section 22.1, “User and Group Configuration”</a>.
+ </div></div><div class="section" title="18.1.22. /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.22. <code class="filename">/etc/sysconfig/vncservers</code> </h3></div></div></div><a id="id721493" 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.
+ </div><div class="para">
+ VNC is a remote display system which allows users to view the desktop environment not only on the machine where it is running but across different networks on a variety of architectures.
+ </div><div class="para">
+ It may contain the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">VNCSERVERS=<em class="replaceable"><code><value></code></em> </code>, where <code class="command"><em class="replaceable"><code><value></code></em> </code> is set to something like <code class="command">"1:fred"</code>, to indicate that a VNC server should be started for user fred on display :1. User fred must have set a VNC password using the <code class="command">vncpasswd</code> command before attempting to connect to the remote VNC server.
+ </div></li></ul></div></div><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN" class="section" title="18.1.23. /etc/sysconfig/xinetd" id="s2-sysconfig-xinetd" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-xinetd">18.1.23. <code class="filename">/etc/sysconfig/xinetd</code> </h3></div></div></div><a id="id595853" 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. The <code class="command">xinetd</code> daemon starts programs that provide Internet services when a request to the port for that service is received. For more information about available parameters for this file, refer to the <code class="command">xinetd</code> man page. For more information on the <code class="command">xinetd</code> service, refer to .
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-additional-resources.html"><strong>Prev</strong>17.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="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_Draft_Documentation/0.1/html/Deployment_Guide/ch-abrt.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-abrt.html
new file mode 100644
index 0000000..19d8c35
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-abrt.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>Chapter 28. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="s2-oprofile-useful-websites.html" title="27.9.2. Useful Websites" /><link rel="next" href="ch28s02.html" title="28.2. Installing and Running ABRT" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe dis
play.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-useful-websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch28s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 28. ABRT" id="ch-abrt" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 28. ABRT</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-abrt.html#id883853">28.1. Overview</a></span></dt><dt><span class="section"><a href="ch28s02.html">28.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="configuring.html">28.3. Configuring ABRT</a></span>
</dt><dt><span class="section"><a href="ch28s04.html">28.4. Plugins and Sending Crash Reports</a></span></dt><dt><span class="section"><a href="ch28s05.html">28.5. Using the Command Line Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch28s05.html#id648054">28.5.1. Viewing Crashes</a></span></dt><dt><span class="section"><a href="ch28s05s02.html">28.5.2. Reporting Crashes</a></span></dt><dt><span class="section"><a href="ch28s05s03.html">28.5.3. Deleting Crashes</a></span></dt></dl></dd></dl></div><div class="section" title="28.1. Overview"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id883853">28.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, through its modular, plugin-oriented architecture, <span class="application"><strong>ABRT</strong></span> provides a number of ways to transmit the crash information to a relevant issue tracker, such as Bugzilla. <span class="application"><strong>ABRT</strong></span>'s various plugins provide the capability of capturing crash information from applications written in the C, C++ and Python languages, as well as the necessary communication backends for issue tracke
rs to which it can report.
+ </div><div class="para">
+ The <span class="application"><strong>ABRT</strong></span> application consists of the <code class="systemitem">abrtd</code> system service, <span class="application"><strong>abrt-applet</strong></span>, which runs in the user's Notification Area, and the <span class="application"><strong>Automatic Bug-Reporting Tool</strong></span> GUI application.
+ </div><div class="mediaobject" align="center"><img src="images/ABRT-Main_Window.png" align="middle" width="444" /><div class="caption"><div class="para">
+ Automatic Bug Reporting Tool Main Window
+ </div></div></div><div class="para">
+ You can open the <span class="application"><strong>ABRT</strong></span> GUI window 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="para">
+ A number of additional packages can be installed to provide <span class="application"><strong>ABRT</strong></span> plugins and addons. Here are descriptions of some of the <span class="application"><strong>ABRT</strong></span> packages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">abrt-desktop</span> — <span class="application"><strong>ABRT</strong></span>'s main package. Installing this package will install <span class="application"><strong>ABRT</strong></span> and also pull in several addon packages. Note that this package is installed by default on Fedora.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt</span> — This package contains the <code class="command">abrtd</code> daemon, configuration file, and localization and other files.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-addon-kerneloops</span> — this plugin provides support for catching and analyzing <em class="firstterm">kernel oopses</em>, i.e. errors that occur in the kernel and which may or may not result in a kernel panic. Also, the <span class="package">abrt-addon-kerneloops</span> plugin provides a way to send its report to a specified server, such as <a href="http://www.kerneloops.org/">kerneloops.org</a>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">gdb</span> — <span class="package">abrt</span> uses <code class="command">gdb</code>, the GNU debugger, to transparently provide relevant crash information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-gui</span> — this package contains the <span class="application"><strong>ABRT</strong></span> Notification Area icon, which notifies users when a program crash has been detected, and the <span class="application"><strong>Automatic Bug Reporting Tool</strong></span> GUI application, which lists program crash instances and provides ways to report those crashes to issue trackers and other locations.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-plugin-bugzilla</span> — this package contains the plugin that is able to automatically submit bug reports to Bugzilla contain crash information such as backtraces and user comments.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-plugin-ticketuploader</span> — this package contains the plugin that uploads tickets created by <span class="application"><strong>ABRT</strong></span> to a specified URL.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-addon-ccpp</span> — this plugin provides support for catching crashes in C and C++ binary programs.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">abrt-addon-python</span> — this plugin provides support for catching crashes in programs written in the Python programming language.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-useful-websites.html"><strong>Prev</strong>27.9.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="ch28s02.html"><strong>Next</strong>28.2. Installing and Running ABRT</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-email.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-email.html
new file mode 100644
index 0000000..3098c95
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-email.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>Chapter 13. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-ftp-useful-websites.html" title="12.6.2. Useful Websites" /><link rel="next" href="s1-email-types.html" title="13.2. Email Program Classifications" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browse
r or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-useful-websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-email-types.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 13. Email" id="ch-email" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 13. Email</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-email.html#s1-email-protocols">13.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="ch-email.html#s2-email-protocols-send">13.1.1. Mail Transport Protocols</a></span></dt><dt><span
class="section"><a href="ch-email.html#s2-email-protocols-client">13.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">13.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta">13.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mda.html">13.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mua.html">13.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">13.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mta.html#s2-email-mta-sendmail">13.3.1. Sendmail</a></span></dt><dt><span class="section"><a href="s2-email-mta-postfix.html">13.3.2. Postfix</a></span></dt><dt><span class="section"><a href="s2-email-mta-fetchmail.html">13.3.3. Fetchmail</a></span></dt></dl></dd><dt><spa
n class="section"><a href="s1-email-switchmail.html">13.4. Mail Transport Agent (MTA) Configuration</a></span></dt><dt><span class="section"><a href="s1-email-mda.html">13.5. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-email-procmail-configuration">13.5.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">13.5.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mua.html">13.6. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">13.6.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">13.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-docs">13.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a h
ref="s2-email-useful-websites.html">13.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-email-related-books.html">13.7.3. Related Books</a></span></dt></dl></dd></dl></div><a id="id986685" 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="13.1. Email Protocols" id="s1-email-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-protocols">13.1. Email Protocols</h2></div></div></div><a id="id875610" 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="13.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">13.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="13.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">13.1.1.1. SMTP</h4></div></div></div><a id="id657072" 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="13.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">13.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="13.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">13.1.2.1. POP</h4></div></div></div><a id="id750153" class="indexterm"></a><div class="para">
+ The default POP server under Fedora is <code class="command">/usr/bin/dovecot</code> and is provided by the <span class="package">dovecot</span> package. When using a POP server, email messages are downloaded by email client applications. By default, most POP 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">
+ POP 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">
+ POP 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, POP 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 POP protocol is POP3.
+ </div><div class="para">
+ There are, however, a variety of lesser-used POP protocol variants:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>APOP</em></span> — POP3 with MDS 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 xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,pt-BR" class="listitem" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,pt-BR"><div class="para">
+ <span class="emphasis"><em>KPOP</em></span> — POP3 with Kerberos authentication.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>RPOP</em></span> — POP3 with RPOP authentication. This uses a per-user ID, similar to a password, to authenticate POP requests. However, this ID is not encrypted, so RPOP is no more secure than standard POP.
+ </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">ipop3s</code> service or by using the <code class="command">/usr/sbin/stunnel</code> program. Refer to <a class="xref" href="s1-email-mua.html#s2-email-security" title="13.6.1. Securing Communication">Section 13.6.1, “Securing Communication”</a> for more information.
+ </div></div><div class="section" title="13.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">13.1.2.2. IMAP</h4></div></div></div><a id="id758144" class="indexterm"></a><div class="para">
+ The default IMAP server under Fedora is <code class="command">/usr/bin/dovecot</code> and is provided by the <code class="filename">dovecot</code> package. When using an IMAP mail server, email messages remain on the server where users can read or delete them. IMAP also allows client applications to create, rename, or delete mail directories on the server to organize and store email.
+ </div><div class="para">
+ IMAP is particularly useful for those 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, IMAP client applications are capable of caching copies of messages locally, so the user can browse previously read messages when not directly connected to the IMAP server.
+ </div><div class="para">
+ IMAP, like POP, 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 <em class="firstterm">SSL</em> 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. Refer to <a class="xref" href="s1-email-mua.html#s2-email-security" title="13.6.1. Securing Communication">Section 13.6.1, “Securing Communication”</a> for more information.
+ </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. A comprehensive list can be found online at <a href="http://en.wikipedia.org/wiki/List_of_mail_servers">http://en.wikipedia.org/wiki/List_of_mail_servers</a>.
+ </div></div><div class="section" title="13.1.2.3. Dovecot" id="s3-email-protocols-dovecot"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-protocols-dovecot">13.1.2.3. Dovecot</h4></div></div></div><a id="id758231" class="indexterm"></a><div class="para">
+ The <code class="command">imap-login</code> and <code class="command">pop3-login</code> processes which implement the IMAP and POP3 protocols are spawned by the master <code class="command">dovecot</code> daemon included in the <span class="package">dovecot</span> package. The use of IMAP and POP is configured through <code class="filename">dovecot.conf</code>; by default <code class="command">dovecot</code> runs IMAP and POP3 together with their secure versions using SSL. To configure <code class="command">dovecot</code> to use POP:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Edit <code class="filename">/etc/dovecot/dovecot.conf</code> to make sure protocols variable contains pop3. For example:
+ </div><pre class="screen">protocols = imap imaps pop3 pop3s
+</pre></li><li class="listitem"><div class="para">
+ Make that change operational for the current session by running the command:
+ </div><pre class="screen">/sbin/service dovecot restart
+</pre></li><li class="listitem"><div class="para">
+ Make that change operational after the next reboot by running the command:
+ </div><pre class="screen">chkconfig dovecot on
+</pre><div class="para">
+ Please note that <code class="filename">dovecot</code> only reports that it started the IMAP server, but also starts the POP3 server.
+ </div></li></ol></div><div class="para">
+ Unlike SMTP, both of these protocols 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 SSL on dovecot:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Edit the <code class="filename">dovecot</code> configuration file <code class="filename">/etc/pki/dovecot/dovecot-openssl.conf</code> 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 dovecot self signed certificates. The 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="filename">dovecot</code> (<code class="command">/sbin/service dovecot restart</code>).
+ </div></li></ul></div>
+ More details on <code class="filename">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-ftp-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="s1-email-types.html"><strong>Next</strong>13.2. Email Program Classifications</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-intro.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-intro.html
new file mode 100644
index 0000000..c25ab9b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-intro.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="
left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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>Next</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="id752903" class="indexterm"></a><div class="para">
+ Welcome to the <em class="citetitle">Fedora Deployment Guide</em>.
+ </div><div class="para">
+ The Fedora Deployment Guide contains information on how to customize your Fedora 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">
+ Setting up a network interface card (NIC)
+ </div></li><li class="listitem"><div class="para">
+ Configuring a Virtual Private Network (VPN)
+ </div></li><li class="listitem"><div class="para">
+ Configuring Samba shares
+ </div></li><li class="listitem"><div class="para">
+ Managing your software with RPM
+ </div></li><li class="listitem"><div class="para">
+ Determining information about your system
+ </div></li><li class="listitem"><div class="para">
+ Upgrading your 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">
+ File systems
+ </div></li><li class="listitem"><div class="para">
+ Package management
+ </div></li><li class="listitem"><div class="para">
+ Network-related configuration
+ </div></li><li class="listitem"><div class="para">
+ System configuration
+ </div></li><li class="listitem"><div class="para">
+ System monitoring
+ </div></li><li class="listitem"><div class="para">
+ Kernel and Driver Configuration
+ </div></li><li class="listitem"><div class="para">
+ Security and Authentication
+ </div></li><li class="listitem"><div class="para">
+ Red Hat Training and Certification
+ </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 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_Draft_Documentation/0.1/html/Deployment_Guide/ch-proc.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-proc.html
new file mode 100644
index 0000000..dc6762d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-proc.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>Chapter 17. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-access-floppy.html" title="16.6. The floppy Group" /><link rel="next" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your bro
wser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-access-floppy.html"><strong>Prev</strong></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 17. The proc File System" id="ch-proc" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 17. 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">17.1. A Virtual File System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-proc.html#s2-proc-viewing">17.1.1
. Viewing Virtual Files</a></span></dt><dt><span class="section"><a href="ch-proc.html#s2-proc-change">17.1.2. Changing Virtual Files</a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-topfiles.html">17.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="s1-proc-topfiles.html#s2-proc-buddyinfo">17.2.1. <code class="filename">/proc/buddyinfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-cmdline.html">17.2.2. <code class="filename">/proc/cmdline</code> </a></span></dt><dt><span class="section"><a href="s2-proc-cpuinfo.html">17.2.3. <code class="filename">/proc/cpuinfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-crypto.html">17.2.4. <code class="filename">/proc/crypto</code> </a></span></dt><dt><span class="section"><a href="s2-proc-devices.html">17.2.5. <code class="filename">/proc/devices</code> </a></span></dt><dt><span class="sec
tion"><a href="s2-proc-dma.html">17.2.6. <code class="filename">/proc/dma</code> </a></span></dt><dt><span class="section"><a href="s2-proc-execdomains.html">17.2.7. <code class="filename">/proc/execdomains</code> </a></span></dt><dt><span class="section"><a href="s2-proc-fb.html">17.2.8. <code class="filename">/proc/fb</code> </a></span></dt><dt><span class="section"><a href="s2-proc-filesystems.html">17.2.9. <code class="filename">/proc/filesystems</code> </a></span></dt><dt><span class="section"><a href="s2-proc-interrupts.html">17.2.10. <code class="filename">/proc/interrupts</code> </a></span></dt><dt><span class="section"><a href="s2-proc-iomem.html">17.2.11. <code class="filename">/proc/iomem</code> </a></span></dt><dt><span class="section"><a href="s2-proc-ioports.html">17.2.12. <code class="filename">/proc/ioports</code> </a></span></dt><dt><span class="section"><a href="s2-proc-kcore.html">17.2.13. <code class="filename">/proc/kcore</code> </a></span></dt><
dt><span class="section"><a href="s2-proc-kmsg.html">17.2.14. <code class="filename">/proc/kmsg</code> </a></span></dt><dt><span class="section"><a href="s2-proc-loadavg.html">17.2.15. <code class="filename">/proc/loadavg</code> </a></span></dt><dt><span class="section"><a href="s2-proc-locks.html">17.2.16. <code class="filename">/proc/locks</code> </a></span></dt><dt><span class="section"><a href="s2-proc-mdstat.html">17.2.17. <code class="filename">/proc/mdstat</code> </a></span></dt><dt><span class="section"><a href="s2-proc-meminfo.html">17.2.18. <code class="filename">/proc/meminfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-misc.html">17.2.19. <code class="filename">/proc/misc</code> </a></span></dt><dt><span class="section"><a href="s2-proc-modules.html">17.2.20. <code class="filename">/proc/modules</code> </a></span></dt><dt><span class="section"><a href="s2-proc-mounts.html">17.2.21. <code class="filename">/proc/mounts</code> </a></span
></dt><dt><span class="section"><a href="s2-proc-mtrr.html">17.2.22. <code class="filename">/proc/mtrr</code> </a></span></dt><dt><span class="section"><a href="s2-proc-partitions.html">17.2.23. <code class="filename">/proc/partitions</code> </a></span></dt><dt><span class="section"><a href="s2-proc-pci.html">17.2.24. <code class="filename">/proc/pci</code> </a></span></dt><dt><span class="section"><a href="s2-proc-slabinfo.html">17.2.25. <code class="filename">/proc/slabinfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-stat.html">17.2.26. <code class="filename">/proc/stat</code> </a></span></dt><dt><span class="section"><a href="s2-proc-swaps.html">17.2.27. <code class="filename">/proc/swaps</code> </a></span></dt><dt><span class="section"><a href="s2-proc-sysrq-trigger.html">17.2.28. <code class="filename">/proc/sysrq-trigger</code> </a></span></dt><dt><span class="section"><a href="s2-proc-uptime.html">17.2.29. <code class="filename">/proc/upt
ime</code> </a></span></dt><dt><span class="section"><a href="s2-proc-version.html">17.2.30. <code class="filename">/proc/version</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-directories.html">17.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-proc-directories.html#s2-proc-processdirs">17.3.1. Process Directories</a></span></dt><dt><span class="section"><a href="s2-proc-dir-bus.html">17.3.2. <code class="filename">/proc/bus/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-driver.html">17.3.3. <code class="filename">/proc/driver/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-fs.html">17.3.4. <code class="filename">/proc/fs</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-irq.html">17.3.5. <code class="filename">/proc/irq/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-net.html">17
.3.6. <code class="filename">/proc/net/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-scsi.html">17.3.7. <code class="filename">/proc/scsi/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-sys.html">17.3.8. <code class="filename">/proc/sys/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-sysvipc.html">17.3.9. <code class="filename">/proc/sysvipc/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-tty.html">17.3.10. <code class="filename">/proc/tty/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-pid.html">17.3.11. <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-sysctl.html">17.4. Using the <code class="command">sysctl</code> Command</a></span></dt><dt><span class="section"><a href="s1-proc-additional-resources.html">17.5. References</a></span></dt></dl></div><a id="id5
86673" class="indexterm"></a><a id="id715388" 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"><h2>Note</h2><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> 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 class="section" title="17.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">17.1. A Virtual File System</h2></div></div></div><a id="id745434" class="indexterm"></a><a id="id965582" class="indexterm"></a><a id="id678643" 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="17.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">17.1.1. Viewing Virtual Files</h3></div></div></div><a id="id787364" class="indexterm"></a><a id="id617915" 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"><h2>Note</h2><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 class="section" title="17.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">17.1.2. Changing Virtual Files</h3></div></div></div><a id="id618015" class="indexterm"></a><a id="id985140" 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"><h2>Tip</h2><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="17.4. Using the sysctl Command">Section 17.4, “Using the <code class="command">sysctl</code> Command”</a>
+ </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="17.3.8. /proc/sys/">Section 17.3.8, “ <code class="filename">/proc/sys/</code> ”</a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-access-floppy.html"><strong>Prev</strong>16.6. The floppy Group</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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>17.2. Top-level Files within the proc File System</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-yum.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-yum.html
new file mode 100644
index 0000000..d8e7679
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch-yum.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enabl
e iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">1.1.1. Checking For Updates<
/a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">1.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Security-Related_Packages">1.1.3. Updating Security-Related Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">1.1.4. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">1.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">1.2.1. Searching, Listing and Displaying Package Information</a></span></dt><dt><span class="section"><a href="sec-Installing.html">1.2.2. Installing</a></span></dt><dt><span class="section"><a href="sec-Removing.html">1.2.3. Removing</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Co
nfiguring_Yum_and_Yum_Repositories.html">1.3. Configuring Yum and Yum Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">1.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="sec-Setting_repository_Options.html">1.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="sec-Using_Yum_Variables.html">1.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">1.3.4. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">1.4. Yum Plugins</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">1.4.1. Enabling, Configuring and Disabling Yum Plugins</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">1.4.2. Installing More Y
um Plugins</a></span></dt><dt><span class="section"><a href="sec-Plugin_Descriptions.html">1.4.3. Plugin Descriptions</a></span></dt></dl></dd><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"><h2>Secure Package Management with GPG-Signed Packages</h2><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 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="id934260" 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"><h2>Note: <span class="application"><strong>Yum</strong></span> and Superuser Privileges</h2><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><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="id752430" 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="id752448" 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"><h2>Important: Updating and Installing Kernels with Yum</h2><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></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="id998365" 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"><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum update</code>
+</pre></div><h6>Example 1.1. Updating all packages at once</h6></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="id859246" class="indexterm"></a><a id="id859258" 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="id859277" 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="id761283" 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_Draft_Documentation/0.1/html/Deployment_Guide/ch10s02s03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch10s02s03.html
new file mode 100644
index 0000000..9f73096
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch10s02s03.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>10.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-dhcp-configuring-server.html" title="10.2. Configuring a DHCP Server" /><link rel="prev" href="lease-database.html" title="10.2.2. Lease Database" /><link rel="next" href="dhcp-relay-agent.html" title="10.2.4. DHCP Relay Agent" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser o
r enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="10.2.3. Starting and Stopping the Server"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id555772">10.2.3. Starting and Stopping the Server</h3></div></div></div><a id="id555779" class="indexterm"></a><a id="id555792" class="indexterm"></a><a id="id555806" class="indexterm"></a><a id="id751232" class="indexterm"></a><div class="important"><h2>Important</h2><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 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 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a>.
+ </div><a id="id751294" class="indexterm"></a><a id="id751308" 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="10.2.4. DHCP Relay Agent">Section 10.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>10.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>10.2.4. DHCP Relay Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch23s07s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch23s07s02.html
new file mode 100644
index 0000000..a749be0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch23s07s02.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.7.2. The Policies Tab</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-printing-edit.html" title="23.7. Modifying Existing Printers" /><link rel="prev" href="s1-printing-edit.html" title="23.7. Modifying Existing Printers" /><link rel="next" href="ch23s07s03.html" title="23.7.3. The Access Control Tab" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable if
rame display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-printing-edit.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch23s07s03.html"><strong>Next</strong></a></li></ul><div class="section" title="23.7.2. The Policies Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id969482">23.7.2. The <span class="guilabel"><strong>Policies</strong></span> Tab</h3></div></div></div><div class="para">
+ To change settings in print output, click the <span class="guilabel"><strong>Policies</strong></span> tab.
+ </div><div class="para">
+ For example, to create a <em class="firstterm">banner page</em> (a page that describes aspects of the print job such as the originating printer, the username from the which the job originated, and the security status of the document being printed) click the <span class="guilabel"><strong>Starting Banner </strong></span> or <span class="guilabel"><strong>Ending Banner</strong></span> drop-menu and choose the option that best describes the nature of the print jobs (such as <span class="guilabel"><strong>topsecret</strong></span>, <span class="guilabel"><strong>classified</strong></span>, or <span class="guilabel"><strong>confidential</strong></span>).
+ </div><div class="figure" title="Figure 23.9. Policies Tab" id="fig-printconf-config2"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config2.png" width="444" alt="Policies Tab" /><div class="longdesc"><div class="para">
+ Policies Tab
+ </div></div></div></div><h6>Figure 23.9. Policies Tab</h6></div><br class="figure-break" /><div class="para">
+ You can also configure the <span class="guilabel"><strong>Error Policy</strong></span> of the printer, by choosing an option from the drop-down menu. You can choose to abort the print job, retry, or stop it.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-edit.html"><strong>Prev</strong>23.7. Modifying Existing Printers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch23s07s03.html"><strong>Next</strong>23.7.3. The Access Control Tab</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch23s07s03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch23s07s03.html
new file mode 100644
index 0000000..0d37e95
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch23s07s03.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.7.3. The Access Control Tab</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-printing-edit.html" title="23.7. Modifying Existing Printers" /><link rel="prev" href="ch23s07s02.html" title="23.7.2. The Policies Tab" /><link rel="next" href="ch23s07s04.html" title="23.7.4. The Printer and Job OptionsTab" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifr
ame display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch23s07s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch23s07s04.html"><strong>Next</strong></a></li></ul><div class="section" title="23.7.3. The Access Control Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id691095">23.7.3. The <span class="guilabel"><strong>Access Control</strong></span> Tab</h3></div></div></div><div class="para">
+ You can change user-level access to the configured printer by clicking the <span class="guilabel"><strong>Access Control</strong></span> tab.
+ </div><div class="para">
+ Add users using the text box and click the <span class="guibutton"><strong>Add</strong></span> button beside it. You can then choose to only allow use of the printer to that subset of users or deny use to those users.
+ </div><div class="figure" title="Figure 23.10. Access Control Tab" id="fig-printconf-config3"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config3.png" width="444" alt="Access Control Tab" /><div class="longdesc"><div class="para">
+ Access Control Tab
+ </div></div></div></div><h6>Figure 23.10. Access Control Tab</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch23s07s02.html"><strong>Prev</strong>23.7.2. The Policies Tab</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch23s07s04.html"><strong>Next</strong>23.7.4. The Printer and Job OptionsTab</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch23s07s04.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch23s07s04.html
new file mode 100644
index 0000000..81d8d4c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch23s07s04.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.7.4. The Printer and Job OptionsTab</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-printing-edit.html" title="23.7. Modifying Existing Printers" /><link rel="prev" href="ch23s07s03.html" title="23.7.3. The Access Control Tab" /><link rel="next" href="s1-printing-managing.html" title="23.8. Managing Print Jobs" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or
enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch23s07s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-managing.html"><strong>Next</strong></a></li></ul><div class="section" title="23.7.4. The Printer and Job OptionsTab"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id691165">23.7.4. The <span class="guilabel"><strong>Printer</strong></span> and <span class="guilabel"><strong>Job Options</strong></span>Tab</h3></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Printer Options</strong></span> tab contains various configuration options for the printer media and output.
+ </div><div class="figure" title="Figure 23.11. Printer Options Tab" id="fig-printconf-config4"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config4.png" width="444" alt="Printer Options Tab" /><div class="longdesc"><div class="para">
+ Printer Jobs Tab
+ </div></div></div></div><h6>Figure 23.11. Printer Options Tab</h6></div><br class="figure-break" /><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Page Size</strong></span> — Allows the paper size to be selected. The options include US Letter, US Legal, A3, and A4
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Media Source</strong></span> — set to <span class="guilabel"><strong>Automatic</strong></span> by default. Change this option to use paper from a different tray.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Media Type</strong></span> — Allows you to change paper type. Options include: Plain, thick, bond, and transparency.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Resolution</strong></span> — Configure the quality and detail of the printout. Default is 300 dots per inch (dpi).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Toner Saving</strong></span> — Choose whether the printer uses less toner to conserve resources.
+ </div></li></ul></div><div class="para">
+ You can also configure printer job options using the <span class="guilabel"><strong>Job Options</strong></span> tab. Use the drop-menu and choose the job options you wish to use, such as <span class="guilabel"><strong>Landscape</strong></span> modes (horizontal or vertical printout), <span class="guilabel"><strong>copies</strong></span>, or <span class="guilabel"><strong>scaling</strong></span> (increase or decrease the size of the printable area, which can be used to fit an oversize print area onto a smaller physical sheet of print medium).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch23s07s03.html"><strong>Prev</strong>23.7.3. The Access Control Tab</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-printing-managing.html"><strong>Next</strong>23.8. Managing Print Jobs</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s02.html
new file mode 100644
index 0000000..18ce4a6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s02.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>28.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-abrt.html" title="Chapter 28. ABRT" /><link rel="prev" href="ch-abrt.html" title="Chapter 28. ABRT" /><link rel="next" href="configuring.html" title="28.3. Configuring ABRT" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a cla
ss="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="configuring.html"><strong>Next</strong></a></li></ul><div class="section" title="28.2. Installing and Running ABRT"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id858262">28.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> is running in the Notification Area of your desktop session. You can ensure that <span class="application"><strong>ABRT</strong></span> is installed by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install abrt-desktop</code>
+</pre><div class="para">
+ <span class="application"><strong>ABRT</strong></span> is typically configured to start up at boot time. You can ensure that the <code class="systemitem">abrtd</code> daemon is running by issuing the command:
+ </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> daemon 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 <code class="command">chkconfig abrtd on</code> command as root.
+ </div><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>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 <code class="command">abrt-applet</code> detects a crash, it displays a red alarm icon in the Notifcation 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 window 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 28. 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="configuring.html"><strong>Next</strong>28.3. Configuring ABRT</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s04.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s04.html
new file mode 100644
index 0000000..650000c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s04.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>28.4. Plugins and Sending Crash Reports</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-abrt.html" title="Chapter 28. ABRT" /><link rel="prev" href="configuring.html" title="28.3. Configuring ABRT" /><link rel="next" href="ch28s05.html" title="28.5. Using the Command Line Interface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe
></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="ch28s05.html"><strong>Next</strong></a></li></ul><div class="section" title="28.4. Plugins and Sending Crash Reports"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id647991">28.4. Plugins and Sending Crash Reports</h2></div></div></div><div class="para">
+ The <code class="literal">[AnalyzerActionsAndReporters]</code> section in <code class="filename">abrt.conf</code> specifies which plugins are to be used to report crash data. As of version 1.0.0, the default <code class="filename">abrt.conf</code> contains:
+ </div><pre class="screen">[ AnalyzerActionsAndReporters ]
+ Kerneloops = KerneloopsReporter
+ CCpp = Bugzilla, Logger
+ Python = Bugzilla, Logger</pre><div class="para">
+ These lines indicate that kernel oopses are to be reported to the <a href="kerneloops.org">kerneloops.org</a> site, and that both binary crashes and python crashes are to be reported to Bugzilla and to a local text file. Each of these destinations' details can be specified in the corresponding <code class="filename">plugins/*.conf</code> file. For example, <code class="filename">plugins/Bugzilla.conf</code> specifies which Bugzilla URL to use (set to <a href="https://bugzilla.redhat.com/">https://bugzilla.redhat.com/</a> by default), the user's login name, password for logging in to the Bugzilla site, etc.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="configuring.html"><strong>Prev</strong>28.3. 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="ch28s05.html"><strong>Next</strong>28.5. Using the Command Line Interface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s05.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s05.html
new file mode 100644
index 0000000..7ebae60
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s05.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>28.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-abrt.html" title="Chapter 28. ABRT" /><link rel="prev" href="ch28s04.html" title="28.4. Plugins and Sending Crash Reports" /><link rel="next" href="ch28s05s02.html" title="28.5.2. Reporting Crashes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</ifra
me></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch28s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch28s05s02.html"><strong>Next</strong></a></li></ul><div class="section" title="28.5. Using the Command Line Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id648040">28.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="28.5.1. Viewing Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id648054">28.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 --get-list</code>:
+ </div><pre class="screen">
+~]# <code class="command">abrt-cli --get-list</code>
+0.
+ UID : 501
+ UUID : d074c2882400b3ff245415e676ed53f22bb8e7b5
+ Package : gnome-packagekit-2.28.2-0.1.20091030git.fc12
+ Executable : /usr/bin/gpk-application
+ Crash Time : Wed 18 Nov 2009 12:07:40 PM CET
+ Crash Count: 2
+1.
+ UID : 501
+ UUID : 52d0d2f64f0b07fb0e626ecdfa4ac4faadc38258
+ Package : gnome-commander-1.3-0.3.git_D20090929T1100_13dev.fc12
+ Executable : /usr/libexec/gnome-commander/gnome-commander
+ Crash Time : Wed 18 Nov 2009 04:58:46 PM CET
+ 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. It is useful when <code class="command">abrt-cli</code> is executed with superuser privileges and it lists crashes from all users. 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="ch28s04.html"><strong>Prev</strong>28.4. Plugins and Sending Crash Reports</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch28s05s02.html"><strong>Next</strong>28.5.2. Reporting Crashes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s05s02.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s05s02.html
new file mode 100644
index 0000000..6cb2350
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s05s02.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>28.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch28s05.html" title="28.5. Using the Command Line Interface" /><link rel="prev" href="ch28s05.html" title="28.5. Using the Command Line Interface" /><link rel="next" href="ch28s05s03.html" title="28.5.3. Deleting Crashes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.
</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch28s05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch28s05s03.html"><strong>Next</strong></a></li></ul><div class="section" title="28.5.2. Reporting Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id648104">28.5.2. Reporting Crashes</h3></div></div></div><div class="para">
+ To report certain crash, you enter <code class="command">abrt-cli --report <UUID></code>, where <code class="varname">UUID</code> is a field from <code class="command">abrt-cli --get-list</code>. You do not need to remember the exact <code class="varname">UUID</code>; either use a mouse to copy and paste it, or use bash completion (write first few characters of the <code class="varname">UUID</code> and press <span class="keycap"><strong><TAB></strong></span>).
+ </div><pre class="screen">
+~]# <code class="command">abrt-cli --report 52d</code>
+ <span class="keycap"><strong><TAB></strong></span>
+~]# <code class="command">abrt-cli --report 52d0d2f64f0b07fb0e626ecdfa4ac4faadc38258</code>
+>> 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"><h2>Preferred Text Editor</h2><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 class="para">
+ When you are done with the report, save your changes and close the editor. You will be asked if you want to send the report. Respond <span class="keycap"><strong>Y</strong></span> to send the report or <span class="keycap"><strong>N</strong></span> to cancel it.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch28s05.html"><strong>Prev</strong>28.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="ch28s05s03.html"><strong>Next</strong>28.5.3. Deleting Crashes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s05s03.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s05s03.html
new file mode 100644
index 0000000..8ce465c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ch28s05s03.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch28s05.html" title="28.5. Using the Command Line Interface" /><link rel="prev" href="ch28s05s02.html" title="28.5.2. Reporting Crashes" /><link rel="next" href="pt-kernel-configuration.html" title="Part V. Kernel and Driver Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enab
le iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch28s05s02.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="28.5.3. Deleting Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1004481">28.5.3. Deleting Crashes</h3></div></div></div><div class="para">
+ If you know that you do not want to report a certain crash, you can delete it from the crash list. To delete a certain crash, enter the command: <code class="command">abrt-cli --delete <em class="replaceable"><code><UUID></code></em> </code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch28s05s02.html"><strong>Prev</strong>28.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="pt-kernel-configuration.html"><strong>Next</strong>Part V. Kernel and Driver Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-Date_and_Time_Configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-Date_and_Time_Configuration.html
new file mode 100644
index 0000000..60cbdee
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-Date_and_Time_Configuration.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>Chapter 19. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="sect-Date_and_Time_Configuration-Command_Line_Configuration.html" title="19.2. Command Line Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../to
c.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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</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 19. Date and Time Configuration" id="chap-Date_and_Time_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. Date and Time Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Date_and_Time_Configurat
ion.html#sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool">19.1. Date/Time Properties Tool</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">19.1.1. Date and Time Properties</a></span></dt><dt><span class="section"><a href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Network_Time_Protocol">19.1.2. Network Time Protocol Properties</a></span></dt><dt><span class="section"><a href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Time_Zone">19.1.3. Time Zone Properties</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html">19.2. Command Line Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">19.2
.1. Date and Time Setup</a></span></dt><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">19.2.2. Network Time Protocol Setup</a></span></dt></dl></dd></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="19.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">19.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> (see <a class="xref" href="ch-The_X_Window_System.html" title="Chapter 21. The X Window System">Chapter 21, <i>The X Window System</i></a> for more information on this topic).
+ </div><a id="id929738" 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 19.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 19.1. Authentication Query</h6></div><br class="figure-break" /><div class="section" title="19.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">19.1.1. Date and Time Properties</h3></div></div></div><a id="id728699" class="indexterm"></a><a id="id663739" 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 19.2. Date and Time Properties">Figure 19.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 19.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 19.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="19.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">19.1.2. Network Time Protocol Properties</h3></div></div></div><a id="id655183" class="indexterm"></a><a id="id655196" class="indexterm"></a><a id="id855455" class="indexterm"></a><a id="id855469" class="indexterm"></a><a id="id855486" 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 19.3. Network Time Protocol Properties">Figure 19.3, “Network Time Protocol Properties”</a>.
+ </div><div class="figure" title="Figure 19.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 19.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"><h2>Note</h2><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 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="19.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">19.1.3. Time Zone Properties</h3></div></div></div><a id="id788153" 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 19.4. Time Zone Properties">Figure 19.4, “Time Zone Properties”</a>.
+ </div><div class="figure" title="Figure 19.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 19.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="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="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"><strong>Next</strong>19.2. Command Line Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Domains.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Domains.html
new file mode 100644
index 0000000..1c608f8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Domains.html
@@ -0,0 +1,229 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="15.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Configuring_Services.html" title="15.2.4. Configuring Services" /><link rel="next" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html" title="15.2.6. Setting up Kerberos Authentication" /></head><body class="draft toc_embeded "><div id="tocdiv" clas
s="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_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="15.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">15.2.5. Configu
ring 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="15.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="15.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="15.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">15.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="15.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">15.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="important"><h2>Important</h2><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></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"><h2>Note</h2><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></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"><h2>Note</h2><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="15.2.5.4. Configuring a Proxy Domain">Section 15.2.5.4, “Configuring a Proxy Domain”</a> for information on this attribute.
+ </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"><h2>Note</h2><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></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="15.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">15.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="15.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">15.2.5.2. Configuring an LDAP Domain</h4></div></div></div><a id="id661357" 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. 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_user_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="id642639" 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 by default 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="id650569" 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"><h2>Note</h2><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></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 class="formalpara"><h5 class="formalpara" id="id1999113">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 a native <acronym class="acronym">LDAP</acronym> domain.
+ </div></div><div class="section" title="15.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">15.2.5.3. Configuring a Microsoft Active Directory Domain</h4></div></div></div><a id="id919355" 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 on the Active Directory machine. This requirement does not apply to Active Directory 2008.
+ </div><div class="section" title="15.2.5.3.1. Configuring Active Directory 2003 as an LDAP Back End"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id1017165">15.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 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_user_search_base = cn=users,dc=example,dc=com
+ldap_group_search_base = cn=users,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></div><div class="section" title="15.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">15.2.5.4. Configuring a Proxy Domain</h4></div></div></div><a id="id642547" 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></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>15.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>15.2.6. Setting up Kerberos Authentication</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Services.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Services.html
new file mode 100644
index 0000000..cd7f0f6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Services.html
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="15.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html" title="15.2.3. Setting Up SSSD" /><link rel="next" href="chap-SSSD_User_Guide-Configuring_Domains.html" title="15.2.5. Configuring Domains" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../
toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="15.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">15.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">nss_sss</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">pam_sss</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="15.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">15.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="15.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">15.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"><h2>Note</h2><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></li></ul></div></div><div class="section" title="15.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">15.2.4.1.2. NSS Configuration Options</h5></div></div></div><div class="para">
+ Use the following options to configure the Name Service Switch (NSS) 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">nss_sss</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">nss_sss</span> should return cached entries before initiating an out-of-band cache refresh (0 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 0-99 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">nss_sss</span> should cache negative cache hits (that is, queries for invalid database entries, like 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 TRUE, 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 FALSE, 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="15.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">15.2.4.1.3. PAM Configuration Options</h5></div></div></div><div class="para">
+ Use these options to configure the <code class="systemitem module">Pluggable Authentication Module</code> (<acronym class="acronym">PAM</acronym>) 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 we should allow cached log ins (in days). If not specified, defaults to <code class="literal">0</code> (no limit).
+ </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>15.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>15.2.5. Configuring Domains</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Introduction.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Introduction.html
new file mode 100644
index 0000000..71fde6c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Introduction.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Authentication_Configuration.html" title="Chapter 15. Authentication Configuration" /><link rel="prev" href="ch-Authentication_Configuration.html" title="Chapter 15. Authentication Configuration" /><link rel="next" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html" title="15.2.2. SSSD Features" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" clas
s="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Authentication_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="15.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">15.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="15.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">15.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.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Authentication_Configuration.html"><strong>Prev</strong>Chapter 15. 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>15.2.2. SSSD Features</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html
new file mode 100644
index 0000000..8a99384
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html
@@ -0,0 +1,145 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="15.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html" title="15.2.2. SSSD Features" /><link rel="next" href="chap-SSSD_User_Guide-Configuring_Services.html" title="15.2.4. Configuring Services" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../
../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="15.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">15.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="15.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">15.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="15.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">15.2.3.1.1. Upgrading from a Previous Version</h5></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="15.2.8. SSSD Configuration File Format">Section 15.2.8, “SSSD Configuration File Format”</a>
+ </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="15.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">15.2.3.1.2. Starting and Stopping SSSD</h5></div></div></div><div class="note"><h2>Note</h2><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="15.2.5. Configuring Domains">Section 15.2.5, “Configuring Domains”</a> for information on how to configure an SSSD domain.
+ </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. You can use the <code class="command">chkconfig</code> command to change this behavior. For example, run the following command to configure SSSD to start when the machine boots:
+ </div><div class="para">
+ <code class="command"># chkconfig sssd on</code>
+ </div></div></div><div class="section" title="15.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">15.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"><h2>Note</h2><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 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="15.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">15.2.3.2.1. Configuring NSS</h5></div></div></div><div class="para">
+ SSSD provides a new NSS module, <code class="systemitem">nss_sss</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="15.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">15.2.3.2.2. Configuring PAM</h5></div></div></div><div class="warning"><h2>Warning</h2><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 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="formalpara" id="form-SSSD_User_Guide-Configuring_PAM-Using_include_Statements_in_PAM_Configurations"><h5 class="formalpara">Using include Statements in PAM Configurations</h5>
+ 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"><h2>Note</h2><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 class="section" title="15.2.3.2.3. Configuring Access Control"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id603215">15.2.3.2.3. Configuring Access Control</h5></div></div></div><a id="id940478" class="indexterm"></a><div class="para">
+ SSSD provides a rudimentary access control mechanism based on the implementation of access or deny lists of usernames. This mechanism is known as the <em class="firstterm">Simple Access Provider</em>, and is configured 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. 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="id974875">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="formalpara"><h5 class="formalpara" id="id603553">Access Control Rules</h5><a id="id923048" 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"><h2>Important</h2><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 when loading the back end and will fail to start.
+ </div></div>
+
+ </div></div><div class="section" title="15.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">15.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="15.2.3.2.4.1. Using SRV Records with Failover">Section 15.2.3.2.4.1, “Using SRV Records with Failover”</a> for more information on service discovery.
+ </div><div class="important"><h2>Important</h2><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 class="section" title="15.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">15.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="15.2.3.2.4.2. How the Failover Mechanism Works"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="id824220">15.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">
+ 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>15.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>15.2.4. Configuring Services</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Troubleshooting.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Troubleshooting.html
new file mode 100644
index 0000000..1157556
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/chap-SSSD_User_Guide-Troubleshooting.html
@@ -0,0 +1,105 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="15.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html" title="15.2.6. Setting up Kerberos Authentication" /><link rel="next" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html" title="15.2.8. SSSD Configuration File Format" /></head><body
class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-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="15.2.7. Troubleshooting" id="chap-SSSD_User_Guide-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="alwa
ys"><h3 class="title" id="chap-SSSD_User_Guide-Troubleshooting">15.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="15.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">15.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="15.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">15.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"><h2>Important</h2><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></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="15.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">15.2.7.3. Problems with SSSD Service Configuration</h4></div></div></div><div class="section" title="15.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">15.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="15.2.3.2.1. Configuring NSS">Section 15.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="15.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">15.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="15.2.3.2.2. Configuring PAM">Section 15.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><div class="section" title="15.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">15.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="15.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">15.2.7.5. Additional Resources</h4></div></div></div><div class="section" title="15.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">15.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="15.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">15.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>15.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>15.2.8. SSSD Configuration File Format</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/configuring.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/configuring.html
new file mode 100644
index 0000000..20376a6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/configuring.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>28.3. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-abrt.html" title="Chapter 28. ABRT" /><link rel="prev" href="ch28s02.html" title="28.2. Installing and Running ABRT" /><link rel="next" href="ch28s04.html" title="28.4. Plugins and Sending Crash Reports" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch28s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch28s04.html"><strong>Next</strong></a></li></ul><div class="section" title="28.3. Configuring ABRT" id="configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="configuring">28.3. 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><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><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 listed after the <em class="parameter"><code>BlackList</code></em> option 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, list them here separated by commas.
+ </div></dd><dt><span class="term">Database = SQLite3</span></dt><dd><div class="para">
+ This option 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><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 no longer catch and save program crash information.
+ </div></dd><dt><span class="term">ActionsAndReporters = SOSreport</span></dt><dd><div class="para">
+ This option tells <span class="application"><strong>ABRT</strong></span> to run the <code class="command">sosreport</code> command immediately after an application crash. 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> 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> after C and C++ or Python application crashes, respectively.
+ </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 order of actions and reporters is important.
+ </div><dl><dt><span class="term">Kerneloops = TicketUploader, Bugzilla</span></dt><dd><div class="para">
+ This directive specifies that, for kernel oopses, the TicketUploader and Bugzilla reporters should run.
+ </div></dd><dt><span class="term">CCpp = TicketUploader, Bugzilla</span></dt><dd><div class="para">
+ This directive specifies that, when C or C++program crashes occur, both the TicketUploader and Bugzilla reporters should run.
+ </div></dd><dt><span class="term">Python = TicketUploader, Bugzilla</span></dt><dd><div class="para">
+ This directive specifies that, when C or C++program crashes occur, both the TicketUploader and Bugzilla reporters should run.
+ </div></dd></dl></div><div class="variablelist" title="[ Cron ] Section Directives"><h6>[ Cron ] Section Directives</h6><dl><dt><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 28.1. [ Cron ] section of /etc/abrt/abrt.conf" id="ex-_Cron__section_of__etc_abrt_abrt.conf"><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><h6>Example 28.1. [ Cron ] section of /etc/abrt/abrt.conf</h6></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="ch28s02.html"><strong>Prev</strong>28.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="ch28s04.html"><strong>Next</strong>28.4. Plugins and Sending Crash Reports</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/dhcp-relay-agent.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/dhcp-relay-agent.html
new file mode 100644
index 0000000..b2b3bbb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/dhcp-relay-agent.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-dhcp-configuring-server.html" title="10.2. Configuring a DHCP Server" /><link rel="prev" href="ch10s02s03.html" title="10.2.3. Starting and Stopping the Server" /><link rel="next" href="s1-dhcp-configuring-client.html" title="10.3. Configuring a DHCP Client" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade
your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch10s02s03.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="10.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">10.2.4. DHCP Relay Agent</h3></div></div></div><a id="id986758" class="indexterm"></a><a id="id986772" class="indexterm"></a><a id="id986786" 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="ch10s02s03.html"><strong>Prev</strong>10.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>10.3. Configuring a DHCP Client</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ers_and_Groups.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ers_and_Groups.html
new file mode 100644
index 0000000..1d23543
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ers_and_Groups.html
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-x-useful-websites.html" title="21.6.2. Useful Websites" /><link rel="next" href="s1-users-tools.html" title="22.2. User and Group Management Tools" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enabl
e iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-useful-websites.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 22. Users and Groups" id="ers_and_Groups" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 22. Users and Groups</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ers_and_Groups.html#s1-users-configui">22.1. User and Group Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ers_and_Groups.html#s2-redhat-config-users-user-new">22.1.1. A
dding a New User</a></span></dt><dt><span class="section"><a href="ers_and_Groups.html#s2-redhat-config-users-group-new">22.1.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="ers_and_Groups.html#s2-redhat-config-users-group-properties">22.1.3. Modifying Group Properties</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html">22.2. User and Group Management Tools</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-cmd-line">22.2.1. Command Line Configuration</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-process.html">22.2.2. Explaining the Process</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-standard-users.html">22.3. Standard Users</a></span></dt><dt><span class="section"><a href="s1-users-groups-standard-groups.html">22.4. Standard Groups</a></span></dt><dt><span class="section"><a href="s1-users-groups-private-groups.html">22.5. User
Private Groups</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-groups-private-groups.html#s2-users-groups-rationale">22.5.1. Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-shadow-utilities.html">22.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="s1-users-groups-additional-resources.html">22.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">22.7.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="id953265" class="indexterm"></a><a id="id606308" class="indexterm"></a><a id="id581074" class="indexterm"></a><a id="id726727" 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. For more information about ACLs, refer to chapter<em class="citetitle">ACLS</em>.
+ </div><div class="section" title="22.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">22.1. User and Group Configuration</h2></div></div></div><a id="id751671" class="indexterm"></a><a id="id617867" class="indexterm"></a><a id="id617881" class="indexterm"></a><a id="id670407" class="indexterm"></a><a id="id670421" class="indexterm"></a><a id="id670434" 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 22.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 22.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="id603476" class="indexterm"></a><a id="id603490" 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="22.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">22.1.1. Adding a New User</h3></div></div></div><a id="id741355" 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="ers_and_Groups.html#user-new-fig" title="Figure 22.2. Creating a new user">Figure 22.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"><h2>Tip</h2><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 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 22.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 22.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>Modifying User Properties</h4><a id="id860046" class="indexterm"></a><a id="id860060" 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="ers_and_Groups.html#user-properties-fig" title="Figure 22.3. User Properties">Figure 22.3, “User Properties”</a> appears.
+ </div><div class="figure" title="Figure 22.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 22.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="id758278" class="indexterm"></a><a id="id758292" class="indexterm"></a><a id="id758305" class="indexterm"></a><a id="id758319" 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="22.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">22.1.2. Adding a New Group</h3></div></div></div><a id="id758413" 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="ers_and_Groups.html#group-new-fig" title="Figure 22.4. New Group">Figure 22.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 22.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 22.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="22.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">22.1.3. Modifying Group Properties</h3></div></div></div><a id="id598539" 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="ers_and_Groups.html#group-properties-fig" title="Figure 22.5. Group Properties">Figure 22.5, “Group Properties”</a> appears.
+ </div><div class="figure" title="Figure 22.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 22.5. Group Properties</h6></div><br class="figure-break" /><a id="id598605" 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="s2-x-useful-websites.html"><strong>Prev</strong>21.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="s1-users-tools.html"><strong>Next</strong>22.2. User and Group Management Tools</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/ABRT-Main_Window.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/ABRT-Main_Window.png
new file mode 100644
index 0000000..4e5b8b9
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/ABRT-Main_Window.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png
new file mode 100644
index 0000000..f737aff
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Authentication_Configuration-authconfig-Authentication.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Authentication_Configuration-authconfig-Authentication.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Authentication_Configuration-authconfig-Options.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Authentication_Configuration-authconfig-Options.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Authentication_Configuration-authconfig-SSSD_Settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Authentication_Configuration-authconfig-SSSD_Settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Authentication_Configuration-authconfig-User_Information.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Authentication_Configuration-authconfig-User_Information.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Change_Runtime_Boolean.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Change_Runtime_Boolean.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/FirefoxWithKerberosSSO.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/FirefoxWithKerberosSSO.png
new file mode 100644
index 0000000..20fca1e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/FirefoxWithKerberosSSO.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-Software_Log_Viewer.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-Software_Log_Viewer.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-Software_Update_Preferences.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-Software_Update_Preferences.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-add_remove_software.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-add_remove_software.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-additional_updates.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-additional_updates.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-authenticate.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-authenticate.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-filters-only_available.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-filters-only_available.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-filters-only_end_user.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-filters-only_end_user.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-htop.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-htop.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-install.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-install.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-installing_a_package_group.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-installing_a_package_group.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-removal_in_progress.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-removal_in_progress.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-remove.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-remove.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-removing_a_package.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-removing_a_package.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-software_update.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-software_update.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-updates_available.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Graphical_Package_Management-updates_available.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Load_New_Policy.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Load_New_Policy.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Connect_automatically.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Connect_automatically.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-IPv4_Settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-IPv4_Settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-Wired.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-Wired.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Addresses.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Addresses.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DHCP_Client_ID.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DHCP_Client_ID.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DNS_Servers.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DNS_Servers.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Method.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Method.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Routes.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Routes.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Search_domains.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Search_domains.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-System_eth0-Routes.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-System_eth0-Routes.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-applet_states.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-applet_states.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/PS2port.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/PS2port.png
new file mode 100644
index 0000000..c1ef70b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/PS2port.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/SCLogin.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/SCLogin.png
new file mode 100644
index 0000000..5bdef58
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/SCLogin.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/SCLoginEnrollment.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/SCLoginEnrollment.png
new file mode 100644
index 0000000..2809b32
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/SCLoginEnrollment.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/SELinux_Decision_Process.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/SELinux_Decision_Process.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Screenshot-1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Screenshot-1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Screenshot-2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Screenshot-2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Users_Groups-Create_New_User.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Users_Groups-Create_New_User.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/Users_Groups-User_Manager.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/Users_Groups-User_Manager.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/abrt_main.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/abrt_main.png
new file mode 100644
index 0000000..9d1e162
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/abrt_main.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/apol-DIF.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/apol-DIF.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/apol-TE-rule-search.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/apol-TE-rule-search.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/apol-plain.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/apol-plain.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/arrow.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/arrow.png
new file mode 100644
index 0000000..e4cc965
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/arrow.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/auth-panel.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/auth-panel.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/authconfig-auth.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/authconfig-auth.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/authconfig-options.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/authconfig-options.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/authconfig-user-info.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/authconfig-user-info.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/authconfig_LDAP_kerb.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/authconfig_LDAP_kerb.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/authconfig_advanced.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/authconfig_advanced.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/authicon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/authicon.png
new file mode 100644
index 0000000..e397b63
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/authicon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/bugworkflow_new4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/bugworkflow_new4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/bugworkflow_old8.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/bugworkflow_old8.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-authentication.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-authentication.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-ntsysv.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-ntsysv.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_configuration.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_configuration.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_disabled.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_disabled.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_enabled.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_enabled.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_running.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_running.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_selected.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_selected.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_stopped.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_stopped.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_unknown.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_unknown.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_wrong.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/controlling-access-to-services-service_wrong.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/date-and-time-authentication.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/date-and-time-authentication.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/date-and-time-date_and_time.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/date-and-time-date_and_time.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/date-and-time-network_time_protocol.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/date-and-time-network_time_protocol.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/date-and-time-time_zone.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/date-and-time-time_zone.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/devicemngr.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/devicemngr.png
new file mode 100644
index 0000000..9709a00
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/devicemngr.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/display-dualhead.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/display-dualhead.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/display-hardware.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/display-hardware.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/display-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/display-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/flask-arch.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/flask-arch.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/flow-diagram.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/flow-diagram.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey1.png
new file mode 100644
index 0000000..bb1da26
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey10.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey10.png
new file mode 100644
index 0000000..87cf00e
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey10.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey11.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey11.png
new file mode 100644
index 0000000..f1203af
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey11.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey2.png
new file mode 100644
index 0000000..6cbcf6f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey3.png
new file mode 100644
index 0000000..4755ef0
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey4.png
new file mode 100644
index 0000000..a818c6c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey5.png
new file mode 100644
index 0000000..fb564a6
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey6.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey6.png
new file mode 100644
index 0000000..214184c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey6.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey7.png
new file mode 100644
index 0000000..eade526
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey8.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey8.png
new file mode 100644
index 0000000..7d71471
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey8.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey9.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey9.png
new file mode 100644
index 0000000..048a406
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/genkey9.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-print-manager-list.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-print-manager-list.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-print-manager.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-print-manager.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-print-queue.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-print-queue.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-system-monitor-filesystems.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-system-monitor-filesystems.png
new file mode 100644
index 0000000..18854ce
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-system-monitor-filesystems.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-system-monitor-memory.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-system-monitor-memory.png
new file mode 100644
index 0000000..e432ce7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-system-monitor-memory.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-system-monitor-processes.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-system-monitor-processes.png
new file mode 100644
index 0000000..90e9df7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/gnome-system-monitor-processes.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/group-new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/group-new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/group-properties.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/group-properties.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-directories-add.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-directories-add.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-directories.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-directories.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-environment.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-environment.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-general-options.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-general-options.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-listen.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-listen.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-logging.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-logging.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-main.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-main.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-server.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-server.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-siteconfig.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-siteconfig.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-tuning.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-tuning.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-virtualhosts-ssl.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-virtualhosts-ssl.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-virtualhosts.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/httpd-virtualhosts.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/hwbrowser.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/hwbrowser.png
new file mode 100644
index 0000000..d3a44d8
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/hwbrowser.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/icon-greencheck-pkgs.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/icon-greencheck-pkgs.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/icon-install-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/icon-install-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/icon-removal-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/icon-removal-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/image_needed.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/image_needed.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/individual-pkgs.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/individual-pkgs.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/install-depend-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/install-depend-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/install-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/install-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-applet-addition.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-applet-addition.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-applet-observation.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-applet-observation.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-applet-selection.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-applet-selection.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-break-take.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-break-take.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-break.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-break.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts-default.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts-default.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts-new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts-new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts-prioritize.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts-prioritize.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts-separate.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts-separate.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts-test.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts-test.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/keyboard-configuration-layouts.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvg.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvg.png
new file mode 100644
index 0000000..c7a6719
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvg.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-auto-config.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-auto-config.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main10.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main10.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main12.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main12.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main13.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main13.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main14.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main14.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main15.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main15.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main16.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main16.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main17.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main17.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main18.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main18.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main21.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main21.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main23.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main23.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main26.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main26.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main27.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main27.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main28.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main28.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main30.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main30.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main31.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main31.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main32.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main32.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main33.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main33.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main34.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main34.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main36.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main36.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main7.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-main7.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-boot.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-boot.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-done.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-done.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-free.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-free.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-lv.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-lv.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-lvdone.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-lvdone.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-postboot.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-postboot.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-pv01.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-pv01.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-pvdone.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-pvdone.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-vg.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm-manual-vg.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm/lvg.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm/lvg.svg
new file mode 100644
index 0000000..f564769
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm/lvols.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvm/lvols.svg
new file mode 100644
index 0000000..a2c6a8f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/lvols.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvols.png
new file mode 100644
index 0000000..dae912b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/lvols.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/mouseconfig.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/mouseconfig.png
new file mode 100644
index 0000000..52c513b
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/mouseconfig.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/n-t-n-ipsec-diagram.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/n-t-n-ipsec-diagram.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/n-to-n-ipsec-local.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/n-to-n-ipsec-local.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/n-to-n-ipsec-remote.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/n-to-n-ipsec-remote.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-aliases.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-aliases.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-dns.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-dns.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-ethernet-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-ethernet-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-ethernet.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-ethernet.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-home-profile.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-home-profile.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-hosts.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-hosts.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-isdn-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-isdn-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-isdn.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-isdn.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-modem-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-modem-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-modem.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-modem.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-office-profile.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-office-profile.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-tokenring-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-tokenring-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-tokenring.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-tokenring.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-tonline1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-tonline1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-tonlineAcctsetup.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-tonlineAcctsetup.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-tonlineProvidertab.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-tonlineProvidertab.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-wireless-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-wireless-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-wireless.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-wireless.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-xdsl-selectdevicetype.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-xdsl-selectdevicetype.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-xdsl-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-xdsl-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-xdsl.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/neat-xdsl.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat.png
new file mode 100644
index 0000000..8a00403
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/neat.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/nfs-add.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/nfs-add.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/nfs-general-options.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/nfs-general-options.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/nfs-server-settings.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/nfs-server-settings.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/nfs-user-access.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/nfs-user-access.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/oprof-start-config.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/oprof-start-config.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/oprof-start-setup.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/oprof-start-setup.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/originals/Graphical_Package_Management-software_update.xcf b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/originals/Graphical_Package_Management-software_update.xcf differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/package-selections.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/package-selections.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/pam-icon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/pam-icon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/print-manager-menu.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/print-manager-menu.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-add-printer.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-add-printer.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-config1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-config1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-config2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-config2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-config3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-config3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-config4.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-config4.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-config5.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-config5.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-default-icon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-default-icon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-edit.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-edit.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-ipp.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-ipp.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-jetdirect.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-jetdirect.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-local.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-local.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-lpd.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-lpd.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-main.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-main.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-ncp.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-ncp.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-queue-name.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-queue-name.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-select-model.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-select-model.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-sharing-general.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-sharing-general.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-sharing-hosts.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-sharing-hosts.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-sharing-queue.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-sharing-queue.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-smb.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-smb.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-test-page.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printconf-test-page.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/printer-notification-icon.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/printer-notification-icon.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-boot-error.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-boot-error.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-final.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-final.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-free.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-free.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-lvm-final.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-lvm-final.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-mntpt.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-mntpt.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-part-add.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-part-add.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-part-bootready.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-part-bootready.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-part-opt.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-part-opt.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-part-opt2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/raid-manual-part-opt2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-config-packages.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-config-packages.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-config-users.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-config-users.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-add.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-add.png
new file mode 100644
index 0000000..7df9952
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-add.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-monitoring1.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-monitoring1.png
new file mode 100644
index 0000000..2deec4c
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-monitoring1.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-monitoring2.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-monitoring2.png
new file mode 100644
index 0000000..164b4c7
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-monitoring2.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-monitoring3.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-monitoring3.png
new file mode 100644
index 0000000..e7daa2f
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-monitoring3.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-prefs.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-prefs.png
new file mode 100644
index 0000000..b3a1ff4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-prefs.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-sample.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-sample.png
new file mode 100644
index 0000000..99d2abd
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer-sample.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer.png
new file mode 100644
index 0000000..e12c3ac
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-logviewer.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-optional-packages.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/redhat-optional-packages.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/registering.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/registering.png
new file mode 100644
index 0000000..2d823b4
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/registering.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/relevant-errata.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/relevant-errata.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/removal-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/removal-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/remove-depend-prep.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/remove-depend-prep.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/rh-securitylevel.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/rh-securitylevel.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/rhl-common/networkconfig/n-t-n-ipsec-diagram.svg b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/s-c-samba-basic.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/s-c-samba-basic.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/s-c-samba-create-share.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/s-c-samba-create-share.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/s-c-samba-security.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/s-c-samba-security.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/s-c-samba-users.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/s-c-samba-users.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/s-c-samba.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/s-c-samba.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/samba-nautilus-machines.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/samba-nautilus-machines.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/samba-nautilus.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/samba-nautilus.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/seaudit-Edit-filter.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/seaudit-Edit-filter.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/seaudit-Query-policy.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/seaudit-Query-policy.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/seaudit-Select-target-type-filtering.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/seaudit-Select-target-type-filtering.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/seaudit-View-filtering.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/seaudit-View-filtering.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/seaudit-plain.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/seaudit-plain.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/sec-ipsec-host2host.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/sec-ipsec-host2host.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/security-intro-to-mls.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/security-intro-to-mls.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/security-mls-data-flow.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/security-mls-data-flow.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/serialport.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/serialport.png
new file mode 100644
index 0000000..a283eae
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/serialport.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/serv-config.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/serv-config.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/ssh-passphrase-prompt.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/ssh-passphrase-prompt.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/ssh-startup-applications-add.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/ssh-startup-applications-add.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/ssh-startup-applications-check.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/ssh-startup-applications-check.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/ssh-startup-applications.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/ssh-startup-applications.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/switchmail-gui.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/switchmail-gui.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/system-config-nfs.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/system-config-nfs.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/tcp_wrap_diagram.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/tcp_wrap_diagram.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/usbport.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/usbport.png
new file mode 100644
index 0000000..d2e5525
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/usbport.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/user-new.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/user-new.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/user-properties.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/user-properties.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/user_pass_groups.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/user_pass_groups.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/user_pass_info.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/user_pass_info.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/images/your-rhn.png b/public_html/en-US/Fedora_Draft_Documentation/0.1/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_Draft_Documentation/0.1/html/Deployment_Guide/images/your-rhn.png differ
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html
new file mode 100644
index 0000000..b3d2562
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><meta name="description" content="The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 13." /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="next" href="pr01.html" title="Preface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left"
href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" 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="id1940995" 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 Draft Documentation</span> <span class="productnumber"></span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id1940995" class="title">Deployment Guide</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="ce
nter"><h2 class="subtitle">Deployment, configuration and administration of Fedora 13</h2></div><p class="edition">Edition 13.0.1</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><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id601514" 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">
+ 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 Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 13.
+ </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#id953328">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="pr01.html#id953305">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="pr01.html#id664376">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="pr01.html#id645978">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="sect-RedHat-We_Need_Feedback.html">2. We Need Feedback!</a></span></dt><dd><dl><dt><span class="section"><a href="sect-RedHat-We_Need_Feedback.html#id963600">2.1. Technical Review Requests</a></span></dt></dl></dd><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="par
t"><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><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">1.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">1.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Security-Related_Packages">1.1.3. Updating Security-Related Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">1.1.4. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">1.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span class="sect
ion"><a href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">1.2.1. Searching, Listing and Displaying Package Information</a></span></dt><dt><span class="section"><a href="sec-Installing.html">1.2.2. Installing</a></span></dt><dt><span class="section"><a href="sec-Removing.html">1.2.3. Removing</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">1.3. Configuring Yum and Yum Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">1.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="sec-Setting_repository_Options.html">1.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="sec-Using_Yum_Variables.html">1.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">1.3.4. Creating a Yu
m Repository</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">1.4. Yum Plugins</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">1.4.1. Enabling, Configuring and Disabling Yum Plugins</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">1.4.2. Installing More Yum Plugins</a></span></dt><dt><span class="section"><a href="sec-Plugin_Descriptions.html">1.4.3. Plugin Descriptions</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html#sec-Refreshing_Software_Sources_Yum_Repositories">2.2.1. Refreshing Software Sources (Yum Repositories)</a></span></dt><dt><span class="section"><a href="sec-Finding_Packages_with_Filters.html">2.2.2. Finding Packages with Filters</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Packages_and_Dependencies.html">2.2.3. Installing and Removing Packages (and Dependencies)</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Package_Groups.html">2.2.4. Installing and Removing Package Groups</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Transaction_Log.html">2.2.5. Viewing the Transaction Log</a></span></dt></dl></dd><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_Ma
nagement-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><dd><dl><dt><span class="section"><a href="s1-rpm-using.html#s2-rpm-finding">3.2.1. Finding RPM Packages</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Upgrading.html">3.2.2. Installing and Upgrading</a></span></dt><dt><span class="section"><a href="sec-Configuration_File_Changes.html">3.2.3. Configuration File Changes</a></span></dt><dt><span class="section"><a href="s2-rpm-uninstalling.html">3.2.4. Uninstalling</a></span></dt><dt><span class="section"><a href="s2-rpm-freshening.html">3.2.5. Freshening</a></span></dt><dt><span class="section"><a href="s2-rpm-querying.html">3.2.6. Querying</a></span></dt><dt
><span class="section"><a href="s2-rpm-verifying.html">3.2.7. Verifying</a></span></dt></dl></dd><dt><span class="section"><a href="s1-check-rpm-sig.html">3.3. Checking a Package's Signature</a></span></dt><dd><dl><dt><span class="section"><a href="s1-check-rpm-sig.html#s2-keys-importing">3.3.1. Importing Keys</a></span></dt><dt><span class="section"><a href="s2-keys-checking.html">3.3.2. Verifying Signature of Packages</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="s1-rpm-additional-resources.html#s2-rpm-installed-docs">3.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-rpm-useful-websites.html">3.5.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-rpm-related-books.html"
>3.5.3. Related Books</a></span></dt></dl></dd></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-networkscripts-interfaces.html">4.2. Interface Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">4.2.1. Ethernet Interfaces</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-chan.html">4.2.2. Channel Bonding Interfaces</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-alias.html">4.2.3. Alias and Clone Files</a></span></dt><dt><span class="section"><a href="s2-ne
tworkscripts-interfaces-ppp0.html">4.2.4. Dialup Interfaces</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-other.html">4.2.5. Other Interfaces</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="s1-networkscripts-resources.html#s2-networkscripts-docs-inst">4.6.1. Installed Documentation</a></span></dt></dl></dd></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_Conf
iguration.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><dd><dl><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network">5.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="sec-Configuring_New_and_Editing_Existing_Connections.html">5.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Automatically.html">5.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="sec-User_and_System_Connections.html">5.2.4. User and System Connections</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Establishing_Connections.html">5.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Establ
ishing_Connections.html#sec-Establishing_a_Wired_Ethernet_Connection">5.3.1. Establishing a Wired (Ethernet) Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Wireless_Connection.html">5.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Mobile_Broadband_Connection.html">5.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_VPN_Connection.html">5.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_DSL_Connection.html">5.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_Routes.html">5.3.6. Establishing Routes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html">5.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Conne
ction_Settings.html#sec-Configuring_802.1x_Security">5.4.1. Configuring 802.1x Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_Wireless_Security.html">5.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_PPP_Point-to-Point_Settings.html">5.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv4_Settings.html">5.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv6_Settings.html">5.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="sec-NetworkManager_Architecture.html">5.5. NetworkManager Architecture</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Controlling_Access_to_Services.html">6. Controlling Access to Services</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Controlling_Access_to_Services.html#s1-services-runlevels">6.
1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="s1-services-configuring.html">6.2. Configuring the Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-configuring.html#s2-services-serviceconf">6.2.1. Using the <span class="application"><strong>Service Configuration</strong></span> Utility</a></span></dt><dt><span class="section"><a href="s2-services-ntsysv.html">6.2.2. Using the <span class="application"><strong>ntsysv</strong></span> Utility</a></span></dt><dt><span class="section"><a href="s2-services-chkconfig.html">6.2.3. Using the <code class="command">chkconfig</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">6.3. Running the Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-running.html#s2-services-service">6.3.1. Using the <span class="application"><strong>service</strong></span> Utility</a></span></dt></dl></dd><dt><span c
lass="section"><a href="s1-services-additional-resources.html">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">6.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">6.4.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-The_BIND_DNS_Server.html">7. The BIND DNS Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s1-bind-introduction">7.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-zones">7.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">7.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s2-bin
d-introduction-bind">7.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-namedconf.html">7.2. <code class="filename">/etc/named.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-namedconf.html#s2-bind-namedconf-state">7.2.1. Common Statement Types</a></span></dt><dt><span class="section"><a href="s2-bind-namedconf-state-other.html">7.2.2. Other Statement Types</a></span></dt><dt><span class="section"><a href="s2-bind-namedconf-comm.html">7.2.3. Comment Tags</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-zone.html">7.3. Zone Files</a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-zone.html#s2-bind-zone-directives">7.3.1. Zone File Directives</a></span></dt><dt><span class="section"><a href="s3-bind-zone-rr.html">7.3.2. Zone File Resource Records</a></span></dt><dt><span class="section"><a href="s2-bind-zone-examples.html">7.3.3. Example Zone File</a></span></dt><dt><
span class="section"><a href="s2-bind-configuration-zone-reverse.html">7.3.4. Reverse Name Resolution Zone Files</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-rndc.html">7.4. Using <code class="command">rndc</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-rndc.html#s2-bind-rndc-configuration-namedconf">7.4.1. Configuring <code class="filename">/etc/named.conf</code> </a></span></dt><dt><span class="section"><a href="s2-bind-rndc-configuration-rndcconf.html">7.4.2. Configuring <code class="filename">/etc/rndc.conf</code> </a></span></dt><dt><span class="section"><a href="s2-bind-rndc-options.html">7.4.3. Command Line Options</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-features.html">7.5. Advanced Features of BIND</a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-features.html#s2-bind-features-protocol">7.5.1. DNS Protocol Enhancements</a></span></dt><dt><span class="section"><a href="s2-bi
nd-features-views.html">7.5.2. Multiple Views</a></span></dt><dt><span class="section"><a href="s2-bind-features-security.html">7.5.3. Security</a></span></dt><dt><span class="section"><a href="s2-bind-features-ipv6.html">7.5.4. IP version 6</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-mistakes.html">7.6. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="s1-bind-additional-resources.html">7.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-additional-resources.html#s2-bind-installed-docs">7.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-bind-useful-websites.html">7.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-bind-related-books.html">7.7.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-OpenSSH.html">8. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1
-ssh-protocol">8.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">8.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-features">8.1.2. Main Features</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">8.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">8.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">8.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">8.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">8.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">8.2.3. Requiring SSH for Remote Connections</a></sp
an></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">8.2.4. Using a Key-Based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-clients.html">8.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">8.3.1. Using the <code class="command">ssh</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">8.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">8.3.3. Using the <code class="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-beyondshell.html">8.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">8.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">8.4.2. Port Forwardi
ng</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">8.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-openssh-additional-resources.html#s2-openssh-installed-docs">8.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-openssh-useful-websites.html">8.5.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Samba.html">9. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Samba.html#samba-rgs-overview">9.1. Introduction to Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Samba.html#s2-samba-abilities">9.1.1. Samba Features</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-daemons.html">9.2. Samba Daemons and Related Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-daemons.html#s2-samba-services">9.2.1. Samba Daemons</a></span></dt></dl></dd><dt><spa
n class="section"><a href="s1-samba-connect-share.html">9.3. Connecting to a Samba Share</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-connect-share.html#s2-samba-connect-share-cmdline">9.3.1. Command Line</a></span></dt><dt><span class="section"><a href="s1-samba-mounting.html">9.3.2. Mounting the Share</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-configuring.html">9.4. Configuring a Samba Server</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-configuring.html#s2-samba-configuring-gui">9.4.1. Graphical Configuration</a></span></dt><dt><span class="section"><a href="s2-samba-configuring-cmdline.html">9.4.2. Command Line Configuration</a></span></dt><dt><span class="section"><a href="s2-samba-encrypted-passwords.html">9.4.3. Encrypted Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-startstop.html">9.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="s1-
samba-servers.html">9.6. Samba Server Types and the <code class="command">smb.conf</code> File</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-servers.html#s2-samba-standalone">9.6.1. Stand-alone Server</a></span></dt><dt><span class="section"><a href="s2-samba-domain-member.html">9.6.2. Domain Member Server</a></span></dt><dt><span class="section"><a href="s2-samba-domain-controller.html">9.6.3. Domain Controller</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-security-modes.html">9.7. Samba Security Modes</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-security-modes.html#s2-samba-user-level">9.7.1. User-Level Security</a></span></dt><dt><span class="section"><a href="s2-samba-share-level.html">9.7.2. Share-Level Security</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-account-info-dbs.html">9.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="s1-samba-netw
ork-browsing.html">9.9. Samba Network Browsing</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-network-browsing.html#s2-samba-domain-browsing">9.9.1. Domain Browsing</a></span></dt><dt><span class="section"><a href="s2-samba-wins.html">9.9.2. WINS (Windows Internetworking Name Server)</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-cups.html">9.10. Samba with CUPS Printing Support</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-cups.html#s2-samba-cups-smb.conf">9.10.1. Simple <code class="filename">smb.conf</code> Settings</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-programs.html">9.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="s1-samba-resources.html">9.12. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-resources.html#s2-samba-resources-installed">9.12.1. Installed Documentation</a></span></dt><dt><span class="secti
on"><a href="s2-samba-resources-published.html">9.12.2. Related Books</a></span></dt><dt><span class="section"><a href="s2-samba-resources-community.html">9.12.3. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html">10. 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">10.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-server.html">10.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-configuring-server.html#config-file">10.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="lease-database.html">10.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="ch10s02s03.html">10.2.3. Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="dhcp-r
elay-agent.html">10.2.4. DHCP Relay Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp-configuring-client.html">10.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html">10.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html#sect-dns_Host_Configuration">10.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">10.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="s1-dhcp-additional-resources.html">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-additional-resources.html#s2-dhcp-installed-docs">10.6.1. Installed Documentation</a></span></dt></dl></dd></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-httpd-v2">11.1. Apache HTTP Server 2.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_Apache_HTTP_Server.html#s2-httpd-v2-features">11.1.1. Features of Apache HTTP Server 2.2</a></span></dt></dl></dd><dt><span class="section"><a href="s1-httpd-mig.html">11.2. Migrating Apache HTTP Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="s1-httpd-mig.html#s1-httpd-v22-mig">11.2.1. Migrating Apache HTTP Server 2.0 Configuration Files</a></span></dt><dt><span class="section"><a href="s3-httpd-v2-mig.html">11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-startstop.html">11.3. Starting and Stopping <code class="command">httpd</code> </a></span></dt><dt><span class="section"><a href="s1-apache-config-ui.html">11.4. Apache HTTP Server Configuration</a></span></dt><dd><dl
><dt><span class="section"><a href="s1-apache-config-ui.html#s2-httpd-basic-settings">11.4.1. Basic Settings</a></span></dt><dt><span class="section"><a href="s2-httpd-default-settings.html">11.4.2. Default Settings</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-config.html">11.5. Configuration Directives in <code class="filename">httpd.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-apache-config.html#s2-apache-tips">11.5.1. General Configuration Tips</a></span></dt><dt><span class="section"><a href="s2-apache-sslcommands.html">11.5.2. Configuration Directives for SSL</a></span></dt><dt><span class="section"><a href="s2-apache-mpm-containers.html">11.5.3. MPM Specific Server-Pool Directives</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-addmods.html">11.6. Adding Modules</a></span></dt><dt><span class="section"><a href="s1-apache-virtualhosts.html">11.7. Virtual Hosts</a></span></dt><dd><dl><dt><span cl
ass="section"><a href="s1-apache-virtualhosts.html#s2-apache-settingupvhosts">11.7.1. Setting Up Virtual Hosts</a></span></dt></dl></dd><dt><span class="section"><a href="s1-httpd-secure-server.html">11.8. Apache HTTP Secure Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-httpd-secure-server.html#s2-secureserver-optionalpackages">11.8.1. An Overview of Security-Related Packages</a></span></dt><dt><span class="section"><a href="s2-secureserver-overview-certs.html">11.8.2. An Overview of Certificates and Security</a></span></dt><dt><span class="section"><a href="s1-secureserver-oldcert.html">11.8.3. Using Pre-Existing Keys and Certificates</a></span></dt><dt><span class="section"><a href="s2-secureserver-certs.html">11.8.4. Types of Certificates</a></span></dt><dt><span class="section"><a href="s2-secureserver-generatingkey.html">11.8.5. Generating a Key</a></span></dt><dt><span class="section"><a href="s1-use-new-key.html">11.8.6. How to conf
igure the server to use the new key</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-additional-resources.html">11.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-apache-additional-resources.html#s2-apache-additional-resources-web">11.9.1. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-FTP.html">12. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-FTP.html#s1-ftp-protocol">12.1. The File Transfer Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-FTP.html#s2-ftp-protocol-multiport">12.1.1. Multiple Ports, Multiple Modes</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ftp-servers.html">12.2. FTP Servers</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-servers.html#s2-ftp-servers-vsftpd">12.2.1. <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s2-ftp-vsftpd-conf.htm
l">12.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s1-ftp-vsftpd-start.html">12.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-vsftpd-start.html#s2-ftp-vsftpd-start-multi">12.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-ftp-vsftpd-conf.html">12.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-vsftpd-conf.html#s2-ftp-vsftpd-conf-opt-daemon">12.5.1. Daemon Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-login.html">12.5.2. Log In Options and Access Controls</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-anon.html">12.5.3. Anonymous User Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-
opt-usr.html">12.5.4. Local User Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-dir.html">12.5.5. Directory Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-file.html">12.5.6. File Transfer Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-log.html">12.5.7. Logging Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-net.html">12.5.8. Network Options</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ftp-resources.html">12.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-resources.html#s2-ftp-installed-documentation">12.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-ftp-useful-websites.html">12.6.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-email.html">13. Email</a></span></dt><dd><dl><dt><span class="section"><a href="c
h-email.html#s1-email-protocols">13.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="ch-email.html#s2-email-protocols-send">13.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="ch-email.html#s2-email-protocols-client">13.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">13.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta">13.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mda.html">13.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mua.html">13.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">13.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mta.html#s2-email-mta-sendmail">13.3.1. Sendmail</a></span></dt
><dt><span class="section"><a href="s2-email-mta-postfix.html">13.3.2. Postfix</a></span></dt><dt><span class="section"><a href="s2-email-mta-fetchmail.html">13.3.3. Fetchmail</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-switchmail.html">13.4. Mail Transport Agent (MTA) Configuration</a></span></dt><dt><span class="section"><a href="s1-email-mda.html">13.5. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-email-procmail-configuration">13.5.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">13.5.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mua.html">13.6. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">13.6.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">13.7. Additio
nal Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-docs">13.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-email-useful-websites.html">13.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-email-related-books.html">13.7.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Lightweight_Directory_Access_Protocol_LDAP.html">14. Lightweight Directory Access Protocol (LDAP)</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Lightweight_Directory_Access_Protocol_LDAP.html#s1-ldap-adv">14.1. Why Use LDAP?</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Lightweight_Directory_Access_Protocol_LDAP.html#s1-ldap-v3">14.1.1. OpenLDAP Features</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-terminology.html">14.2. LDAP Terminology</a></span></dt><dt><span class="section"><a href="
s1-ldap-daemonsutils.html">14.3. OpenLDAP Daemons and Utilities</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ldap-daemonsutils.html#s2-ldap-pam-nss">14.3.1. NSS, PAM, and LDAP</a></span></dt><dt><span class="section"><a href="s2-ldap-other-apps.html">14.3.2. PHP4, LDAP, and the Apache HTTP Server</a></span></dt><dt><span class="section"><a href="s2-ldap-applications.html">14.3.3. LDAP Client Applications</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-files.html">14.4. OpenLDAP Configuration Files</a></span></dt><dt><span class="section"><a href="s1-ldap-files-schemas.html">14.5. The <code class="filename">/etc/openldap/schema/</code> Directory</a></span></dt><dt><span class="section"><a href="s1-ldap-quickstart.html">14.6. OpenLDAP Setup Overview</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ldap-quickstart.html#s2-ldap-files-slapd-conf">14.6.1. Editing <code class="filename">/etc/openldap/slapd.conf</code> </a></span></dt>
</dl></dd><dt><span class="section"><a href="s1-ldap-pam.html">14.7. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ldap-pam.html#s2-ldap-pamd">14.7.1. PAM and LDAP</a></span></dt><dt><span class="section"><a href="s2-ldap-migrate.html">14.7.2. Migrating Old Authentication Information to LDAP Format</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-migrate.html">14.8. Migrating Directories from Earlier Releases</a></span></dt><dt><span class="section"><a href="s1-ldap-additional-resources.html">14.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ldap-additional-resources.html#s2-ldap-installed-docs">14.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-ldap-additional-resources-web.html">14.9.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-ldap-related-books.html">14.9.3. Related Books</a></span></dt></
dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Authentication_Configuration.html">15. Authentication Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool">15.1. The Authentication Configuration Tool</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">15.1.1. Identity & Authentication</a></span></dt><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">15.1.2. Advanced Options</a></span></dt><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">15.1.3. Command Line Version</a></span></dt></dl></dd><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html">15.2. The System Securi
ty Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html#sect-SSSD_User_Guide-Introduction-What_is_SSSD">15.2.1. What is SSSD?</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html">15.2.2. SSSD Features</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Setting_Up_SSSD.html">15.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Services.html">15.2.4. Configuring Services</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Domains.html">15.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">15.2.6. Setting up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Troubleshooting.html">15.2.7. Troubleshooting</a></span
></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html">15.2.8. SSSD Configuration File Format</a></span></dt></dl></dd></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="ch-Console_Access.html">16. Console Access</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Console_Access.html#s1-access-console-ctrlaltdel">16.1. Disabling Shutdown Via <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span></a></span></dt><dt><span class="section"><a href="s1-access-console-program.html">16.2. Disabling Console Program Access</a></span></dt><dt><span class="section"><a href="s1-access-console-define.html">16.3. Defining the Console</a></span></dt><dt><span class="section"><a href="s1-access-console-files.html
">16.4. Making Files Accessible From the Console</a></span></dt><dt><span class="section"><a href="s1-access-console-enable.html">16.5. Enabling Console Access for Other Applications</a></span></dt><dt><span class="section"><a href="s1-access-floppy.html">16.6. The <code class="filename">floppy</code> Group</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-proc.html">17. 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">17.1. A Virtual File System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-proc.html#s2-proc-viewing">17.1.1. Viewing Virtual Files</a></span></dt><dt><span class="section"><a href="ch-proc.html#s2-proc-change">17.1.2. Changing Virtual Files</a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-topfiles.html">17.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="sect
ion"><a href="s1-proc-topfiles.html#s2-proc-buddyinfo">17.2.1. <code class="filename">/proc/buddyinfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-cmdline.html">17.2.2. <code class="filename">/proc/cmdline</code> </a></span></dt><dt><span class="section"><a href="s2-proc-cpuinfo.html">17.2.3. <code class="filename">/proc/cpuinfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-crypto.html">17.2.4. <code class="filename">/proc/crypto</code> </a></span></dt><dt><span class="section"><a href="s2-proc-devices.html">17.2.5. <code class="filename">/proc/devices</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dma.html">17.2.6. <code class="filename">/proc/dma</code> </a></span></dt><dt><span class="section"><a href="s2-proc-execdomains.html">17.2.7. <code class="filename">/proc/execdomains</code> </a></span></dt><dt><span class="section"><a href="s2-proc-fb.html">17.2.8. <code class="filename">/proc/fb</code> </a></spa
n></dt><dt><span class="section"><a href="s2-proc-filesystems.html">17.2.9. <code class="filename">/proc/filesystems</code> </a></span></dt><dt><span class="section"><a href="s2-proc-interrupts.html">17.2.10. <code class="filename">/proc/interrupts</code> </a></span></dt><dt><span class="section"><a href="s2-proc-iomem.html">17.2.11. <code class="filename">/proc/iomem</code> </a></span></dt><dt><span class="section"><a href="s2-proc-ioports.html">17.2.12. <code class="filename">/proc/ioports</code> </a></span></dt><dt><span class="section"><a href="s2-proc-kcore.html">17.2.13. <code class="filename">/proc/kcore</code> </a></span></dt><dt><span class="section"><a href="s2-proc-kmsg.html">17.2.14. <code class="filename">/proc/kmsg</code> </a></span></dt><dt><span class="section"><a href="s2-proc-loadavg.html">17.2.15. <code class="filename">/proc/loadavg</code> </a></span></dt><dt><span class="section"><a href="s2-proc-locks.html">17.2.16. <code class="filename">/proc/
locks</code> </a></span></dt><dt><span class="section"><a href="s2-proc-mdstat.html">17.2.17. <code class="filename">/proc/mdstat</code> </a></span></dt><dt><span class="section"><a href="s2-proc-meminfo.html">17.2.18. <code class="filename">/proc/meminfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-misc.html">17.2.19. <code class="filename">/proc/misc</code> </a></span></dt><dt><span class="section"><a href="s2-proc-modules.html">17.2.20. <code class="filename">/proc/modules</code> </a></span></dt><dt><span class="section"><a href="s2-proc-mounts.html">17.2.21. <code class="filename">/proc/mounts</code> </a></span></dt><dt><span class="section"><a href="s2-proc-mtrr.html">17.2.22. <code class="filename">/proc/mtrr</code> </a></span></dt><dt><span class="section"><a href="s2-proc-partitions.html">17.2.23. <code class="filename">/proc/partitions</code> </a></span></dt><dt><span class="section"><a href="s2-proc-pci.html">17.2.24. <code class="filen
ame">/proc/pci</code> </a></span></dt><dt><span class="section"><a href="s2-proc-slabinfo.html">17.2.25. <code class="filename">/proc/slabinfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-stat.html">17.2.26. <code class="filename">/proc/stat</code> </a></span></dt><dt><span class="section"><a href="s2-proc-swaps.html">17.2.27. <code class="filename">/proc/swaps</code> </a></span></dt><dt><span class="section"><a href="s2-proc-sysrq-trigger.html">17.2.28. <code class="filename">/proc/sysrq-trigger</code> </a></span></dt><dt><span class="section"><a href="s2-proc-uptime.html">17.2.29. <code class="filename">/proc/uptime</code> </a></span></dt><dt><span class="section"><a href="s2-proc-version.html">17.2.30. <code class="filename">/proc/version</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-directories.html">17.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dd><dl><dt><span class="section"><a h
ref="s1-proc-directories.html#s2-proc-processdirs">17.3.1. Process Directories</a></span></dt><dt><span class="section"><a href="s2-proc-dir-bus.html">17.3.2. <code class="filename">/proc/bus/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-driver.html">17.3.3. <code class="filename">/proc/driver/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-fs.html">17.3.4. <code class="filename">/proc/fs</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-irq.html">17.3.5. <code class="filename">/proc/irq/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-net.html">17.3.6. <code class="filename">/proc/net/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-scsi.html">17.3.7. <code class="filename">/proc/scsi/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-sys.html">17.3.8. <code class="filename">/proc/sys/</code> </a></span></dt><dt><span class="section"><a
href="s2-proc-dir-sysvipc.html">17.3.9. <code class="filename">/proc/sysvipc/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-tty.html">17.3.10. <code class="filename">/proc/tty/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-pid.html">17.3.11. <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-sysctl.html">17.4. Using the <code class="command">sysctl</code> Command</a></span></dt><dt><span class="section"><a href="s1-proc-additional-resources.html">17.5. References</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><dd><dl><dt><span class="section"><a href="ch-The_syscon
fig_Directory.html#s2-sysconfig-arpwatch">18.1.1. <code class="filename">/etc/sysconfig/arpwatch</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-authconfig">18.1.2. <code class="filename">/etc/sysconfig/authconfig</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-autofs">18.1.3. <code class="filename">/etc/sysconfig/autofs</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-clock">18.1.4. <code class="filename">/etc/sysconfig/clock</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-desktop">18.1.5. <code class="filename">/etc/sysconfig/desktop</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-dhcpd">18.1.6. <code class="filename">/etc/sysconfig/dhcpd</code> </a></span></dt><dt><span class="section"><a href="ch
-The_sysconfig_Directory.html#s2-sysconfig-firewall">18.1.7. <code class="filename">/etc/sysconfig/firstboot</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-i18n">18.1.8. <code class="filename">/etc/sysconfig/i18n</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-init">18.1.9. <code class="filename">/etc/sysconfig/init</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-ip6tables">18.1.10. <code class="filename">/etc/sysconfig/ip6tables-config</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-kybd">18.1.11. <code class="filename">/etc/sysconfig/keyboard</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-named">18.1.12. <code class="filename">/etc/sysconfig/named</code> </a></span></dt><dt><span class="section"
><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-network">18.1.13. <code class="filename">/etc/sysconfig/network</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-ntpd">18.1.14. <code class="filename">/etc/sysconfig/ntpd</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-radvd">18.1.15. <code class="filename">/etc/sysconfig/radvd</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-samba">18.1.16. <code class="filename">/etc/sysconfig/samba</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-selinux">18.1.17. <code class="filename">/etc/sysconfig/selinux</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-sendmail">18.1.18. <code class="filename">/etc/sysconfig/sendmail</code> </a></span></dt><dt><span class="s
ection"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-spamd">18.1.19. <code class="filename">/etc/sysconfig/spamassassin</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-squid">18.1.20. <code class="filename">/etc/sysconfig/squid</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-rcu">18.1.21. <code class="filename">/etc/sysconfig/system-config-users</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-vncservers">18.1.22. <code class="filename">/etc/sysconfig/vncservers</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-xinetd">18.1.23. <code class="filename">/etc/sysconfig/xinetd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysconfig-etcsysconf-dir.html">18.2. Directories in the <code class="filename">/etc/sysconfig/</code> Direct
ory</a></span></dt><dt><span class="section"><a href="s1-sysconfig-additional-resources.html">18.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysconfig-additional-resources.html#s2-sysconfig-installed-documentation">18.3.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Date_and_Time_Configuration.html">19. 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">19.1. Date/Time Properties Tool</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">19.1.1. Date and Time Properties</a></span></dt><dt><span class="section"><a href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Network_Time_Protocol">19.1.2. Network Time Protocol Properties</a></s
pan></dt><dt><span class="section"><a href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Time_Zone">19.1.3. Time Zone Properties</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html">19.2. Command Line Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">19.2.1. Date and Time Setup</a></span></dt><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">19.2.2. Network Time Protocol Setup</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Keyboard_Configuration.html">20. Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Keyboard_Configuration.html#s1-keyboard-layout">20.1. Changing the Keyboard Layout</a
></span></dt><dt><span class="section"><a href="s1-keyboard-indicator.html">20.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="s1-keyboard-break.html">20.3. Setting Up a Typing Break</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-The_X_Window_System.html">21. The X Window System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_X_Window_System.html#s1-x-server">21.1. The X11R7.1 Release</a></span></dt><dt><span class="section"><a href="s1-x-clients.html">21.2. Desktop Environments and Window Managers</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-clients.html#s2-x-clients-desktop">21.2.1. Desktop Environments</a></span></dt><dt><span class="section"><a href="s2-x-clients-winmanagers.html">21.2.2. Window Managers</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-server-configuration.html">21.3. X Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a
href="s1-x-server-configuration.html#s2-x-server-config-xorg.conf">21.3.1. <code class="filename">xorg.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-fonts.html">21.4. Fonts</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-fonts.html#s2-x-fonts-fontconfig">21.4.1. Fontconfig</a></span></dt><dt><span class="section"><a href="s2-x-fonts-core.html">21.4.2. Core X Font System</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-runlevels.html">21.5. Runlevels and X</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-runlevels.html#s2-x-runlevels-3">21.5.1. Runlevel 3</a></span></dt><dt><span class="section"><a href="s2-x-runlevels-5.html">21.5.2. Runlevel 5</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-additional-resources.html">21.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-additional-resources.html#s2-x-installed-documentation">21.6.1. Installed D
ocumentation</a></span></dt><dt><span class="section"><a href="s2-x-useful-websites.html">21.6.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ers_and_Groups.html">22. Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ers_and_Groups.html#s1-users-configui">22.1. User and Group Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ers_and_Groups.html#s2-redhat-config-users-user-new">22.1.1. Adding a New User</a></span></dt><dt><span class="section"><a href="ers_and_Groups.html#s2-redhat-config-users-group-new">22.1.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="ers_and_Groups.html#s2-redhat-config-users-group-properties">22.1.3. Modifying Group Properties</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html">22.2. User and Group Management Tools</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-cmd-line">2
2.2.1. Command Line Configuration</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-process.html">22.2.2. Explaining the Process</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-standard-users.html">22.3. Standard Users</a></span></dt><dt><span class="section"><a href="s1-users-groups-standard-groups.html">22.4. Standard Groups</a></span></dt><dt><span class="section"><a href="s1-users-groups-private-groups.html">22.5. User Private Groups</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-groups-private-groups.html#s2-users-groups-rationale">22.5.1. Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-shadow-utilities.html">22.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="s1-users-groups-additional-resources.html">22.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-groups-additional-resources.html#s2-user
s-groups-documentation">22.7.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Printer_Configuration.html">23. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Printer_Configuration.html#s1-printing-local-printer">23.1. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">23.2. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">23.3. Adding a Samba (SMB) Printer</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">23.4. Adding a JetDirect Printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">23.5. Selecting the Printer Model and Finishing</a></span></dt><dd><dl><dt><span class="section"><a href="s1-printing-select-model.html#s2-printing-confirm">23.5.1. Confirming Printer Configuration</a></span></dt></dl></dd><dt><span class=
"section"><a href="s1-printing-test-page.html">23.6. Printing a Test Page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">23.7. Modifying Existing Printers</a></span></dt><dd><dl><dt><span class="section"><a href="s1-printing-edit.html#id969412">23.7.1. The <span class="guilabel"><strong>Settings</strong></span> Tab</a></span></dt><dt><span class="section"><a href="ch23s07s02.html">23.7.2. The <span class="guilabel"><strong>Policies</strong></span> Tab</a></span></dt><dt><span class="section"><a href="ch23s07s03.html">23.7.3. The <span class="guilabel"><strong>Access Control</strong></span> Tab</a></span></dt><dt><span class="section"><a href="ch23s07s04.html">23.7.4. The <span class="guilabel"><strong>Printer</strong></span> and <span class="guilabel"><strong>Job Options</strong></span>Tab</a></span></dt></dl></dd><dt><span class="section"><a href="s1-printing-managing.html">23.8. Managing Print Jobs</a></span></dt><dt><span class="section"><a href=
"s1-printing-additional-resources.html">23.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-printing-additional-resources.html#s2-printing-installed-docs">23.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-printing-useful-websites.html">23.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Automated_Tasks.html">24. Automated Tasks</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Automated_Tasks.html#s1-autotasks-cron">24.1. Cron</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Automated_Tasks.html#s2-autotasks-cron-configuring">24.1.1. Configuring Cron Tasks</a></span></dt><dt><span class="section"><a href="ch-Automated_Tasks.html#s2-autotasks-cron-access">24.1.2. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="ch-Automated_Tasks.html#s2-autotasks-cron-service">24.1.3. Starting and Stopping the Service</a></span
></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-at-batch.html">24.2. At and Batch</a></span></dt><dd><dl><dt><span class="section"><a href="s1-autotasks-at-batch.html#s2-autotasks-at-configuring">24.2.1. Configuring At Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">24.2.2. Configuring Batch Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-viewing.html">24.2.3. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-commandline-options.html">24.2.4. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-controlling-access.html">24.2.5. Controlling Access to At and Batch</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-service.html">24.2.6. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">24.3. Additional Re
sources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-autotasks-additional-resources.html#s2-autotasks-installed-docs">24.3.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Log_Files.html">25. Log Files</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Log_Files.html#s1-logfiles-locating">25.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="s1-logfiles-viewing.html">25.2. Viewing Log Files</a></span></dt><dt><span class="section"><a href="s1-logfiles-adding.html">25.3. Adding a Log File</a></span></dt><dt><span class="section"><a href="s1-logfiles-examining.html">25.4. Monitoring Log Files</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">26. Gathering System Information</a></span></dt><dd><dl><dt><span class="section"
><a href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">26.1. System Processes</a></span></dt><dt><span class="section"><a href="s1-sysinfo-memory-usage.html">26.2. Memory Usage</a></span></dt><dt><span class="section"><a href="s1-sysinfo-filesystems.html">26.3. File Systems</a></span></dt><dt><span class="section"><a href="s1-sysinfo-hardware.html">26.4. Hardware</a></span></dt><dt><span class="section"><a href="s1-sysinfo-additional-resources.html">26.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">26.5.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-OProfile.html">27. OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OProfile.html#s1-oprofile-overview-tools">27.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="s1-oprofile-configuring.html">27.2. Configuring OProfil
e</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">27.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">27.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-starting-separate.html">27.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-starting.html">27.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">27.4. Saving Data</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">27.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">27.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">27.5.2. Us
ing <code class="command">opreport</code> on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">27.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">27.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">27.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">27.7. Example Usage</a></span></dt><dt><span class="section"><a href="s1-oprofile-gui.html">27.8. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-additional-resources.html">27.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-additional-resources.html#s1-oprofile-installed-docs">27.9.1. Installed Docs</a></span></dt><dt><span cla
ss="section"><a href="s2-oprofile-useful-websites.html">27.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-abrt.html">28. ABRT</a></span></dt><dd><dl><dt><span class="section"><a href="ch-abrt.html#id883853">28.1. Overview</a></span></dt><dt><span class="section"><a href="ch28s02.html">28.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="configuring.html">28.3. Configuring ABRT</a></span></dt><dt><span class="section"><a href="ch28s04.html">28.4. Plugins and Sending Crash Reports</a></span></dt><dt><span class="section"><a href="ch28s05.html">28.5. Using the Command Line Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch28s05.html#id648054">28.5.1. Viewing Crashes</a></span></dt><dt><span class="section"><a href="ch28s05s02.html">28.5.2. Reporting Crashes</a></span></dt><dt><span class="section"><a href="ch28s05s03.html">28.5.3. Deleting Crashes</a></span></dt></dl></dd></dl></dd
></dl></dd><dt><span class="part"><a href="pt-kernel-configuration.html">V. Kernel and Driver Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Manually_Upgrading_the_Kernel.html">29. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">29.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">29.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">29.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">29.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">29.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">29.6. Verifying the Boot Loader</a></span></dt><dd><dl>
<dt><span class="section"><a href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">29.6.1. Configuring the GRUB Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-iseries.html">29.6.2. Configuring the <span class="trademark">OS/400</span>® Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-pseries.html">29.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-General_Parameters_and_Modules.html">30. General Parameters and Modules</a></span></dt><dd><dl><dt><span class="section"><a href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">30.1. Kernel Module Utilities</a></span></dt><dt><span class="section"><a href="s1-kernel-modules-persistant.html">30.2. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="s1-modules-parameters-specifying.html">30.3. Specifying Module Parameters</a></span></dt><dt><span class
="section"><a href="s1-modules-scsi.html">30.4. Storage parameters</a></span></dt><dt><span class="section"><a href="s1-modules-ethernet.html">30.5. Ethernet Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="s1-modules-ethernet.html#s2-modules-multiple-eth">30.5.1. Using Multiple Ethernet Cards</a></span></dt><dt><span class="section"><a href="s2-modules-bonding.html">30.5.2. The Channel Bonding Module</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">30.6. 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_Draft_Documentation/0.1/html/Deployment_Guide/ix01.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ix01.html
new file mode 100644
index 0000000..f181626
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/ix01.html
@@ -0,0 +1,3 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image
_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id579160"><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>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="indext
erm" href="s2-email-mta-fetchmail.html#s3-email-fetchmail-configuration-user">User Options</a></dt></dl></dd><dt> .procmailrc , <a class="indexterm" href="s1-email-mda.html#s2-email-procmail-configuration">Procmail Configuration</a></dt><dt> /dev/oprofile/ , <a class="indexterm" href="s1-oprofile-dev-oprofile.html">Understanding /dev/oprofile/ </a></dt><dt> /dev/shm , <a class="indexterm" href="s1-sysinfo-filesystems.html">File Systems</a></dt><dt> /etc/httpd/conf/httpd.conf , <a class="indexterm" href="s1-apache-config-ui.html">Apache HTTP Server Configuration</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="ch10s02s03.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/cron , <a class
="indexterm" href="ch-Automated_Tasks.html#s2-autotasks-cron-configuring">Configuring Cron Tasks</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt> (see OProfile)</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#id603215">Configuring Access Control</a></dt><dt>in SSSD, rules, <a class="indexterm" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#id603215">Configuring Access Control</a></dt></dl></dd><dt> AccessFileName </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Action </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddDescription </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apac
he-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddEncoding </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddHandler </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddIcon </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddIconByEncoding </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddIconByType </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>adding</dt><dd><dl><dt>gro
up, <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> AddLanguage </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AddType </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Alias </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Allow </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> AllowOverride </dt><dd><dl><dt>Apache configuration directive, <a clas
s="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>Apache (see Apache HTTP Server)</dt><dt>Apache HTTP Server</dt><dd><dl><dt>1.3</dt><dd><dl><dt>migration to 2.0, <a class="indexterm" href="s3-httpd-v2-mig.html">Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></dt></dl></dd><dt>2.0</dt><dd><dl><dt>migration from 1.3, <a class="indexterm" href="s3-httpd-v2-mig.html">Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></dt><dt>MPM specific directives, <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt>2.2</dt><dd><dl><dt>2.0, <a class="indexterm" href="s1-httpd-mig.html">Migrating Apache HTTP Server Configuration Files</a></dt><dt>features of, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s2-httpd-v2-features">Features of Apache HTTP Server 2.2</a></dt><dt>migration from 2.0, <a class="indexterm" href="s1-httpd-mig.html
#s1-httpd-v22-mig">Migrating Apache HTTP Server 2.0 Configuration Files</a></dt><dt>migration to 2.2, <a class="indexterm" href="s1-httpd-mig.html">Migrating Apache HTTP Server Configuration Files</a></dt></dl></dd><dt>additional resources, <a class="indexterm" href="s1-apache-additional-resources.html">Additional Resources</a></dt><dd><dl><dt>useful websites, <a class="indexterm" href="s1-apache-additional-resources.html#s2-apache-additional-resources-web">Useful Websites</a></dt></dl></dd><dt>configuration, <a class="indexterm" href="s1-apache-config.html">Configuration Directives in httpd.conf </a></dt><dt>introducing, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html">The Apache HTTP Server</a></dt><dt>log files</dt><dd><dl><dt> /var/log/httpd/error_log , <a class="indexterm" href="s1-apache-config.html">Configuration Directives in httpd.conf </a></dt><dt>combined log file format, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configurat
ion Tips</a></dt><dt>format of, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt>troubleshooting with, <a class="indexterm" href="s1-apache-config.html">Configuration Directives in httpd.conf </a>, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt>using log analyzer tools with, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>migration to 2.0, <a class="indexterm" href="s3-httpd-v2-mig.html">Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></dt><dd><dl><dt>bind addresses and ports, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-port">Interface and Port Binding</a></dt><dt>content negotiation, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-mig-main-cont">Content Negotiation</a></dt><dt>directory indexing, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-mig
-main-dirindex">Directory Indexing</a></dt><dt>DSO Support, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-dso">Dynamic Shared Object (DSO) Support</a></dt><dt>error documents, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-mig-main-error">Error Documents</a></dt><dt>LDAP, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-mod-ldapz">The mod_authz_ldap Module</a></dt><dt>logging, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-mig-main-log">Logging</a></dt><dt>module system changes, <a class="indexterm" href="s3-httpd-v2-mig.html#s2-httpd-v2-mig-mod">Modules and Apache HTTP Server 2.0</a></dt><dt> mod_auth_db , <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-mod-dbm">The mod_auth_dbm and mod_auth_db Modules</a></dt><dt> mod_auth_dbm , <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-mod-dbm">The mod_auth_dbm and mod_auth_db Modules</a></dt><dt> mod_include , <a class="indexterm" href="s3-httpd-v2
-mig.html#s3-httpd-v2-mig-mod-include">The mod_include Module</a></dt><dt> mod_perl , <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-mod-perl">The mod_perl Module</a></dt><dt> mod_proxy , <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-mod-proxy">The mod_proxy Module</a></dt><dt> mod_ssl , <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-mod-ssl">The mod_ssl Module</a></dt><dt>PHP, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-mod-php">PHP</a></dt><dt>removed directives, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-other">Other Global Environment Changes</a></dt><dt>server-pool size, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-pool">Server-Pool Size Regulation</a></dt><dt> SuexecUserGroup , <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-mod-suexec">The suexec Module</a>, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuratio
n Tips</a></dt><dt> UserDir directive, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-mig-main-map"> UserDir Mapping</a></dt><dt>virtual host configuration, <a class="indexterm" href="s3-httpd-v2-mig.html#s2-httpd-v2-mig-virtual">Virtual Host Configuration</a></dt></dl></dd><dt>migration to 2.2, <a class="indexterm" href="s1-httpd-mig.html">Migrating Apache HTTP Server Configuration Files</a></dt><dt>Multi-Processing Modules</dt><dd><dl><dt>activating worker MPM, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-pool">Server-Pool Size Regulation</a></dt><dt> prefork , <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-pool">Server-Pool Size Regulation</a></dt><dt> worker , <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-pool">Server-Pool Size Regulation</a></dt></dl></dd><dt>reloading, <a class="indexterm" href="s1-apache-startstop.html">Starting and Stopping httpd </a></dt><dt>restarting, <a class="indexterm" href="s1-apa
che-startstop.html">Starting and Stopping httpd </a></dt><dt>running without security, <a class="indexterm" href="s1-apache-virtualhosts.html">Virtual Hosts</a></dt><dt>securing, <a class="indexterm" href="s2-secureserver-overview-certs.html">An Overview of Certificates and Security</a></dt><dt>server status reports, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt>starting, <a class="indexterm" href="s1-apache-startstop.html">Starting and Stopping httpd </a></dt><dt>stopping, <a class="indexterm" href="s1-apache-startstop.html">Starting and Stopping httpd </a></dt><dt>troubleshooting, <a class="indexterm" href="s1-apache-config.html">Configuration Directives in httpd.conf </a></dt></dl></dd><dt>Apache HTTP Server Keys</dt><dd><dl><dt>use new keys, <a class="indexterm" href="s1-use-new-key.html">How to configure the server to use the new key</a></dt></dl></dd><dt>APXS Apache utility, <a class="indexterm" href="s1-apache-
addmods.html">Adding Modules</a></dt><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 Configuration 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" hr
ef="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="s1-ldap-pam.html">Configuring a System to Authenticate Using OpenLDAP</a>, <a class="indexterm" href="s1-ldap-pam.html#s2-ldap-pamd">PAM and LDAP</a>, <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</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 cla
ss="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>Automated Tasks, <a class="indexterm" href="ch-Automated_Tasks.html">Automated Tasks</a></dt></dl></div><div class="indexdiv"><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 (se
e BIND)</dt><dt>BIND</dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-bind-additional-resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-bind-additional-resources.html#s2-bind-installed-docs">Installed Documentation</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 files</dt><dd><dl><dt> /etc/named.conf , <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"> /etc/named.conf </a></dt><dt> /var/named/ directory, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-bind">BIND as a Nameserver</a></dt><dt>BIND as a Nameserver, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bi
nd-introduction-bind">BIND as a Nameserver</a></dt><dt>zone files, <a class="indexterm" href="s1-bind-zone.html">Zone Files</a></dt></dl></dd><dt>configuration of</dt><dd><dl><dt>reverse name resolution, <a class="indexterm" href="s2-bind-configuration-zone-reverse.html">Reverse Name Resolution Zone Files</a></dt><dt>zone file directives, <a class="indexterm" href="s1-bind-zone.html#s2-bind-zone-directives">Zone File Directives</a></dt><dt>zone file examples, <a class="indexterm" href="s2-bind-zone-examples.html">Example Zone File</a></dt><dt>zone file resource records, <a class="indexterm" href="s3-bind-zone-rr.html">Zone File Resource Records</a></dt><dt> zone statements sample, <a class="indexterm" href="s1-bind-namedconf.html#s3-bind-configuration-named-zone">Sample zone Statements</a></dt></dl></dd><dt>features, <a class="indexterm" href="s1-bind-features.html">Advanced Features of BIND</a></dt><dd><dl><dt>DNS enhancements, <a class="indexterm" href="s1-bind-features.ht
ml#s2-bind-features-protocol">DNS Protocol Enhancements</a></dt><dt>IPv6, <a class="indexterm" href="s2-bind-features-ipv6.html">IP version 6</a></dt><dt>multiple views, <a class="indexterm" href="s2-bind-features-views.html">Multiple Views</a></dt><dt>security, <a class="indexterm" href="s2-bind-features-security.html">Security</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="ch-The_BIND_DNS_Server.html">The BIND DNS Server</a>, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s1-bind-introduction">Introduction to DNS</a></dt><dt> named daemon, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-bind">BIND as a Nameserver</a></dt><dt>nameserver</dt><dd><dl><dt>definition of, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s1-bind-introduction">Introduction to DNS</a></dt></dl></dd><dt>nameserver types</dt><dd><dl><dt>caching-only, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">Namese
rver Types</a></dt><dt>forwarding, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">Nameserver Types</a></dt><dt>master, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">Nameserver Types</a></dt><dt>slave, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">Nameserver Types</a></dt></dl></dd><dt> rndc program, <a class="indexterm" href="s1-bind-rndc.html">Using rndc </a></dt><dd><dl><dt> /etc/rndc.conf , <a class="indexterm" href="s2-bind-rndc-configuration-rndcconf.html">Configuring /etc/rndc.conf </a></dt><dt>command line options, <a class="indexterm" href="s2-bind-rndc-options.html">Command Line Options</a></dt><dt>configuring keys, <a class="indexterm" href="s2-bind-rndc-configuration-rndcconf.html">Configuring /etc/rndc.conf </a></dt><dt>configuring named to use, <a class="indexterm" href="s1-bind-rndc.html#s2-bind-rndc-configuration-namedconf">Configurin
g /etc/named.conf </a></dt></dl></dd><dt>root nameserver</dt><dd><dl><dt>definition of, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s1-bind-introduction">Introduction to DNS</a></dt></dl></dd><dt>zones</dt><dd><dl><dt>definition of, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-zones">Nameserver Zones</a></dt></dl></dd></dl></dd><dt>bind</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>related books, <a class="indexterm" href="s2-bind-related-books.html">Related Books</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 kernel module</dt><dd><dl><dt>sysfs, <a class="indexterm" href="s2-modules-bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><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><dt> BrowserMatch </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>CA (see secure server)</dt><dt>cache directives for Apache, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> CacheNegotiatedDocs </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>caching-only nameserver (see BIND)</dt><dt>CGI scripts</dt><dd><dl><dt>allowing execution outside cgi-bin , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a><
/dt><dt>outside the ScriptAlias , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</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>bonding directives, <a class="indexterm" href="s2-modules-bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt><dt>bonding options, <a class="indexterm" href="s2-modules-bonding.html">The Channel Bonding Module</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="s2-modules-bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>channel bonding interface (see kernel module)</dt><dt>chara
cter 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> chkconfig (see services configuration)</dt><dt>command line options</dt><dd><dl><dt>printing from, <a class="indexterm" href="s1-printing-managing.html">Managing Print Jobs</a></dt></dl></dd><dt>configuration</dt><dd><dl><dt>Apache HTTP Server, <a class="indexterm" href="s1-apache-config.html">Configuration Directives in httpd.conf </a></dt><dt>virtual hosts, <a class="indexterm" href="s1-apache-virtualhosts.html">Virtual Hosts</a></dt></dl></dd><dt>configuration directives, Apache, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dd><dl><dt> AccessFileName , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Action , <a class="indexterm
" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> AddDescription , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> AddEncoding , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> AddHandler , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> AddIcon , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> AddIconByEncoding , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> AddIconByType , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> AddLanguage , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> AddType , <a class="indexterm" href="s1-apache-config.html#s2-ap
ache-tips">General Configuration Tips</a></dt><dt> Alias , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Allow , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> AllowOverride , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> BrowserMatch , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> CacheNegotiatedDocs , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> CustomLog , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> DefaultIcon , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> DefaultType , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a
></dt><dt> Deny , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Directory , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> DirectoryIndex , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> DocumentRoot , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ErrorDocument , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ErrorLog , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ExtendedStatus , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt>for cache functionality, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Group , <a class="i
ndexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> HeaderName , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> HostnameLookups , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> IfDefine , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> IfModule , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Include , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> IndexIgnore , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> IndexOptions , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> KeepAlive , <a class="indexterm" href="s1-apache-config.html#s2-apac
he-tips">General Configuration Tips</a></dt><dd><dl><dt>(see also KeepAliveTimeout )</dt><dt>troubleshooting, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> KeepAliveTimeout , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> LanguagePriority , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Listen , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> LoadModule , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Location , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> LogFormat </dt><dd><dl><dt>format options, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> LogLevel
, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> MaxClients , <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt><dt> MaxKeepAliveRequests , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> MaxRequestsPerChild , <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt><dt> MaxSpareServers , <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt><dt> MaxSpareThreads , <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt><dt> MinSpareServers , <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt><dt> MinSpareThreads , <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt><dt> NameV
irtualHost , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Options , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Order , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> PidFile , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Proxy , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ProxyRequests , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ReadmeName , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> Redirect , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ScriptAlias , <a class="indexterm" href="s1-apache-config.ht
ml#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerAdmin , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerName , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerRoot , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerSignature , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ServerTokens , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> SetEnvIf , <a class="indexterm" href="s2-apache-sslcommands.html">Configuration Directives for SSL</a></dt><dt>SSL configuration, <a class="indexterm" href="s2-apache-sslcommands.html">Configuration Directives for SSL</a></dt><dt> StartServers , <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Dir
ectives</a></dt><dt> SuexecUserGroup , <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-mod-suexec">The suexec Module</a>, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ThreadsPerChild , <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt><dt> Timeout , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> TypesConfig , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> UseCanonicalName , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> User , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> UserDir , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> VirtualHost , <a class="indexterm" h
ref="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>Configuration File Changes, <a class="indexterm" href="ch-yum.html#sec-Preserving_Configuration_File_Changes">Preserving Configuration File Changes</a></dt><dt>Cron, <a class="indexterm" href="ch-Automated_Tasks.html">Automated Tasks</a></dt><dt>cron</dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-autotasks-additional-resources.html">Additional Resources</a></dt><dt>configuration file, <a class="indexterm" href="ch-Automated_Tasks.html#s2-autotasks-cron-configuring">Configuring Cron Tasks</a></dt><dt>example crontabs, <a class="indexterm" href="ch-Automated_Tasks.html#s2-autotasks-cron-configuring">Configuring Cron Tasks</a></dt><dt>user-defined tasks, <a class="indexterm" href="ch-Automated_Tasks.html#s2-autotasks-cron-configuring">Configuring Cron Tasks</a></dt></dl></dd><dt> crontab , <a class="indexterm" href="ch-Automated_Tasks.html#s2-autotasks-cron-configuri
ng">Configuring Cron Tasks</a></dt><dt>CUPS, <a class="indexterm" href="ch-Printer_Configuration.html">Printer Configuration</a></dt><dt> CustomLog </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd></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_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> DefaultIcon </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl>
</dd><dt> DefaultType </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</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-Specifying_Multiple_Domains">Specifying 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/sys/net/ </a></dt></dl></dd><dt> Deny </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>desktop environments (see X)</dt><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="ch10s02s03.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="ch10s02s03.html">Starting and Stopping the Server</a></dt><dt>dhcpd6.conf, <a class="indexterm" href="s1-dhcp_for_ipv6_dhcpv6.html">DHCP for IPv6 (DHCPv6)</a></dt><dt>DHCPv6, <a class="indexterm" href="s
1-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="ch10s02s03.html">Starting and Stopping the Server</a></dt><dt>stopping the server, <a class="indexterm" href="ch10s02s03.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="ch10s02s03.html">Starting and Stopping the Server</a></dt><dt> dhcrelay , <a class="indexterm" href="dhcp-relay-agent.html">DHCP Relay Agent</a></dt><dt> Directory </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> DirectoryIndex </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>display m
anagers (see X)</dt><dt>DNS, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s1-bind-introduction">Introduction to DNS</a></dt><dd><dl><dt>(see also BIND)</dt><dt>introducing, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s1-bind-introduction">Introduction to DNS</a></dt></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> DocumentRoot </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt>changing, <a class="indexterm" href="s1-apache-virtualhosts.html">Virtual Hosts</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>DSOs</dt><dd><dl><dt>loading, <a class="indexterm" href="s1-apache-addmods.html">Adding Modules</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><d
t>Postfix, <a class="indexterm" href="s2-email-mta-postfix.html">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>Dovecot, <a class="indexterm" href="ch-email.html#s3-email-protocols-dovecot">Dovecot</a></dt><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="s1-email-mta.html#s2-email-mta-sendmail">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 Tranport 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> ErrorDocume
nt </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ErrorLog </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>Ethernet (see network)</dt><dt>Ethernet module (see kernel module)</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="indexter
m" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt><dt> ExtendedStatus </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd></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 Option
s</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></dl></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)</d
t></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> findsmb , <a class="indexterm" href="s1-samba-connect-share.html#s2-samba-connect-share-cmdline">Command Line</a></dt><dt> findsmb program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt>forwarding nameserver (see BIND)</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.htm
l">Memory Usage</a></dt><dt>FTP, <a class="indexterm" href="ch-FTP.html">FTP</a></dt><dd><dl><dt>(see also vsftpd )</dt><dt>active mode, <a class="indexterm" href="ch-FTP.html#s2-ftp-protocol-multiport">Multiple Ports, Multiple Modes</a></dt><dt>command port, <a class="indexterm" href="ch-FTP.html#s2-ftp-protocol-multiport">Multiple Ports, Multiple Modes</a></dt><dt>data port, <a class="indexterm" href="ch-FTP.html#s2-ftp-protocol-multiport">Multiple Ports, Multiple Modes</a></dt><dt>definition of, <a class="indexterm" href="ch-FTP.html">FTP</a></dt><dt>introducing, <a class="indexterm" href="ch-FTP.html#s1-ftp-protocol">The File Transfer Protocol</a></dt><dt>passive mode, <a class="indexterm" href="ch-FTP.html#s2-ftp-protocol-multiport">Multiple Ports, Multiple Modes</a></dt><dt>server software</dt><dd><dl><dt> Red Hat Content Accelerator , <a class="indexterm" href="s1-ftp-servers.html">FTP Servers</a></dt><dt> vsftpd , <a class="indexterm" href="s1-ftp-servers.html">FTP
Servers</a></dt></dl></dd></dl></dd></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>GNOME, <a class="indexterm" href="s1-x-clients.html#s2-x-clients-desktop">Desktop Environments</a></dt><dd><dl><dt>(see also X)</dt></dl></dd><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 Viewer )</dt><dt> gnome-system-monitor , <a class="indexterm" href="ch-Gathering_System_Information.html#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.html">Checking a Package's Signature</a></dt></dl></dd><dt> Group </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>group confi/sbin/nologinguration</dt><dd><dl><dt>adding groups, <a class="indexterm" href=
"ers_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="ers_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="ers_and_Groups.html#s2-redhat-config-users-group-properties">Modifying Group Properties</a></dt><dt>modifying group properties, <a class="indexterm" href="ers_and_Groups.html#s2-redhat-config-users-group-properties">Modifying Group Properties</a></dt><dt>viewing list of groups, <a class="indexterm" href="ers_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="ers_and_Groups.html">Users and Groups</a></dt><dt>introducing, <a class="indexterm" href="ers_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.html">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="inde
xterm" 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> HeaderName </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> HostnameLookups
</dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> HTTP Configuration Tool </dt><dd><dl><dt>error log, <a class="indexterm" href="s2-httpd-default-settings.html#s3-httpd-logging">Logging</a></dt><dt>modules, <a class="indexterm" href="s1-apache-config-ui.html">Apache HTTP Server Configuration</a></dt><dt>transfer log, <a class="indexterm" href="s2-httpd-default-settings.html#s3-httpd-logging">Logging</a></dt></dl></dd><dt>HTTP directives</dt><dd><dl><dt> DirectoryIndex , <a class="indexterm" href="s2-httpd-default-settings.html#s3-httpd-site-config">Site Configuration</a></dt><dt> ErrorDocument , <a class="indexterm" href="s2-httpd-default-settings.html#s3-httpd-site-config">Site Configuration</a></dt><dt> ErrorLog , <a class="indexterm" href="s2-httpd-default-settings.html#s3-httpd-logging">Logging</a></dt><dt> HostnameLookups , <a class="indexterm" href="s2-http
d-default-settings.html#s3-httpd-logging">Logging</a></dt><dt> Listen , <a class="indexterm" href="s1-apache-config-ui.html#s2-httpd-basic-settings">Basic Settings</a></dt><dt> LogFormat , <a class="indexterm" href="s2-httpd-default-settings.html#s3-httpd-logging">Logging</a></dt><dt> LogLevel , <a class="indexterm" href="s2-httpd-default-settings.html#s3-httpd-logging">Logging</a></dt><dt> Options , <a class="indexterm" href="s2-httpd-default-settings.html#s3-httpd-site-config">Site Configuration</a></dt><dt> ServerAdmin , <a class="indexterm" href="s1-apache-config-ui.html#s2-httpd-basic-settings">Basic Settings</a></dt><dt> ServerName , <a class="indexterm" href="s1-apache-config-ui.html#s2-httpd-basic-settings">Basic Settings</a></dt><dt> TransferLog , <a class="indexterm" href="s2-httpd-default-settings.html#s3-httpd-logging">Logging</a></dt></dl></dd><dt> httpd , <a class="indexterm" href="s1-apache-config-ui.html">Apache HTTP Server Configuration</a></dt><dt> httpd.co
nf (see configuration directives, Apache)</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> IfDefine </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ifdown , <a class="indexterm" href="s1-networkscripts-control.html">Interface Control Scripts</a></dt><dt> IfModule </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ifup , <a class="indexterm" href="s1-networkscripts-control.html">Interface Control Scripts</a></dt><dt> Include </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-confi
g.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> IndexIgnore </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> IndexOptions </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><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 pa
ckages, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding RPM Packages</a></dt></dl></dd><dt> insmod , <a class="indexterm" href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">Kernel Module Utilities</a></dt><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>KDE, <a class="indexterm" href="s1-x-clients.html#s2-x-clients-desktop">Desktop Environments</a></dt><dd><dl><dt>(see also X)</dt></dl></dd><dt> KeepAlive </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apac
he-tips">General Configuration Tips</a></dt></dl></dd><dt> KeepAliveTimeout </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</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></dl></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 bonding</dt><dd><dl><dt>sysfs, <a class="indexterm" href="s2-modules-bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>kernel module</dt><dd><dl><dt>/etc/sysconfig/modules/
, <a class="indexterm" href="s1-kernel-modules-persistant.html">Persistent Module Loading</a></dt><dt>bonding kernel module, <a class="indexterm" href="s2-modules-bonding.html">The Channel Bonding Module</a></dt><dd><dl><dt>bonding directives, <a class="indexterm" href="s2-modules-bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="s2-modules-bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>channel bonding, <a class="indexterm" href="s2-modules-bonding.html">The Channel Bonding Module</a></dt><dt>channel bonding interface, <a class="indexterm" href="s2-modules-bonding.html">The Channel Bonding Module</a></dt><dt>commands</dt><dd><dl><dt>group of, <a class="indexterm" href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">Kernel Module Utilities</a></dt></dl></dd><dt>Ethernet module, <a class="indexterm" href="s1-modules-ethernet.h
tml">Ethernet Parameters</a></dt><dd><dl><dt>supporting multiple cards, <a class="indexterm" href="s1-modules-ethernet.html#s2-modules-multiple-eth">Using Multiple Ethernet Cards</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="ch-General_Parameters_and_Modules.html">General Parameters and Modules</a></dt><dt>listing, <a class="indexterm" href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>loading, <a class="indexterm" href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>module parameters</dt><dd><dl><dt>specifying, <a class="indexterm" href="s1-modules-parameters-specifying.html">Specifying Module Parameters</a></dt><dt>supplying, <a class="indexterm" href="s1-modules-parameters-specifying.html">Specifying Module Parameters</a></dt></dl></dd><dt>module-init-tools, <a class="indexterm" href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">Kerne
l Module Utilities</a></dt><dt>NIC module, <a class="indexterm" href="s1-modules-ethernet.html">Ethernet Parameters</a></dt><dt>persistent loading, <a class="indexterm" href="s1-kernel-modules-persistant.html">Persistent Module Loading</a></dt><dt>SCSImodule</dt><dd><dl><dt>parameters, <a class="indexterm" href="s1-modules-scsi.html">Storage parameters</a></dt></dl></dd><dt>types of, <a class="indexterm" href="ch-General_Parameters_and_Modules.html">General Parameters and Modules</a></dt><dt>unload, <a class="indexterm" href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>utilities, <a class="indexterm" href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">Kernel Module Utilities</a></dt></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 Pack
ages</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_Configuration.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><dt> kwin , <a class="indexterm" href="s2-x-clients-winmanagers.html">Window Managers</a></dt><dd><dl><dt>(see also X)</d
t></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt> LanguagePriority </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>LDAP</dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-ldap-additional-resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-ldap-additional-resources.html#s2-ldap-installed-docs">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="s2-ldap-related-books.html">Related Books</a></dt><dt>useful websites, <a class="indexterm" href="s2-ldap-additional-resources-web.html">Useful Websites</a></dt></dl></dd><dt>advantages of, <a class="indexterm" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html#s1-ldap-adv">Why Use LDAP?</a></dt><dt>applications</dt><dd><dl><dt> ldapadd , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP D
aemons and Utilities</a></dt><dt> ldapdelete , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt> ldapmodify , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt> ldappasswd , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt> ldapsearch , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt>OpenLDAP suite, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt> slapadd , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt> slapcat , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt> slapd , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt> slapindex , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP D
aemons and Utilities</a></dt><dt> slappasswd , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt> slurpd , <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt>utilities, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt></dl></dd><dt>authentication using, <a class="indexterm" href="s1-ldap-pam.html">Configuring a System to Authenticate Using OpenLDAP</a></dt><dd><dl><dt> Authentication Configuration Tool , <a class="indexterm" href="s1-ldap-pam.html">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>editing /etc/ldap.conf , <a class="indexterm" href="s1-ldap-pam.html">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>editing /etc/nsswitch.conf , <a class="indexterm" href="s1-ldap-pam.html">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>editing /etc/openldap/ldap.conf , <a class="indexterm" href="s1
-ldap-pam.html">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>editing slapd.conf , <a class="indexterm" href="s1-ldap-pam.html">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>packages, <a class="indexterm" href="s1-ldap-pam.html">Configuring a System to Authenticate Using OpenLDAP</a></dt><dt>PAM, <a class="indexterm" href="s1-ldap-pam.html#s2-ldap-pamd">PAM and LDAP</a></dt><dt>setting up clients, <a class="indexterm" href="s1-ldap-pam.html">Configuring a System to Authenticate Using OpenLDAP</a></dt></dl></dd><dt>client applications, <a class="indexterm" href="s2-ldap-applications.html">LDAP Client Applications</a></dt><dt>configuration files</dt><dd><dl><dt> /etc/ldap.conf , <a class="indexterm" href="s1-ldap-files.html">OpenLDAP Configuration Files</a></dt><dt> /etc/openldap/ldap.conf , <a class="indexterm" href="s1-ldap-files.html">OpenLDAP Configuration Files</a></dt><dt> /etc/openldap/schema/ directory, <a class="indexterm" href="s1-
ldap-files.html">OpenLDAP Configuration Files</a>, <a class="indexterm" href="s1-ldap-files-schemas.html">The /etc/openldap/schema/ Directory</a></dt><dt> /etc/openldap/slapd.conf , <a class="indexterm" href="s1-ldap-files.html">OpenLDAP Configuration Files</a>, <a class="indexterm" href="s1-ldap-quickstart.html#s2-ldap-files-slapd-conf">Editing /etc/openldap/slapd.conf </a></dt></dl></dd><dt>daemons, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dt>definition of, <a class="indexterm" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html">Lightweight Directory Access Protocol (LDAP)</a></dt><dt>LDAPv2, <a class="indexterm" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html">Lightweight Directory Access Protocol (LDAP)</a></dt><dt>LDAPv3, <a class="indexterm" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html">Lightweight Directory Access Protocol (LDAP)</a></dt><dt>LDIF</dt><dd><dl><dt>format of, <a class="indext
erm" href="s1-ldap-terminology.html">LDAP Terminology</a></dt></dl></dd><dt>OpenLDAP features, <a class="indexterm" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html#s1-ldap-v3">OpenLDAP Features</a></dt><dt>setting up, <a class="indexterm" href="s1-ldap-quickstart.html">OpenLDAP Setup Overview</a></dt><dd><dl><dt>migrating older directories, <a class="indexterm" href="s1-ldap-migrate.html">Migrating Directories from Earlier Releases</a></dt></dl></dd><dt>terminology, <a class="indexterm" href="s1-ldap-terminology.html">LDAP Terminology</a></dt><dt>upgrading directories, <a class="indexterm" href="s1-ldap-migrate.html">Migrating Directories from Earlier Releases</a></dt><dt>using with Apache HTTP Server, <a class="indexterm" href="s2-ldap-other-apps.html">PHP4, LDAP, and the Apache HTTP Server</a></dt><dt>using with NSS, <a class="indexterm" href="s1-ldap-daemonsutils.html#s2-ldap-pam-nss">NSS, PAM, and LDAP</a></dt><dt>using with PAM, <a class="indexterm" href="s1-ld
ap-daemonsutils.html#s2-ldap-pam-nss">NSS, PAM, and LDAP</a></dt><dt>using with PHP4, <a class="indexterm" href="s2-ldap-other-apps.html">PHP4, LDAP, and the Apache HTTP Server</a></dt></dl></dd><dt> ldapadd command, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> ldapdelete command, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> ldapmodify command, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> ldappasswd command, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> ldapsearch command, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></
dd><dt>Lightweight Directory Access Protocol (see LDAP)</dt><dt> Listen </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> LoadModule </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Location </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</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>description, <a class="indexterm" href="ch-Log_Files.html">Log Files</a></dt><dt>locating, <a class="indexterm" href="ch-Log_Files.html#s1-logfiles-locating">Locating Log Files</a></dt><dt>monitoring, <a class="indexterm" href="s1-logfiles-examining.html">Monitoring Log Files</a></dt><d
t>rotating, <a class="indexterm" href="ch-Log_Files.html#s1-logfiles-locating">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> LogFormat </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> LogLevel </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> logrotate , <a class="indexterm" href="ch-Log_Files.html#s1-logfiles-locating">Locating Log Files</a></dt><dt> lpd , <a class="indexterm" href="ch-Printer_Configuration.html">Printer Configuration</a></dt><d
t> lsmod , <a class="indexterm" href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt> lspci , <a class="indexterm" href="s2-proc-pci.html"> /proc/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="s1-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt><dt>Mail User Agent, <a class="indexterm" href="s1-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a> (see email)</dt><dt>master nameserver (see BIND)</dt><dt> MaxClients </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> MaxKeepAliveRequests </dt><dd><dl><dt>Apache configuration directive, <a class="
indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> MaxRequestsPerChild </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> MaxSpareServers </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> MaxSpareThreads </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt>MDA (see Mail Delivery Agent)</dt><dt>memory usage, <a class="indexterm" href="s1-sysinfo-memory-usage.html">Memory Usage</a></dt><dt> metacity , <a class="indexterm" href="s2-x-clients-winmanagers.html">Window Managers</a></dt><dd><dl><dt>(see also X)</dt></dl></dd><dt> MinSpareServers </dt><dd><dl><dt>Apache configuration directive
, <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> MinSpareThreads </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> modprobe , <a class="indexterm" href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>module (see kernel module)</dt><dt>module parameters (see kernel module)</dt><dt>modules</dt><dd><dl><dt>Apache</dt><dd><dl><dt>loading, <a class="indexterm" href="s1-apache-addmods.html">Adding Modules</a></dt><dt>the own, <a class="indexterm" href="s1-apache-addmods.html">Adding Modules</a></dt></dl></dd></dl></dd><dt>MTA (see Mail Transport Agent)</dt><dd><dl><dt>setting default, <a class="indexterm" href="s1-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt><dt>switching with Mail Transport Agent Switcher , <a class="in
dexterm" href="s1-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt></dl></dd><dt>MUA, <a class="indexterm" href="s1-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 configuration, <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-Specifying_Multiple_Domains">Specifying Multiple Domains</a></dt></dl></dd><dt> mwm , <a class="indexterm" href="s2-x-clients-winmanagers.html">Window Managers</a></dt><dd><dl><dt>(see also X)</dt></dl></dd></dl></div><div class="indexdiv"><h
3>N</h3><dl><dt> named daemon (see BIND)</dt><dt> named.conf (see BIND)</dt><dt>nameserver (see BIND)</dt><dt> NameVirtualHost </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> net program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></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.h
tml">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 Interfaces</a></dt><dt>Ethernet, <a class="indexterm" href="s1-networkscripts-interfaces.html#s2-networkscript
s-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="s2-modules-bonding.html">The Channel Bonding Module</a></dt></dl></dd><dt>NIC module</dt><dd><dl><dt>kernel module, <a class="indexterm" href="s1-modules-ethernet.html">Ethernet Parameters</a></dt></dl></dd><dt> nmblookup program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><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="cha
p-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> 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>objects, dynamically shared (see DSOs)</dt><dt> opannotate (see OProfile)</dt><dt> opcontrol (see OProfile)</dt><dt>OpenLDAP (see LDAP)</dt><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-op
enssh-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-ssh-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">Gener
ating 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 Versio
n 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></dl></dd><dt> ophelp , <a class="indexterm" href="s2-oprofile-events.html">Setting Events to Monitor</a></dt><dt> opreport (see OProfile)</dt><dt>OProfile, <a class="indexterm" href="ch-OProfile.html">OProfile</a></dt><dd><dl><dt> /dev/oprofile/ , <a class="indexterm" href="s1-oprofile-dev-oprofile.html">Understanding /dev/oprofile/ </a></dt><dt>additional resources, <a class="indexterm" href="s1-oprofile-additional-resources.html">Additional Resources</a></dt><dt>configuring, <a class="indexterm" href="s1-oprofile-configuring.html">Config
uring OProfile</a></dt><dd><dl><dt>separating profiles, <a class="indexterm" href="s2-oprofile-starting-separate.html">Separating Kernel and User-space Profiles</a></dt></dl></dd><dt>events</dt><dd><dl><dt>sampling rate, <a class="indexterm" href="s2-oprofile-events.html#s3-oprofile-events-sampling">Sampling Rate</a></dt><dt>setting, <a class="indexterm" href="s2-oprofile-events.html">Setting Events to Monitor</a></dt></dl></dd><dt>monitoring the kernel, <a class="indexterm" href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> opannotate , <a class="indexterm" href="s2-oprofile-reading-opannotate.html">Using opannotate </a></dt><dt> opcontrol , <a class="indexterm" href="s1-oprofile-configuring.html">Configuring OProfile</a></dt><dd><dl><dt> --no-vmlinux , <a class="indexterm" href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> --start , <a class="indexterm" href="s1-oprofile-starting.html">Starting a
nd Stopping OProfile</a></dt><dt> --vmlinux= , <a class="indexterm" href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the Kernel</a></dt></dl></dd><dt> ophelp , <a class="indexterm" href="s2-oprofile-events.html">Setting Events to Monitor</a></dt><dt> opreport , <a class="indexterm" href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">Using opreport </a>, <a class="indexterm" href="s2-oprofile-module-output.html">Getting more detailed output on the modules</a></dt><dd><dl><dt>on a single executable, <a class="indexterm" href="s2-oprofile-reading-opreport-single.html">Using opreport on a Single Executable</a></dt></dl></dd><dt> oprofiled , <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile</a></dt><dd><dl><dt>log file, <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile</a></dt></dl></dd><dt>overview of tools, <a class="indexterm" href="ch-OProfile.html#s1-oprofile-overview-tools
">Overview of Tools</a></dt><dt>reading data, <a class="indexterm" href="s1-oprofile-analyzing-data.html">Analyzing the Data</a></dt><dt>saving data, <a class="indexterm" href="s1-oprofile-saving-data.html">Saving Data</a></dt><dt>starting, <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile</a></dt><dt>unit mask, <a class="indexterm" href="s2-oprofile-events.html#s3-oprofile-events-unit-masks">Unit Masks</a></dt></dl></dd><dt> oprofiled (see OProfile)</dt><dt> oprof_start , <a class="indexterm" href="s1-oprofile-gui.html">Graphical Interface</a></dt><dt> Options </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Order </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>OS/400 boot loader</dt><dd><dl><dt>configuration fil
e, <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_Architecture.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-unre
solved-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_Groups.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 Fil
ters</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 with 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="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>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>dependencies, <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_th
e_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 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_Packag
e_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 Information</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.h
tml">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">Searching, 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.html#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.html#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-sh
adow-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> pdbedit program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> PidFile </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</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="s2-email-mta-postfix.html">Postfix</a></dt><dd><dl><dt>default installation, <a class="indexterm" href="s2-email-mta-postfix.html#s3-email-mta-postfix-default">The Default Postfix Installation</a></dt></dl></dd><dt>postfix, <a class="indexterm" href="s1-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt><dt> prefdm
(see X)</dt><dt> printconf (see printer configuration)</dt><dt>printer configuration, <a class="indexterm" href="ch-Printer_Configuration.html">Printer Configuration</a></dt><dd><dl><dt>adding</dt><dd><dl><dt>CUPS (IPP) printer, <a class="indexterm" href="s1-printing-ipp-printer.html">Adding an IPP Printer</a></dt><dt>IPP printer, <a class="indexterm" href="s1-printing-ipp-printer.html">Adding an IPP Printer</a></dt><dt>JetDirect printer, <a class="indexterm" href="s1-printing-jetdirect-printer.html">Adding a JetDirect Printer</a></dt><dt>local printer, <a class="indexterm" href="ch-Printer_Configuration.html#s1-printing-local-printer">Adding a Local Printer</a></dt><dt>Samba (SMB) printer, <a class="indexterm" href="s1-printing-smb-printer.html">Adding a Samba (SMB) Printer</a></dt></dl></dd><dt>cancel print job, <a class="indexterm" href="s1-printing-managing.html">Managing Print Jobs</a></dt><dt>CUPS, <a class="indexterm" href="ch-Printer_Configuration.html">Printer Conf
iguration</a></dt><dt>default printer, <a class="indexterm" href="s1-printing-edit.html">Modifying Existing Printers</a></dt><dt>delete existing printer, <a class="indexterm" href="s1-printing-edit.html">Modifying Existing Printers</a></dt><dt>IPP printer, <a class="indexterm" href="s1-printing-ipp-printer.html">Adding an IPP Printer</a></dt><dt>JetDirect printer, <a class="indexterm" href="s1-printing-jetdirect-printer.html">Adding a JetDirect Printer</a></dt><dt>local printer, <a class="indexterm" href="ch-Printer_Configuration.html#s1-printing-local-printer">Adding a Local Printer</a></dt><dt>managing print jobs, <a class="indexterm" href="s1-printing-managing.html">Managing Print Jobs</a></dt><dt>networked CUPS (IPP) printer, <a class="indexterm" href="s1-printing-ipp-printer.html">Adding an IPP Printer</a></dt><dt>printing from the command line, <a class="indexterm" href="s1-printing-managing.html">Managing Print Jobs</a></dt><dt>Samba (SMB) printer, <a class="indexterm
" href="s1-printing-smb-printer.html">Adding a Samba (SMB) Printer</a></dt><dt>test page, <a class="indexterm" href="s1-printing-test-page.html">Printing a Test Page</a></dt><dt>viewing print spool, command line, <a class="indexterm" href="s1-printing-managing.html">Managing Print Jobs</a></dt></dl></dd><dt> Printer Configuration Tool (see printer configuration)</dt><dt> printtool (see printer configuration)</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/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 de
vices, <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><dt> /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="indexterm" 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/pci </dt><dd><dl><dt>viewing using lspci , <a class="indexterm" href="s2-proc-pci.html"> /proc/pci </a></dt></dl></dd><dt> /proc/PID/ 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/ director
y, <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-fs"> /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></dt><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><d
d><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.ht
ml#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> Proxy </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>proxy server, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt> ProxyRequests </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><
/dl></dd><dt> ps , <a class="indexterm" href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">System Processes</a></dt><dt> public_html directories, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</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> ReadmeName </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> Red Hat RPM Guide , <a class="indexterm" href="s2-rpm-related-books.html">Related Books</a></dt><dt> Redirect </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>removing package groups</dt><dd><dl><dt>re
moving 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> rmmod , <a class="indexterm" href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">Kernel Module Utilities</a></dt><dt>root nameserver (see BIND)</dt><dt> rpcclient program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></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="in
dexterm" 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>conflicts, <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-des
ign">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" href="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>fresh
ening, <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">Checking 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-Ins
talling_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="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> 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>Samba (see Samba)</dt><dd><dl><dt>Abilities, <a class="indexterm" href="ch-Samba.html#s2-samba-abilities">Samba Features</a></dt><dt>Account Informa
tion Databases, <a class="indexterm" href="s1-samba-account-info-dbs.html">Samba Account Information Databases</a></dt><dd><dl><dt> ldapsam , <a class="indexterm" href="s1-samba-account-info-dbs.html">Samba Account Information Databases</a></dt><dt> ldapsam_compat , <a class="indexterm" href="s1-samba-account-info-dbs.html">Samba Account Information Databases</a></dt><dt> mysqlsam , <a class="indexterm" href="s1-samba-account-info-dbs.html">Samba Account Information Databases</a></dt><dt>Plain Text, <a class="indexterm" href="s1-samba-account-info-dbs.html">Samba Account Information Databases</a></dt><dt> smbpasswd , <a class="indexterm" href="s1-samba-account-info-dbs.html">Samba Account Information Databases</a></dt><dt> tdbsam , <a class="indexterm" href="s1-samba-account-info-dbs.html">Samba Account Information Databases</a></dt><dt> xmlsam , <a class="indexterm" href="s1-samba-account-info-dbs.html">Samba Account Information Databases</a></dt></dl></dd><dt>Additional Re
sources, <a class="indexterm" href="s1-samba-resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-samba-resources.html#s2-samba-resources-installed">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="s2-samba-resources-published.html">Related Books</a></dt><dt>useful websites, <a class="indexterm" href="s2-samba-resources-community.html">Useful Websites</a></dt></dl></dd><dt>Backward Compatible Database Backends, <a class="indexterm" href="s1-samba-account-info-dbs.html">Samba Account Information Databases</a></dt><dt>Browsing, <a class="indexterm" href="s1-samba-network-browsing.html">Samba Network Browsing</a></dt><dt>configuration, <a class="indexterm" href="s1-samba-configuring.html">Configuring a Samba Server</a>, <a class="indexterm" href="s2-samba-configuring-cmdline.html">Command Line Configuration</a></dt><dd><dl><dt>default, <a class="indexterm" href="s1-samba-configuring.html">Co
nfiguring a Samba Server</a></dt></dl></dd><dt>CUPS Printing Support, <a class="indexterm" href="s1-samba-cups.html">Samba with CUPS Printing Support</a></dt><dd><dl><dt>CUPS smb.conf, <a class="indexterm" href="s1-samba-cups.html#s2-samba-cups-smb.conf">Simple smb.conf Settings</a></dt></dl></dd><dt>daemon, <a class="indexterm" href="s1-samba-daemons.html">Samba Daemons and Related Services</a></dt><dd><dl><dt>nmbd, <a class="indexterm" href="s1-samba-daemons.html#s2-samba-services">Samba Daemons</a></dt><dt>overview, <a class="indexterm" href="s1-samba-daemons.html#s2-samba-services">Samba Daemons</a></dt><dt>smbd, <a class="indexterm" href="s1-samba-daemons.html#s2-samba-services">Samba Daemons</a></dt><dt>winbindd, <a class="indexterm" href="s1-samba-daemons.html#s2-samba-services">Samba Daemons</a></dt></dl></dd><dt>encrypted passwords, <a class="indexterm" href="s2-samba-encrypted-passwords.html">Encrypted Passwords</a></dt><dt> findsmb , <a class="indexterm" href="s1-
samba-connect-share.html#s2-samba-connect-share-cmdline">Command Line</a></dt><dt>graphical configuration, <a class="indexterm" href="s1-samba-configuring.html#s2-samba-configuring-gui">Graphical Configuration</a></dt><dd><dl><dt>adding a share, <a class="indexterm" href="s1-samba-configuring.html#s3-samba-gui-add-share">Adding a Share</a></dt><dt>configuring server settings, <a class="indexterm" href="s1-samba-configuring.html#s3-samba-gui-server-settings">Configuring Server Settings</a></dt><dt>managing Samba users, <a class="indexterm" href="s1-samba-configuring.html#s3-samba-gui-users">Managing Samba Users</a></dt></dl></dd><dt>Introduction, <a class="indexterm" href="ch-Samba.html#samba-rgs-overview">Introduction to Samba</a></dt><dt>Network Browsing, <a class="indexterm" href="s1-samba-network-browsing.html">Samba Network Browsing</a></dt><dd><dl><dt>Domain Browsing, <a class="indexterm" href="s1-samba-network-browsing.html#s2-samba-domain-browsing">Domain Browsing</a>
</dt><dt>WINS, <a class="indexterm" href="s2-samba-wins.html">WINS (Windows Internetworking Name Server)</a></dt></dl></dd><dt>New Database Backends, <a class="indexterm" href="s1-samba-account-info-dbs.html">Samba Account Information Databases</a></dt><dt>Programs, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dd><dl><dt> findsmb , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> net , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> nmblookup , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> pdbedit , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> rpcclient , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbcacls , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbclient
, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbcontrol , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbpasswd , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbspool , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbstatus , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbtar , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> testparm , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> wbinfo , <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt></dl></dd><dt>Reference, <a class="indexterm" href="ch-Samba.html">Samba</a></dt><dt>Security Modes, <a class="indexterm" href="s1-samba-security-modes.html">Samba Security Modes
</a></dt><dd><dl><dt>Active Directory Security Mode, <a class="indexterm" href="s1-samba-security-modes.html#s2-samba-ads-security-mode">Active Directory Security Mode (User-Level Security)</a></dt><dt>Domain Security Mode, <a class="indexterm" href="s1-samba-security-modes.html#s2-samba-domain-security-mode">Domain Security Mode (User-Level Security)</a></dt><dt>Server Security Mode, <a class="indexterm" href="s1-samba-security-modes.html#s2-samba-server-security-mode">Server Security Mode (User-Level Security)</a></dt><dt>Share-Level Security, <a class="indexterm" href="s2-samba-share-level.html">Share-Level Security</a></dt><dt>User Level Security, <a class="indexterm" href="s1-samba-security-modes.html#s2-samba-user-level">User-Level Security</a></dt></dl></dd><dt>Server Types, <a class="indexterm" href="s1-samba-servers.html">Samba Server Types and the smb.conf File</a></dt><dt>server types</dt><dd><dl><dt>Domain Controller, <a class="indexterm" href="s2-samba-domain-co
ntroller.html">Domain Controller</a></dt><dt>Domain Member, <a class="indexterm" href="s2-samba-domain-member.html">Domain Member Server</a></dt><dt>Stand Alone, <a class="indexterm" href="s1-samba-servers.html#s2-samba-standalone">Stand-alone Server</a></dt></dl></dd><dt>service</dt><dd><dl><dt>conditional restarting, <a class="indexterm" href="s1-samba-startstop.html">Starting and Stopping Samba</a></dt><dt>reloading, <a class="indexterm" href="s1-samba-startstop.html">Starting and Stopping Samba</a></dt><dt>restarting, <a class="indexterm" href="s1-samba-startstop.html">Starting and Stopping Samba</a></dt><dt>starting, <a class="indexterm" href="s1-samba-startstop.html">Starting and Stopping Samba</a></dt><dt>stopping, <a class="indexterm" href="s1-samba-startstop.html">Starting and Stopping Samba</a></dt></dl></dd><dt>share</dt><dd><dl><dt>connecting to via the command line, <a class="indexterm" href="s1-samba-connect-share.html#s2-samba-connect-share-cmdline">Command Li
ne</a></dt><dt>connecting to with Nautilus, <a class="indexterm" href="s1-samba-connect-share.html">Connecting to a Samba Share</a></dt><dt>mounting, <a class="indexterm" href="s1-samba-mounting.html">Mounting the Share</a></dt></dl></dd><dt>smb.conf, <a class="indexterm" href="s1-samba-servers.html">Samba Server Types and the smb.conf File</a></dt><dd><dl><dt>Active Directory Member Server example, <a class="indexterm" href="s2-samba-domain-member.html#s3-samba-domain-member-ads">Active Directory Domain Member Server</a></dt><dt>Anonymous Print Server example, <a class="indexterm" href="s1-samba-servers.html#s3-samba-standalone-anonprint">Anonymous Print Server</a></dt><dt>Anonymous Read Only example, <a class="indexterm" href="s1-samba-servers.html#s3-samba-standalone-anonreadonly">Anonymous Read-Only</a></dt><dt>Anonymous Read/Write example, <a class="indexterm" href="s1-samba-servers.html#s3-samba-standalone-anonreadwrite">Anonymous Read/Write</a></dt><dt>NT4-style Domai
n Member example, <a class="indexterm" href="s2-samba-domain-member.html#s3-samba-domain-member-nt4">Windows NT4-based Domain Member Server</a></dt><dt>PDC using Active Directory, <a class="indexterm" href="s2-samba-domain-controller.html#samba-rgs-pdc-ads">Primary Domain Controller (PDC) with Active Directory</a></dt><dt>PDC using tdbsam , <a class="indexterm" href="s2-samba-domain-controller.html#s3-samba-pdc-tdbsam">Primary Domain Controller (PDC) using tdbsam </a></dt><dt>Secure File and Print Server example, <a class="indexterm" href="s1-samba-servers.html#s3-samba-standalone-readwriteall">Secure Read/Write File and Print Server</a></dt></dl></dd><dt> smbclient , <a class="indexterm" href="s1-samba-connect-share.html#s2-samba-connect-share-cmdline">Command Line</a></dt><dt>WINS, <a class="indexterm" href="s2-samba-wins.html">WINS (Windows Internetworking Name Server)</a></dt><dt>with Windows NT 4.0, 2000, ME, and XP, <a class="indexterm" href="s2-samba-encrypted-passwor
ds.html">Encrypted Passwords</a></dt></dl></dd><dt> scp (see OpenSSH)</dt><dt> ScriptAlias </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>SCSI module (see kernel module)</dt><dt>secure server</dt><dd><dl><dt>certificate</dt><dd><dl><dt>authorities, <a class="indexterm" href="s2-secureserver-certs.html">Types of Certificates</a></dt><dt>choosing a CA, <a class="indexterm" href="s2-secureserver-certs.html">Types of Certificates</a></dt><dt> moving it after an upgrade, <a class="indexterm" href="s1-secureserver-oldcert.html">Using Pre-Existing Keys and Certificates</a></dt><dt>pre-existing, <a class="indexterm" href="s1-secureserver-oldcert.html">Using Pre-Existing Keys and Certificates</a></dt><dt>test vs. signed vs. self-signed, <a class="indexterm" href="s2-secureserver-certs.html">Types of Certificates</a></dt></dl></dd><dt>explanation of security, <a class="
indexterm" href="s2-secureserver-overview-certs.html">An Overview of Certificates and Security</a></dt><dt>installing, <a class="indexterm" href="s1-httpd-secure-server.html">Apache HTTP Secure Server Configuration</a></dt><dt>key</dt><dd><dl><dt>generating, <a class="indexterm" href="s2-secureserver-generatingkey.html">Generating a Key</a></dt></dl></dd><dt>packages, <a class="indexterm" href="s1-httpd-secure-server.html#s2-secureserver-optionalpackages">An Overview of Security-Related Packages</a></dt><dt>providing a certificate for, <a class="indexterm" href="s2-secureserver-overview-certs.html">An Overview of Certificates and Security</a></dt><dt>security</dt><dd><dl><dt>explanation of, <a class="indexterm" href="s2-secureserver-overview-certs.html">An Overview of Certificates and Security</a></dt></dl></dd><dt>upgrading from, <a class="indexterm" href="s1-secureserver-oldcert.html">Using Pre-Existing Keys and Certificates</a></dt></dl></dd><dt>security</dt><dd><dl><dt>r
unning Apache without, <a class="indexterm" href="s1-apache-virtualhosts.html">Virtual Hosts</a></dt></dl></dd><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="s1-email-mta.html#s2-email-mta-sendmail">Sendmail</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-email-additional-resources.html">Additional Resources</a></dt><dt>aliases, <a class="indexterm" href="s1-email-mta.html#s3-email-sendmail-changes-masquerading">Masquerading</a></dt><dt>common configuration changes, <a class="indexterm" href="s1-email-mta.html#s3-email-mta-sendmail-changes">Common Sendmail Configuration Changes</a></dt><dt>default installation, <a class="indexterm" href="s1-email-mta.html#s3-email-mta-sendmail-default">The Default Sendmail I
nstallation</a></dt><dt>LDAP and, <a class="indexterm" href="s1-email-mta.html#s3-email-mta-sendmail-ldap">Using Sendmail with LDAP</a></dt><dt>limitations, <a class="indexterm" href="s1-email-mta.html#s3-email-mta-sendmail-purpose">Purpose and Limitations</a></dt><dt>masquerading, <a class="indexterm" href="s1-email-mta.html#s3-email-sendmail-changes-masquerading">Masquerading</a></dt><dt>purpose, <a class="indexterm" href="s1-email-mta.html#s3-email-mta-sendmail-purpose">Purpose and Limitations</a></dt><dt>spam, <a class="indexterm" href="s1-email-mta.html#s3-email-sendmail-stopping-spam">Stopping Spam</a></dt><dt>with UUCP, <a class="indexterm" href="s1-email-mta.html#s3-email-mta-sendmail-changes">Common Sendmail Configuration Changes</a></dt></dl></dd><dt>sendmail, <a class="indexterm" href="s1-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt><dt>server side includes, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configu
ration Tips</a></dt><dt> ServerAdmin </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ServerName </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ServerRoot </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ServerSignature </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> ServerTokens </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> service (see services configuration)</dt><dt>services configuration, <a class="i
ndexterm" 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> SetEnvIf </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s2-apache-sslcommands.html">Configuration Directives for SSL</a></dt></dl></dd><dt> sftp (see OpenSSH)</dt><dt>shadow passwords</dt><dd><dl><dt>overvie
w 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> slapadd command, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> slapcat command, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> slapd command, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> slapindex command, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> slappasswd command, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt>slave nameserver (see BIND)</dt><dt> slurpd comm
and, <a class="indexterm" href="s1-ldap-daemonsutils.html">OpenLDAP Daemons and Utilities</a></dt><dd><dl><dt>(see also LDAP)</dt></dl></dd><dt> smbcacls program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbclient , <a class="indexterm" href="s1-samba-connect-share.html#s2-samba-connect-share-cmdline">Command Line</a></dt><dt> smbclient program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbcontrol program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbpasswd program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbspool program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbstatus program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> smbtar program, <a class="indexterm" href="s1-samba-pr
ograms.html">Samba Distribution Programs</a></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="in
dexterm" 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>requiring 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 Versio
ns</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 configuration, <a class="indexterm" href="s2-apache-sslcommands.html">Configuration Directives for SSL</a></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_Configu
ration_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 LDAP 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> StartServers </dt><dd><dl><dt>Apache configura
tion directive, <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt></dl></dd><dt> startx , <a class="indexterm" href="s1-x-runlevels.html#s2-x-runlevels-3">Runlevel 3</a> (see X)</dt><dd><dl><dt>(see also X)</dt></dl></dd><dt> stunnel , <a class="indexterm" href="s1-email-mua.html#s3-email-security-servers">Securing Email Client Communications</a></dt><dt> SuexecUserGroup </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-mod-suexec">The suexec Module</a>, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><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-arpwatc
h"> /etc/sysconfig/arpwatch </a></dt><dt> /etc/sysconfig/authconfig , <a class="indexterm" href="ch-The_sysconfig_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/desktop , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-desktop"> /etc/sysconfig/desktop </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.ht
ml#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/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></dt><dt> /etc/sysconfig/ntpd , <a class="indexterm" href="ch-The_sysconfig_Dir
ectory.html#s2-sysconfig-ntpd"> /etc/sysconfig/ntpd </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/sendmail , <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-T
he_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> sysconfig/ directory</dt><dd><dl><dt> /etc/sysconfig/network-scripts/ directory, <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/ directory, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories 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 analysis</dt><dd><dl><dt>OProfile (see OProfile)</dt></dl></dd><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 Log 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> System Log Viewer - Filter </dt><dd><dl><dt>System Log Filter, <a class="indexterm" href="s1-logfiles-viewing.html">Viewing Log Files</a></dt></dl></dd><dt> System Log Viewer - View Menu </dt><dd><dl><dt>View Menu, <a class="indexterm" href="s1-logfiles-viewing.html">Viewing Log Files</a></dt></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.html"> /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-httpd (see HTTP Configuration Tool)</dt><dt> system-config-printer (see printer configuration)</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> testparm program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt> ThreadsPerChild </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s2-apache-mpm-containers.html">MPM Specific Server-Pool Directives</a></dt></dl></dd><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="indexterm" 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> Timeout </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>TLB cache (see hugepages)</dt><dt>tool</dt><dd><dl><dt> Authentication Configuration Tool , <a class="indexterm" href="ch-Authentication_Configuration.htm
l#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-processes">System Processes</a></dt><dt>troubleshooting</dt><dd><dl><dt>error log, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> twm , <a class="indexterm" href="s2-x-clients-winmanagers.html">Window Managers</a></dt><dd><dl><dt>(see also X)</dt></dl></dd><dt> TypesConfig </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd></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> UseCanonicalName </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> User </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>user configuration</dt><dd><dl><dt>adding users, <a class="indexterm" href="ers_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing full name, <a class="indexterm" href="ers_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing home directory, <a class="indexterm" href="ers_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing login shell,
<a class="indexterm" href="ers_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing password, <a class="indexterm" href="ers_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="ers_and_Groups.html#s1-users-configui">User and Group Configuration</a></dt><dt>modify groups for a user, <a class="indexterm" href="ers_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>modifying users, <a class="indexterm" href="ers_and_Groups.html#s2-redhat-config-users-user-new">Ad
ding 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="ers_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> UserDir </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>users (see user configuration)</dt><dd><dl><dt> /etc/passw
d , <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="ers_and_Groups.html">Users and Groups</a></dt><dt>personal HTML directories, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</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="ers_and_Groups.html">Users and Groups</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>VeriSign</dt><dd><dl><dt>using existing certificate, <a class="indexterm" href="s1-secureserver-oldcert.html">Using Pre-Existing Keys and Certificates</a></dt></dl></dd><dt>virtual file system (see proc file system)</dt><dt>virtual files (see proc file system)</dt><dt>virtual hosts</dt><dd><dl><dt>configuring, <a class="indexterm" href="s1-apache-virtualhosts.html">Virtual Hosts</a></dt><dt> Listen command, <a class="indexterm" href="s1-apache-virtualhosts.html#s2-apache-settingupvhosts">Setting Up Virtual Hosts</a></dt><dt>name-based, <a class="indexterm" href="s1-apache-virtualhosts.html">Virtual Hosts</a></dt><dt> Options , <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt><dt>server side includes, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a
></dt></dl></dd><dt> VirtualHost </dt><dd><dl><dt>Apache configuration directive, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt> vsftpd , <a class="indexterm" href="s1-ftp-servers.html">FTP Servers</a></dt><dd><dl><dt>(see also FTP)</dt><dt>additional resources, <a class="indexterm" href="s1-ftp-resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-ftp-resources.html#s2-ftp-installed-documentation">Installed Documentation</a></dt><dt>useful websites, <a class="indexterm" href="s2-ftp-useful-websites.html">Useful Websites</a></dt></dl></dd><dt>condrestart, <a class="indexterm" href="s1-ftp-vsftpd-start.html">Starting and Stopping vsftpd </a></dt><dt>configuration file</dt><dd><dl><dt> /etc/vsftpd/vsftpd.conf , <a class="indexterm" href="s1-ftp-vsftpd-conf.html"> vsftpd Configuration Options</a></dt><dt>access controls, <a class="indexterm" href="s2-ftp
-vsftpd-conf-opt-login.html">Log In Options and Access Controls</a></dt><dt>anonymous user options, <a class="indexterm" href="s2-ftp-vsftpd-conf-opt-anon.html">Anonymous User Options</a></dt><dt>daemon options, <a class="indexterm" href="s1-ftp-vsftpd-conf.html#s2-ftp-vsftpd-conf-opt-daemon">Daemon Options</a></dt><dt>directory options, <a class="indexterm" href="s2-ftp-vsftpd-conf-opt-dir.html">Directory Options</a></dt><dt>file transfer options, <a class="indexterm" href="s2-ftp-vsftpd-conf-opt-file.html">File Transfer Options</a></dt><dt>format of, <a class="indexterm" href="s1-ftp-vsftpd-conf.html"> vsftpd Configuration Options</a></dt><dt>local user options, <a class="indexterm" href="s2-ftp-vsftpd-conf-opt-usr.html">Local User Options</a></dt><dt>logging options, <a class="indexterm" href="s2-ftp-vsftpd-conf-opt-log.html">Logging Options</a></dt><dt>login options, <a class="indexterm" href="s2-ftp-vsftpd-conf-opt-login.html">Log In Options and Access Controls</a></dt>
<dt>network options, <a class="indexterm" href="s2-ftp-vsftpd-conf-opt-net.html">Network Options</a></dt></dl></dd><dt>multihome configuration, <a class="indexterm" href="s1-ftp-vsftpd-start.html#s2-ftp-vsftpd-start-multi">Starting Multiple Copies of vsftpd </a></dt><dt>restarting, <a class="indexterm" href="s1-ftp-vsftpd-start.html">Starting and Stopping vsftpd </a></dt><dt>RPM</dt><dd><dl><dt>files installed by, <a class="indexterm" href="s2-ftp-vsftpd-conf.html">Files Installed with vsftpd </a></dt></dl></dd><dt>security features, <a class="indexterm" href="s1-ftp-servers.html">FTP Servers</a></dt><dt>starting, <a class="indexterm" href="s1-ftp-vsftpd-start.html">Starting and Stopping vsftpd </a></dt><dt>starting multiple copies of, <a class="indexterm" href="s1-ftp-vsftpd-start.html#s2-ftp-vsftpd-start-multi">Starting Multiple Copies of vsftpd </a></dt><dt>status, <a class="indexterm" href="s1-ftp-vsftpd-start.html">Starting and Stopping vsftpd </a></dt><dt>stopping, <a
class="indexterm" href="s1-ftp-vsftpd-start.html">Starting and Stopping vsftpd </a></dt></dl></dd></dl></div><div class="indexdiv"><h3>W</h3><dl><dt> wbinfo program, <a class="indexterm" href="s1-samba-programs.html">Samba Distribution Programs</a></dt><dt>webmaster</dt><dd><dl><dt>email address for, <a class="indexterm" href="s1-apache-config.html#s2-apache-tips">General Configuration Tips</a></dt></dl></dd><dt>window managers (see X)</dt><dt>Windows 2000</dt><dd><dl><dt>connecting to shares using Samba, <a class="indexterm" href="s2-samba-encrypted-passwords.html">Encrypted Passwords</a></dt></dl></dd><dt>Windows 98</dt><dd><dl><dt>connecting to shares using Samba, <a class="indexterm" href="s2-samba-encrypted-passwords.html">Encrypted Passwords</a></dt></dl></dd><dt>Windows ME</dt><dd><dl><dt>connecting to shares using Samba, <a class="indexterm" href="s2-samba-encrypted-passwords.html">Encrypted Passwords</a></dt></dl></dd><dt>Windows NT 4.0</dt><dd><dl><dt>connecting to
shares using Samba, <a class="indexterm" href="s2-samba-encrypted-passwords.html">Encrypted Passwords</a></dt></dl></dd><dt>Windows XP</dt><dd><dl><dt>connecting to shares using Samba, <a class="indexterm" href="s2-samba-encrypted-passwords.html">Encrypted Passwords</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>X</h3><dl><dt>X</dt><dd><dl><dt> /etc/X11/xorg.conf </dt><dd><dl><dt>boolean values for, <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-struct">The Structure</a></dt><dt> Device , <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-device"> Device </a></dt><dt> DRI , <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-dri"> DRI </a></dt><dt> Files section, <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-files"> Files </a></dt><dt> InputDevice section, <a class="indexterm" href="s1-x-server-configuration.html#s3-
x-server-config-xorg.conf-inputd"> InputDevice </a></dt><dt>introducing, <a class="indexterm" href="s1-x-server-configuration.html#s2-x-server-config-xorg.conf"> xorg.conf </a></dt><dt> Module section, <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-modules"> Module </a></dt><dt> Monitor , <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-monitor"> Monitor </a></dt><dt> Screen , <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-screen"> Screen </a></dt><dt> Section tag, <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-struct">The Structure</a></dt><dt> ServerFlags section, <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-serverf"> ServerFlags </a></dt><dt> ServerLayout section, <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-serverl"> ServerLayout </a
></dt><dt>structure of, <a class="indexterm" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-struct">The Structure</a></dt></dl></dd><dt>additional resources, <a class="indexterm" href="s1-x-additional-resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-x-additional-resources.html#s2-x-installed-documentation">Installed Documentation</a></dt><dt>useful websites, <a class="indexterm" href="s2-x-useful-websites.html">Useful Websites</a></dt></dl></dd><dt>configuration files</dt><dd><dl><dt> /etc/X11/ directory, <a class="indexterm" href="s1-x-server-configuration.html">X Server Configuration Files</a></dt><dt> /etc/X11/xorg.conf , <a class="indexterm" href="s1-x-server-configuration.html#s2-x-server-config-xorg.conf"> xorg.conf </a></dt><dt>options within, <a class="indexterm" href="s1-x-server-configuration.html">X Server Configuration Files</a></dt><dt>server options, <a class="indexterm" href="s1-
x-server-configuration.html#s2-x-server-config-xorg.conf"> xorg.conf </a></dt></dl></dd><dt>desktop environments</dt><dd><dl><dt>GNOME, <a class="indexterm" href="s1-x-clients.html#s2-x-clients-desktop">Desktop Environments</a></dt><dt>KDE, <a class="indexterm" href="s1-x-clients.html#s2-x-clients-desktop">Desktop Environments</a></dt></dl></dd><dt>display managers</dt><dd><dl><dt>configuration of preferred, <a class="indexterm" href="s2-x-runlevels-5.html">Runlevel 5</a></dt><dt>definition of, <a class="indexterm" href="s2-x-runlevels-5.html">Runlevel 5</a></dt><dt> GNOME , <a class="indexterm" href="s2-x-runlevels-5.html">Runlevel 5</a></dt><dt> KDE , <a class="indexterm" href="s2-x-runlevels-5.html">Runlevel 5</a></dt><dt> prefdm script, <a class="indexterm" href="s2-x-runlevels-5.html">Runlevel 5</a></dt><dt> xdm , <a class="indexterm" href="s2-x-runlevels-5.html">Runlevel 5</a></dt></dl></dd><dt>fonts</dt><dd><dl><dt>core X font subsystem, <a class="indexterm" href="s2-
x-fonts-core.html">Core X Font System</a></dt><dt>Fontconfig, <a class="indexterm" href="s1-x-fonts.html#s2-x-fonts-fontconfig">Fontconfig</a></dt><dt>Fontconfig, adding fonts to, <a class="indexterm" href="s1-x-fonts.html#s3-x-fonts-fontconfig-add">Adding Fonts to Fontconfig</a></dt><dt>FreeType, <a class="indexterm" href="s1-x-fonts.html#s2-x-fonts-fontconfig">Fontconfig</a></dt><dt>introducing, <a class="indexterm" href="s1-x-fonts.html">Fonts</a></dt><dt>X Font Server, <a class="indexterm" href="s2-x-fonts-core.html">Core X Font System</a></dt><dt>X Render Extension, <a class="indexterm" href="s1-x-fonts.html#s2-x-fonts-fontconfig">Fontconfig</a></dt><dt> xfs , <a class="indexterm" href="s2-x-fonts-core.html">Core X Font System</a></dt><dt> xfs configuration, <a class="indexterm" href="s2-x-fonts-core.html#s3-x-fonts-xfs-config"> xfs Configuration</a></dt><dt> xfs, adding fonts to, <a class="indexterm" href="s2-x-fonts-core.html#s2-x-fonts-xfs-add">Adding Fonts to xfs </
a></dt><dt>Xft, <a class="indexterm" href="s1-x-fonts.html#s2-x-fonts-fontconfig">Fontconfig</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="ch-The_X_Window_System.html">The X Window System</a></dt><dt>runlevels</dt><dd><dl><dt>3, <a class="indexterm" href="s1-x-runlevels.html#s2-x-runlevels-3">Runlevel 3</a></dt><dt>5, <a class="indexterm" href="s2-x-runlevels-5.html">Runlevel 5</a></dt></dl></dd><dt>runlevels and, <a class="indexterm" href="s1-x-runlevels.html">Runlevels and X</a></dt><dt>window managers</dt><dd><dl><dt> kwin , <a class="indexterm" href="s2-x-clients-winmanagers.html">Window Managers</a></dt><dt> metacity , <a class="indexterm" href="s2-x-clients-winmanagers.html">Window Managers</a></dt><dt> mwm , <a class="indexterm" href="s2-x-clients-winmanagers.html">Window Managers</a></dt><dt> twm , <a class="indexterm" href="s2-x-clients-winmanagers.html">Window Managers</a></dt></dl></dd><dt>X clients, <a class="indexterm" href="ch-The_X_Window_Syste
m.html">The X Window System</a>, <a class="indexterm" href="s1-x-clients.html">Desktop Environments and Window Managers</a></dt><dd><dl><dt>desktop environments, <a class="indexterm" href="s1-x-clients.html#s2-x-clients-desktop">Desktop Environments</a></dt><dt> startx command, <a class="indexterm" href="s1-x-runlevels.html#s2-x-runlevels-3">Runlevel 3</a></dt><dt>window managers, <a class="indexterm" href="s2-x-clients-winmanagers.html">Window Managers</a></dt><dt> xinit command, <a class="indexterm" href="s1-x-runlevels.html#s2-x-runlevels-3">Runlevel 3</a></dt></dl></dd><dt>X server, <a class="indexterm" href="ch-The_X_Window_System.html">The X Window System</a></dt><dd><dl><dt>features of, <a class="indexterm" href="ch-The_X_Window_System.html#s1-x-server">The X11R7.1 Release</a></dt></dl></dd></dl></dd><dt>X Window System (see X)</dt><dt>X.500 (see LDAP)</dt><dt>X.500 Lite (see LDAP)</dt><dt> xinit (see X)</dt><dt>Xorg (see Xorg)</dt></dl></div><div class="indexdiv"><h
3>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></dt></dl></dd><dt>displaying packages with Yum, <a class="indexterm" href="sec-Packages_and_P
ackage_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, Listing and Displaying Package Information</a></dt><dd><dl><dt>Glob expressions, <a class="i
ndexterm" 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_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>y
um 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>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">Plu
gin 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 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></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_History.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_Draft_Documentation/0.1/html/Deployment_Guide/lease-database.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/lease-database.html
new file mode 100644
index 0000000..30c9687
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/lease-database.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-dhcp-configuring-server.html" title="10.2. Configuring a DHCP Server" /><link rel="prev" href="s1-dhcp-configuring-server.html" title="10.2. Configuring a DHCP Server" /><link rel="next" href="ch10s02s03.html" title="10.2.3. Starting and Stopping the Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade y
our browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="ch10s02s03.html"><strong>Next</strong></a></li></ul><div class="section" title="10.2.2. Lease Database" id="lease-database"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="lease-database">10.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>10.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="ch10s02s03.html"><strong>Next</strong>10.2.3. Starting and Stopping the Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pr01.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pr01.html
new file mode 100644
index 0000000..2b17af5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pr01.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http
://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id877691" lang="en-US"><div class="titlepage"><div><div><h1 id="id877691" 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="id953328">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="id953305">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>F1</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>F7</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="id664376">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="id645978">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"><h2>Note</h2><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 class="important"><h2>Important</h2><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' won't cause data loss but may cause irritation and frustration.
+ </div></div><div class="warning"><h2>Warning</h2><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </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_Draft_Documentation/0.1/html/Deployment_Guide/pt-kernel-configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-kernel-configuration.html
new file mode 100644
index 0000000..9f2d760
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-kernel-configuration.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="ch28s05s03.html" title="28.5.3. Deleting Crashes" /><link rel="next" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 29. Manually Upgrading the Kernel" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or ena
ble iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch28s05s03.html"><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 xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES" class="part" title="Part V. Kernel and Driver Configuration" id="pt-kernel-configuration" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part V. Kernel and Driver Configuration</h1></div></div></div><div class="partintro" t
itle="Kernel and Driver Configuration" id="id616161"><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-Manually_Upgrading_the_Kernel.html">29. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">29.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">29.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">29.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">29.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">29.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">29.6. Verifying the Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="s1-kernel-boot-loader.html#s3-kerne
l-boot-loader-grub">29.6.1. Configuring the GRUB Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-iseries.html">29.6.2. Configuring the <span class="trademark">OS/400</span>® Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-pseries.html">29.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-General_Parameters_and_Modules.html">30. General Parameters and Modules</a></span></dt><dd><dl><dt><span class="section"><a href="ch-General_Parameters_and_Modules.html#s1-kernel-module-utils">30.1. Kernel Module Utilities</a></span></dt><dt><span class="section"><a href="s1-kernel-modules-persistant.html">30.2. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="s1-modules-parameters-specifying.html">30.3. Specifying Module Parameters</a></span></dt><dt><span class="section"><a href="s1-modules-scsi.html">30.4. Storage parameters</a>
</span></dt><dt><span class="section"><a href="s1-modules-ethernet.html">30.5. Ethernet Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="s1-modules-ethernet.html#s2-modules-multiple-eth">30.5.1. Using Multiple Ethernet Cards</a></span></dt><dt><span class="section"><a href="s2-modules-bonding.html">30.5.2. The Channel Bonding Module</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">30.6. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch28s05s03.html"><strong>Prev</strong>28.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="ch-Manually_Upgrading_the_Kernel.html"><strong>Next</strong>Chapter 29. Manually Upgrading the Kernel</a></li></ul></body></ht
ml>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-network-related-config.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-network-related-config.html
new file mode 100644
index 0000000..5fb7ffa
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-network-related-config.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display
.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_Interfaces.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,de-DE,ru-RU,fr-FR,zh-CN,it-IT,es-ES,ja-JP" class="part" title="Part II. Network-Related Configuration" id="pt-network-related-config" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,de-DE,ru-RU,fr-FR,zh-CN,it-IT,es-ES,ja-JP"><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="id908183"><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><dd><dl><dt><span class="section"><a href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">4.2.1. Ethernet Interfaces</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-chan.html">4.2.2. Channel Bonding Interfaces</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-alias.html">4.2.3. Alias and Clone Files</a></span></dt><dt><span class="section"><a href="s2-networkscripts-interfaces-ppp0.html">4.2.4. Dialup Interfaces</a></span></dt><dt><span class="section"><a href="s2-networkscripts
-interfaces-other.html">4.2.5. Other Interfaces</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="s1-networkscripts-resources.html#s2-networkscripts-docs-inst">4.6.1. Installed Documentation</a></span></dt></dl></dd></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><dd><dl><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network">5.2.1. Connecting to a Network</a></span></dt><dt><span class="section"><a href="sec-Configuring_New_and_Editing_Existing_Connections.html">5.2.2. Configuring New and Editing Existing Connections</a></span></dt><dt><span class="section"><a href="sec-Connecting_to_a_Network_Automatically.html">5.2.3. Connecting to a Network Automatically</a></span></dt><dt><span class="section"><a href="sec-User_and_System_Connections.html">5.2.4. User and System Connections</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Establishing_Connections.html">5.3. Establishing Connections</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Establishing_Connections.html#sec-Establishing_a_Wired_Ethernet_Connection">5.3.1. Establishing a Wired (Ethernet) Connection</a></sp
an></dt><dt><span class="section"><a href="sec-Establishing_a_Wireless_Connection.html">5.3.2. Establishing a Wireless Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_Mobile_Broadband_Connection.html">5.3.3. Establishing a Mobile Broadband Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_VPN_Connection.html">5.3.4. Establishing a VPN Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_a_DSL_Connection.html">5.3.5. Establishing a DSL Connection</a></span></dt><dt><span class="section"><a href="sec-Establishing_Routes.html">5.3.6. Establishing Routes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html">5.4. Configuring Connection Settings</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html#sec-Configuring_802.1x_Security">5.4.1. Configuring 802.1x Security</a></span></dt><dt><span class="section
"><a href="sec-Configuring_Wireless_Security.html">5.4.2. Configuring Wireless Security</a></span></dt><dt><span class="section"><a href="sec-Configuring_PPP_Point-to-Point_Settings.html">5.4.3. Configuring PPP (Point-to-Point) Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv4_Settings.html">5.4.4. Configuring IPv4 Settings</a></span></dt><dt><span class="section"><a href="sec-Configuring_IPv6_Settings.html">5.4.5. Configuring IPv6 Settings</a></span></dt></dl></dd><dt><span class="section"><a href="sec-NetworkManager_Architecture.html">5.5. NetworkManager Architecture</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Controlling_Access_to_Services.html">6. Controlling Access to Services</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Controlling_Access_to_Services.html#s1-services-runlevels">6.1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="s1-services-configuring.html">6.2. Config
uring the Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-configuring.html#s2-services-serviceconf">6.2.1. Using the <span class="application"><strong>Service Configuration</strong></span> Utility</a></span></dt><dt><span class="section"><a href="s2-services-ntsysv.html">6.2.2. Using the <span class="application"><strong>ntsysv</strong></span> Utility</a></span></dt><dt><span class="section"><a href="s2-services-chkconfig.html">6.2.3. Using the <code class="command">chkconfig</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">6.3. Running the Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-running.html#s2-services-service">6.3.1. Using the <span class="application"><strong>service</strong></span> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-additional-resources.html">6.4. Additional Resources</a></span></dt><dd><dl><dt><span class
="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">6.4.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">6.4.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-The_BIND_DNS_Server.html">7. The BIND DNS Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s1-bind-introduction">7.1. Introduction to DNS</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-zones">7.1.1. Nameserver Zones</a></span></dt><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">7.1.2. Nameserver Types</a></span></dt><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-bind">7.1.3. BIND as a Nameserver</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-namedconf.
html">7.2. <code class="filename">/etc/named.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-namedconf.html#s2-bind-namedconf-state">7.2.1. Common Statement Types</a></span></dt><dt><span class="section"><a href="s2-bind-namedconf-state-other.html">7.2.2. Other Statement Types</a></span></dt><dt><span class="section"><a href="s2-bind-namedconf-comm.html">7.2.3. Comment Tags</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-zone.html">7.3. Zone Files</a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-zone.html#s2-bind-zone-directives">7.3.1. Zone File Directives</a></span></dt><dt><span class="section"><a href="s3-bind-zone-rr.html">7.3.2. Zone File Resource Records</a></span></dt><dt><span class="section"><a href="s2-bind-zone-examples.html">7.3.3. Example Zone File</a></span></dt><dt><span class="section"><a href="s2-bind-configuration-zone-reverse.html">7.3.4. Reverse Name Resolution Zone Files</a></span></dt
></dl></dd><dt><span class="section"><a href="s1-bind-rndc.html">7.4. Using <code class="command">rndc</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-rndc.html#s2-bind-rndc-configuration-namedconf">7.4.1. Configuring <code class="filename">/etc/named.conf</code> </a></span></dt><dt><span class="section"><a href="s2-bind-rndc-configuration-rndcconf.html">7.4.2. Configuring <code class="filename">/etc/rndc.conf</code> </a></span></dt><dt><span class="section"><a href="s2-bind-rndc-options.html">7.4.3. Command Line Options</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-features.html">7.5. Advanced Features of BIND</a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-features.html#s2-bind-features-protocol">7.5.1. DNS Protocol Enhancements</a></span></dt><dt><span class="section"><a href="s2-bind-features-views.html">7.5.2. Multiple Views</a></span></dt><dt><span class="section"><a href="s2-bind-features-security.html"
>7.5.3. Security</a></span></dt><dt><span class="section"><a href="s2-bind-features-ipv6.html">7.5.4. IP version 6</a></span></dt></dl></dd><dt><span class="section"><a href="s1-bind-mistakes.html">7.6. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="s1-bind-additional-resources.html">7.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-bind-additional-resources.html#s2-bind-installed-docs">7.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-bind-useful-websites.html">7.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-bind-related-books.html">7.7.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-OpenSSH.html">8. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">8.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">8.1.
1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-features">8.1.2. Main Features</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">8.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">8.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">8.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">8.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">8.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">8.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">8.2.4. Using a Key-Based Authentication</a></spa
n></dt></dl></dd><dt><span class="section"><a href="s1-ssh-clients.html">8.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">8.3.1. Using the <code class="command">ssh</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">8.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">8.3.3. Using the <code class="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-beyondshell.html">8.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">8.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">8.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">8.5. Additional Resources<
/a></span></dt><dd><dl><dt><span class="section"><a href="s1-openssh-additional-resources.html#s2-openssh-installed-docs">8.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-openssh-useful-websites.html">8.5.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Samba.html">9. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Samba.html#samba-rgs-overview">9.1. Introduction to Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Samba.html#s2-samba-abilities">9.1.1. Samba Features</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-daemons.html">9.2. Samba Daemons and Related Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-daemons.html#s2-samba-services">9.2.1. Samba Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-connect-share.html">9.3. Connecting to a Samba Share</a></span></dt><dd><dl><dt><span class
="section"><a href="s1-samba-connect-share.html#s2-samba-connect-share-cmdline">9.3.1. Command Line</a></span></dt><dt><span class="section"><a href="s1-samba-mounting.html">9.3.2. Mounting the Share</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-configuring.html">9.4. Configuring a Samba Server</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-configuring.html#s2-samba-configuring-gui">9.4.1. Graphical Configuration</a></span></dt><dt><span class="section"><a href="s2-samba-configuring-cmdline.html">9.4.2. Command Line Configuration</a></span></dt><dt><span class="section"><a href="s2-samba-encrypted-passwords.html">9.4.3. Encrypted Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-startstop.html">9.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="s1-samba-servers.html">9.6. Samba Server Types and the <code class="command">smb.conf</code> File</a></span></dt><dd><dl><dt><span
class="section"><a href="s1-samba-servers.html#s2-samba-standalone">9.6.1. Stand-alone Server</a></span></dt><dt><span class="section"><a href="s2-samba-domain-member.html">9.6.2. Domain Member Server</a></span></dt><dt><span class="section"><a href="s2-samba-domain-controller.html">9.6.3. Domain Controller</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-security-modes.html">9.7. Samba Security Modes</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-security-modes.html#s2-samba-user-level">9.7.1. User-Level Security</a></span></dt><dt><span class="section"><a href="s2-samba-share-level.html">9.7.2. Share-Level Security</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-account-info-dbs.html">9.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="s1-samba-network-browsing.html">9.9. Samba Network Browsing</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-network-brows
ing.html#s2-samba-domain-browsing">9.9.1. Domain Browsing</a></span></dt><dt><span class="section"><a href="s2-samba-wins.html">9.9.2. WINS (Windows Internetworking Name Server)</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-cups.html">9.10. Samba with CUPS Printing Support</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-cups.html#s2-samba-cups-smb.conf">9.10.1. Simple <code class="filename">smb.conf</code> Settings</a></span></dt></dl></dd><dt><span class="section"><a href="s1-samba-programs.html">9.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="s1-samba-resources.html">9.12. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-samba-resources.html#s2-samba-resources-installed">9.12.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-samba-resources-published.html">9.12.2. Related Books</a></span></dt><dt><span class="section"><a href="s2-samb
a-resources-community.html">9.12.3. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html">10. 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">10.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-server.html">10.2. Configuring a DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-configuring-server.html#config-file">10.2.1. Configuration File</a></span></dt><dt><span class="section"><a href="lease-database.html">10.2.2. Lease Database</a></span></dt><dt><span class="section"><a href="ch10s02s03.html">10.2.3. Starting and Stopping the Server</a></span></dt><dt><span class="section"><a href="dhcp-relay-agent.html">10.2.4. DHCP Relay Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp-configuring-clien
t.html">10.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html">10.4. Configuring a Multihomed DHCP Server</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html#sect-dns_Host_Configuration">10.4.1. Host Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">10.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="s1-dhcp-additional-resources.html">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-dhcp-additional-resources.html#s2-dhcp-installed-docs">10.6.1. Installed Documentation</a></span></dt></dl></dd></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-httpd-v2">11.1. Apache HTTP Server 2.2</a></spa
n></dt><dd><dl><dt><span class="section"><a href="ch-The_Apache_HTTP_Server.html#s2-httpd-v2-features">11.1.1. Features of Apache HTTP Server 2.2</a></span></dt></dl></dd><dt><span class="section"><a href="s1-httpd-mig.html">11.2. Migrating Apache HTTP Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="s1-httpd-mig.html#s1-httpd-v22-mig">11.2.1. Migrating Apache HTTP Server 2.0 Configuration Files</a></span></dt><dt><span class="section"><a href="s3-httpd-v2-mig.html">11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-startstop.html">11.3. Starting and Stopping <code class="command">httpd</code> </a></span></dt><dt><span class="section"><a href="s1-apache-config-ui.html">11.4. Apache HTTP Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-apache-config-ui.html#s2-httpd-basic-settings">11.4.1. Basic Settings</a></span></dt><dt
><span class="section"><a href="s2-httpd-default-settings.html">11.4.2. Default Settings</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-config.html">11.5. Configuration Directives in <code class="filename">httpd.conf</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-apache-config.html#s2-apache-tips">11.5.1. General Configuration Tips</a></span></dt><dt><span class="section"><a href="s2-apache-sslcommands.html">11.5.2. Configuration Directives for SSL</a></span></dt><dt><span class="section"><a href="s2-apache-mpm-containers.html">11.5.3. MPM Specific Server-Pool Directives</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-addmods.html">11.6. Adding Modules</a></span></dt><dt><span class="section"><a href="s1-apache-virtualhosts.html">11.7. Virtual Hosts</a></span></dt><dd><dl><dt><span class="section"><a href="s1-apache-virtualhosts.html#s2-apache-settingupvhosts">11.7.1. Setting Up Virtual Hosts</a></span></dt><
/dl></dd><dt><span class="section"><a href="s1-httpd-secure-server.html">11.8. Apache HTTP Secure Server Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-httpd-secure-server.html#s2-secureserver-optionalpackages">11.8.1. An Overview of Security-Related Packages</a></span></dt><dt><span class="section"><a href="s2-secureserver-overview-certs.html">11.8.2. An Overview of Certificates and Security</a></span></dt><dt><span class="section"><a href="s1-secureserver-oldcert.html">11.8.3. Using Pre-Existing Keys and Certificates</a></span></dt><dt><span class="section"><a href="s2-secureserver-certs.html">11.8.4. Types of Certificates</a></span></dt><dt><span class="section"><a href="s2-secureserver-generatingkey.html">11.8.5. Generating a Key</a></span></dt><dt><span class="section"><a href="s1-use-new-key.html">11.8.6. How to configure the server to use the new key</a></span></dt></dl></dd><dt><span class="section"><a href="s1-apache-additional-resources.
html">11.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-apache-additional-resources.html#s2-apache-additional-resources-web">11.9.1. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-FTP.html">12. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-FTP.html#s1-ftp-protocol">12.1. The File Transfer Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-FTP.html#s2-ftp-protocol-multiport">12.1.1. Multiple Ports, Multiple Modes</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ftp-servers.html">12.2. FTP Servers</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-servers.html#s2-ftp-servers-vsftpd">12.2.1. <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s2-ftp-vsftpd-conf.html">12.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s1-ftp-vsf
tpd-start.html">12.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-vsftpd-start.html#s2-ftp-vsftpd-start-multi">12.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-ftp-vsftpd-conf.html">12.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-vsftpd-conf.html#s2-ftp-vsftpd-conf-opt-daemon">12.5.1. Daemon Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-login.html">12.5.2. Log In Options and Access Controls</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-anon.html">12.5.3. Anonymous User Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-usr.html">12.5.4. Local User Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-dir.html">12.
5.5. Directory Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-file.html">12.5.6. File Transfer Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-log.html">12.5.7. Logging Options</a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf-opt-net.html">12.5.8. Network Options</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ftp-resources.html">12.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ftp-resources.html#s2-ftp-installed-documentation">12.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-ftp-useful-websites.html">12.6.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-email.html">13. Email</a></span></dt><dd><dl><dt><span class="section"><a href="ch-email.html#s1-email-protocols">13.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="ch-email.html#
s2-email-protocols-send">13.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="ch-email.html#s2-email-protocols-client">13.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">13.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta">13.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mda.html">13.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mua.html">13.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">13.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mta.html#s2-email-mta-sendmail">13.3.1. Sendmail</a></span></dt><dt><span class="section"><a href="s2-email-mta-postfix.html">13.3.2. Postfix</a></span></dt><dt><span class="section"><a href
="s2-email-mta-fetchmail.html">13.3.3. Fetchmail</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-switchmail.html">13.4. Mail Transport Agent (MTA) Configuration</a></span></dt><dt><span class="section"><a href="s1-email-mda.html">13.5. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-email-procmail-configuration">13.5.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">13.5.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mua.html">13.6. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">13.6.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">13.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-d
ocs">13.7.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-email-useful-websites.html">13.7.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-email-related-books.html">13.7.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Lightweight_Directory_Access_Protocol_LDAP.html">14. Lightweight Directory Access Protocol (LDAP)</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Lightweight_Directory_Access_Protocol_LDAP.html#s1-ldap-adv">14.1. Why Use LDAP?</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Lightweight_Directory_Access_Protocol_LDAP.html#s1-ldap-v3">14.1.1. OpenLDAP Features</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-terminology.html">14.2. LDAP Terminology</a></span></dt><dt><span class="section"><a href="s1-ldap-daemonsutils.html">14.3. OpenLDAP Daemons and Utilities</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ld
ap-daemonsutils.html#s2-ldap-pam-nss">14.3.1. NSS, PAM, and LDAP</a></span></dt><dt><span class="section"><a href="s2-ldap-other-apps.html">14.3.2. PHP4, LDAP, and the Apache HTTP Server</a></span></dt><dt><span class="section"><a href="s2-ldap-applications.html">14.3.3. LDAP Client Applications</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-files.html">14.4. OpenLDAP Configuration Files</a></span></dt><dt><span class="section"><a href="s1-ldap-files-schemas.html">14.5. The <code class="filename">/etc/openldap/schema/</code> Directory</a></span></dt><dt><span class="section"><a href="s1-ldap-quickstart.html">14.6. OpenLDAP Setup Overview</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ldap-quickstart.html#s2-ldap-files-slapd-conf">14.6.1. Editing <code class="filename">/etc/openldap/slapd.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-pam.html">14.7. Configuring a System to Authenticate Using OpenLDAP</a></s
pan></dt><dd><dl><dt><span class="section"><a href="s1-ldap-pam.html#s2-ldap-pamd">14.7.1. PAM and LDAP</a></span></dt><dt><span class="section"><a href="s2-ldap-migrate.html">14.7.2. Migrating Old Authentication Information to LDAP Format</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ldap-migrate.html">14.8. Migrating Directories from Earlier Releases</a></span></dt><dt><span class="section"><a href="s1-ldap-additional-resources.html">14.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ldap-additional-resources.html#s2-ldap-installed-docs">14.9.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-ldap-additional-resources-web.html">14.9.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-ldap-related-books.html">14.9.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Authentication_Configuration.html">15. Authentication Configuration</a>
</span></dt><dd><dl><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool">15.1. The Authentication Configuration Tool</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">15.1.1. Identity & Authentication</a></span></dt><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">15.1.2. Advanced Options</a></span></dt><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">15.1.3. Command Line Version</a></span></dt></dl></dd><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html">15.2. The System Security Services Daemon (SSSD)</a></span></dt><dd><dl><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html#sect
-SSSD_User_Guide-Introduction-What_is_SSSD">15.2.1. What is SSSD?</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html">15.2.2. SSSD Features</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Setting_Up_SSSD.html">15.2.3. Setting Up SSSD</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Services.html">15.2.4. Configuring Services</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Configuring_Domains.html">15.2.5. Configuring Domains</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">15.2.6. Setting up Kerberos Authentication</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Troubleshooting.html">15.2.7. Troubleshooting</a></span></dt><dt><span class="section"><a href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.h
tml">15.2.8. SSSD Configuration File Format</a></span></dt></dl></dd></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 accesskey="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_Draft_Documentation/0.1/html/Deployment_Guide/pt-pkg-management.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-pkg-management.html
new file mode 100644
index 0000000..f82166c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-pkg-management.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.
fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES" class="part" title="Part I. Package Management" id="pt-pkg-management" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES"><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="id575550"><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><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">1.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">1.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Security-Related_Packages">1.1.3. Updating Security-Related Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">1.1.4. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">1.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Pa
ckages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">1.2.1. Searching, Listing and Displaying Package Information</a></span></dt><dt><span class="section"><a href="sec-Installing.html">1.2.2. Installing</a></span></dt><dt><span class="section"><a href="sec-Removing.html">1.2.3. Removing</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">1.3. Configuring Yum and Yum Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">1.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="sec-Setting_repository_Options.html">1.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="sec-Using_Yum_Variables.html">1.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">1.3.4. Creating a Yum Repository</a></sp
an></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">1.4. Yum Plugins</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">1.4.1. Enabling, Configuring and Disabling Yum Plugins</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">1.4.2. Installing More Yum Plugins</a></span></dt><dt><span class="section"><a href="sec-Plugin_Descriptions.html">1.4.3. Plugin Descriptions</a></span></dt></dl></dd><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/Remo
ve Software</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html#sec-Refreshing_Software_Sources_Yum_Repositories">2.2.1. Refreshing Software Sources (Yum Repositories)</a></span></dt><dt><span class="section"><a href="sec-Finding_Packages_with_Filters.html">2.2.2. Finding Packages with Filters</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Packages_and_Dependencies.html">2.2.3. Installing and Removing Packages (and Dependencies)</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Removing_Package_Groups.html">2.2.4. Installing and Removing Package Groups</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Transaction_Log.html">2.2.5. Viewing the Transaction Log</a></span></dt></dl></dd><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-Additio
nal_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><dd><dl><dt><span class="section"><a href="s1-rpm-using.html#s2-rpm-finding">3.2.1. Finding RPM Packages</a></span></dt><dt><span class="section"><a href="sec-Installing_and_Upgrading.html">3.2.2. Installing and Upgrading</a></span></dt><dt><span class="section"><a href="sec-Configuration_File_Changes.html">3.2.3. Configuration File Changes</a></span></dt><dt><span class="section"><a href="s2-rpm-uninstalling.html">3.2.4. Uninstalling</a></span></dt><dt><span class="section"><a href="s2-rpm-freshening.html">3.2.5. Freshening</a></span></dt><dt><span class="section"><a href="s2-rpm-querying.html">3.2.6. Querying</a></span></dt><dt><span class="sectio
n"><a href="s2-rpm-verifying.html">3.2.7. Verifying</a></span></dt></dl></dd><dt><span class="section"><a href="s1-check-rpm-sig.html">3.3. Checking a Package's Signature</a></span></dt><dd><dl><dt><span class="section"><a href="s1-check-rpm-sig.html#s2-keys-importing">3.3.1. Importing Keys</a></span></dt><dt><span class="section"><a href="s2-keys-checking.html">3.3.2. Verifying Signature of Packages</a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="s1-rpm-additional-resources.html#s2-rpm-installed-docs">3.5.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-rpm-useful-websites.html">3.5.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-rpm-related-books.html">3.5.3. Related Book
s</a></span></dt></dl></dd></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_Draft_Documentation/0.1/html/Deployment_Guide/pt-sysconfig.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-sysconfig.html
new file mode 100644
index 0000000..8479fb3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-sysconfig.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html" title="15.2.8. SSSD Configuration File Format" /><link rel="next" href="ch-Console_Access.html" title="Chapter 16. Console Access" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="ch-Console_Access.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,de-DE,es-ES,fr-FR,it-IT,ja-JP" class="part" title="Part III. System Configuration" id="pt-sysconfig" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,de-DE,es-ES,fr-FR,it-IT,ja-JP"><div class="titlepage"><div><div te
xt-align="center"><h1 class="title">Part III. System Configuration</h1></div></div></div><div class="partintro" title="System Configuration" id="id1006022"><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="ch-Console_Access.html">16. Console Access</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Console_Access.html#s1-access-console-ctrlaltdel">16.1. Disabling Shutdown Via <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Del</strong></span></a></span></dt><dt><span class="section"><a href="s1-access-console-program.html">16.2. Disabling Console Program Access</a></span></dt><dt><span class="section"><a href="s1-access-console-define.html">16.3. Defining the Console</a></span></dt><dt><span class="section"><a href="s1-access-console-files.html">16.4. Making Files Accessible From the Console</a></span></dt><dt><span class="section"><a href="s1-access-console-enable.html">16.5. Enabling Console Access for Other Applications</a></span></dt><dt><span class="section"><a href="s1-access-floppy.html"
>16.6. The <code class="filename">floppy</code> Group</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-proc.html">17. 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">17.1. A Virtual File System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-proc.html#s2-proc-viewing">17.1.1. Viewing Virtual Files</a></span></dt><dt><span class="section"><a href="ch-proc.html#s2-proc-change">17.1.2. Changing Virtual Files</a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-topfiles.html">17.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="s1-proc-topfiles.html#s2-proc-buddyinfo">17.2.1. <code class="filename">/proc/buddyinfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-cmdline.html">17.2.2. <code class="filename">/proc/cmdline</code> </a></span></dt><dt
><span class="section"><a href="s2-proc-cpuinfo.html">17.2.3. <code class="filename">/proc/cpuinfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-crypto.html">17.2.4. <code class="filename">/proc/crypto</code> </a></span></dt><dt><span class="section"><a href="s2-proc-devices.html">17.2.5. <code class="filename">/proc/devices</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dma.html">17.2.6. <code class="filename">/proc/dma</code> </a></span></dt><dt><span class="section"><a href="s2-proc-execdomains.html">17.2.7. <code class="filename">/proc/execdomains</code> </a></span></dt><dt><span class="section"><a href="s2-proc-fb.html">17.2.8. <code class="filename">/proc/fb</code> </a></span></dt><dt><span class="section"><a href="s2-proc-filesystems.html">17.2.9. <code class="filename">/proc/filesystems</code> </a></span></dt><dt><span class="section"><a href="s2-proc-interrupts.html">17.2.10. <code class="filename">/proc/interrupts</cod
e> </a></span></dt><dt><span class="section"><a href="s2-proc-iomem.html">17.2.11. <code class="filename">/proc/iomem</code> </a></span></dt><dt><span class="section"><a href="s2-proc-ioports.html">17.2.12. <code class="filename">/proc/ioports</code> </a></span></dt><dt><span class="section"><a href="s2-proc-kcore.html">17.2.13. <code class="filename">/proc/kcore</code> </a></span></dt><dt><span class="section"><a href="s2-proc-kmsg.html">17.2.14. <code class="filename">/proc/kmsg</code> </a></span></dt><dt><span class="section"><a href="s2-proc-loadavg.html">17.2.15. <code class="filename">/proc/loadavg</code> </a></span></dt><dt><span class="section"><a href="s2-proc-locks.html">17.2.16. <code class="filename">/proc/locks</code> </a></span></dt><dt><span class="section"><a href="s2-proc-mdstat.html">17.2.17. <code class="filename">/proc/mdstat</code> </a></span></dt><dt><span class="section"><a href="s2-proc-meminfo.html">17.2.18. <code class="filename">/proc/memin
fo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-misc.html">17.2.19. <code class="filename">/proc/misc</code> </a></span></dt><dt><span class="section"><a href="s2-proc-modules.html">17.2.20. <code class="filename">/proc/modules</code> </a></span></dt><dt><span class="section"><a href="s2-proc-mounts.html">17.2.21. <code class="filename">/proc/mounts</code> </a></span></dt><dt><span class="section"><a href="s2-proc-mtrr.html">17.2.22. <code class="filename">/proc/mtrr</code> </a></span></dt><dt><span class="section"><a href="s2-proc-partitions.html">17.2.23. <code class="filename">/proc/partitions</code> </a></span></dt><dt><span class="section"><a href="s2-proc-pci.html">17.2.24. <code class="filename">/proc/pci</code> </a></span></dt><dt><span class="section"><a href="s2-proc-slabinfo.html">17.2.25. <code class="filename">/proc/slabinfo</code> </a></span></dt><dt><span class="section"><a href="s2-proc-stat.html">17.2.26. <code class="filename">/
proc/stat</code> </a></span></dt><dt><span class="section"><a href="s2-proc-swaps.html">17.2.27. <code class="filename">/proc/swaps</code> </a></span></dt><dt><span class="section"><a href="s2-proc-sysrq-trigger.html">17.2.28. <code class="filename">/proc/sysrq-trigger</code> </a></span></dt><dt><span class="section"><a href="s2-proc-uptime.html">17.2.29. <code class="filename">/proc/uptime</code> </a></span></dt><dt><span class="section"><a href="s2-proc-version.html">17.2.30. <code class="filename">/proc/version</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-directories.html">17.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dd><dl><dt><span class="section"><a href="s1-proc-directories.html#s2-proc-processdirs">17.3.1. Process Directories</a></span></dt><dt><span class="section"><a href="s2-proc-dir-bus.html">17.3.2. <code class="filename">/proc/bus/</code> </a></span></dt><dt><span class="section"><a href="s2-
proc-dir-driver.html">17.3.3. <code class="filename">/proc/driver/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-fs.html">17.3.4. <code class="filename">/proc/fs</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-irq.html">17.3.5. <code class="filename">/proc/irq/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-net.html">17.3.6. <code class="filename">/proc/net/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-scsi.html">17.3.7. <code class="filename">/proc/scsi/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-sys.html">17.3.8. <code class="filename">/proc/sys/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-dir-sysvipc.html">17.3.9. <code class="filename">/proc/sysvipc/</code> </a></span></dt><dt><span class="section"><a href="s2-proc-tty.html">17.3.10. <code class="filename">/proc/tty/</code> </a></span></dt><dt><span class="section"><a href
="s2-proc-pid.html">17.3.11. <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-proc-sysctl.html">17.4. Using the <code class="command">sysctl</code> Command</a></span></dt><dt><span class="section"><a href="s1-proc-additional-resources.html">17.5. References</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><dd><dl><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-arpwatch">18.1.1. <code class="filename">/etc/sysconfig/arpwatch</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-authconfig">18.1.2. <code class="filename">/etc/sysco
nfig/authconfig</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-autofs">18.1.3. <code class="filename">/etc/sysconfig/autofs</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-clock">18.1.4. <code class="filename">/etc/sysconfig/clock</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-desktop">18.1.5. <code class="filename">/etc/sysconfig/desktop</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-dhcpd">18.1.6. <code class="filename">/etc/sysconfig/dhcpd</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-firewall">18.1.7. <code class="filename">/etc/sysconfig/firstboot</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-i18n">18.1.8. <code class="filename">/etc
/sysconfig/i18n</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-init">18.1.9. <code class="filename">/etc/sysconfig/init</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-ip6tables">18.1.10. <code class="filename">/etc/sysconfig/ip6tables-config</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-kybd">18.1.11. <code class="filename">/etc/sysconfig/keyboard</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-named">18.1.12. <code class="filename">/etc/sysconfig/named</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-network">18.1.13. <code class="filename">/etc/sysconfig/network</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-ntpd">18.1.14. <code class="fil
ename">/etc/sysconfig/ntpd</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-radvd">18.1.15. <code class="filename">/etc/sysconfig/radvd</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-samba">18.1.16. <code class="filename">/etc/sysconfig/samba</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-selinux">18.1.17. <code class="filename">/etc/sysconfig/selinux</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-sendmail">18.1.18. <code class="filename">/etc/sysconfig/sendmail</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-spamd">18.1.19. <code class="filename">/etc/sysconfig/spamassassin</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-squid">18.1.20. <code
class="filename">/etc/sysconfig/squid</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-rcu">18.1.21. <code class="filename">/etc/sysconfig/system-config-users</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-vncservers">18.1.22. <code class="filename">/etc/sysconfig/vncservers</code> </a></span></dt><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s2-sysconfig-xinetd">18.1.23. <code class="filename">/etc/sysconfig/xinetd</code> </a></span></dt></dl></dd><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><dd><dl><dt><span class="section"><a href="s1-sysconfig-additional-resources.html#s2-sysconfig-installed-documentation"
>18.3.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Date_and_Time_Configuration.html">19. 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">19.1. Date/Time Properties Tool</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">19.1.1. Date and Time Properties</a></span></dt><dt><span class="section"><a href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Network_Time_Protocol">19.1.2. Network Time Protocol Properties</a></span></dt><dt><span class="section"><a href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Time_Zone">19.1.3. Time Zone Properties</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command
_Line_Configuration.html">19.2. Command Line Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">19.2.1. Date and Time Setup</a></span></dt><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">19.2.2. Network Time Protocol Setup</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Keyboard_Configuration.html">20. Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Keyboard_Configuration.html#s1-keyboard-layout">20.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="s1-keyboard-indicator.html">20.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="s1-keyboard-break.html">20.3. Setting Up a Typing Break</a></span></dt></dl></dd><dt><
span class="chapter"><a href="ch-The_X_Window_System.html">21. The X Window System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_X_Window_System.html#s1-x-server">21.1. The X11R7.1 Release</a></span></dt><dt><span class="section"><a href="s1-x-clients.html">21.2. Desktop Environments and Window Managers</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-clients.html#s2-x-clients-desktop">21.2.1. Desktop Environments</a></span></dt><dt><span class="section"><a href="s2-x-clients-winmanagers.html">21.2.2. Window Managers</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-server-configuration.html">21.3. X Server Configuration Files</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-server-configuration.html#s2-x-server-config-xorg.conf">21.3.1. <code class="filename">xorg.conf</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-fonts.html">21.4. Fonts</a></span></dt><dd><dl><dt><span class="section"
><a href="s1-x-fonts.html#s2-x-fonts-fontconfig">21.4.1. Fontconfig</a></span></dt><dt><span class="section"><a href="s2-x-fonts-core.html">21.4.2. Core X Font System</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-runlevels.html">21.5. Runlevels and X</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-runlevels.html#s2-x-runlevels-3">21.5.1. Runlevel 3</a></span></dt><dt><span class="section"><a href="s2-x-runlevels-5.html">21.5.2. Runlevel 5</a></span></dt></dl></dd><dt><span class="section"><a href="s1-x-additional-resources.html">21.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-x-additional-resources.html#s2-x-installed-documentation">21.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-x-useful-websites.html">21.6.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ers_and_Groups.html">22. Users and Groups</a></span></dt><dd><dl><dt><s
pan class="section"><a href="ers_and_Groups.html#s1-users-configui">22.1. User and Group Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ers_and_Groups.html#s2-redhat-config-users-user-new">22.1.1. Adding a New User</a></span></dt><dt><span class="section"><a href="ers_and_Groups.html#s2-redhat-config-users-group-new">22.1.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="ers_and_Groups.html#s2-redhat-config-users-group-properties">22.1.3. Modifying Group Properties</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html">22.2. User and Group Management Tools</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-cmd-line">22.2.1. Command Line Configuration</a></span></dt><dt><span class="section"><a href="s2-redhat-config-users-process.html">22.2.2. Explaining the Process</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-standard-users.html">22.3.
Standard Users</a></span></dt><dt><span class="section"><a href="s1-users-groups-standard-groups.html">22.4. Standard Groups</a></span></dt><dt><span class="section"><a href="s1-users-groups-private-groups.html">22.5. User Private Groups</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-groups-private-groups.html#s2-users-groups-rationale">22.5.1. Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-shadow-utilities.html">22.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="s1-users-groups-additional-resources.html">22.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">22.7.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Printer_Configuration.html">23. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Printer_Con
figuration.html#s1-printing-local-printer">23.1. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">23.2. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">23.3. Adding a Samba (SMB) Printer</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">23.4. Adding a JetDirect Printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">23.5. Selecting the Printer Model and Finishing</a></span></dt><dd><dl><dt><span class="section"><a href="s1-printing-select-model.html#s2-printing-confirm">23.5.1. Confirming Printer Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-printing-test-page.html">23.6. Printing a Test Page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">23.7. Modifying Existing Printers</a></span></dt><dd><dl><dt><span class="section"><a href="s1-printing-edit
.html#id969412">23.7.1. The <span class="guilabel"><strong>Settings</strong></span> Tab</a></span></dt><dt><span class="section"><a href="ch23s07s02.html">23.7.2. The <span class="guilabel"><strong>Policies</strong></span> Tab</a></span></dt><dt><span class="section"><a href="ch23s07s03.html">23.7.3. The <span class="guilabel"><strong>Access Control</strong></span> Tab</a></span></dt><dt><span class="section"><a href="ch23s07s04.html">23.7.4. The <span class="guilabel"><strong>Printer</strong></span> and <span class="guilabel"><strong>Job Options</strong></span>Tab</a></span></dt></dl></dd><dt><span class="section"><a href="s1-printing-managing.html">23.8. Managing Print Jobs</a></span></dt><dt><span class="section"><a href="s1-printing-additional-resources.html">23.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-printing-additional-resources.html#s2-printing-installed-docs">23.9.1. Installed Documentation</a></span></dt><dt><span class="
section"><a href="s2-printing-useful-websites.html">23.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Automated_Tasks.html">24. Automated Tasks</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Automated_Tasks.html#s1-autotasks-cron">24.1. Cron</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Automated_Tasks.html#s2-autotasks-cron-configuring">24.1.1. Configuring Cron Tasks</a></span></dt><dt><span class="section"><a href="ch-Automated_Tasks.html#s2-autotasks-cron-access">24.1.2. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="ch-Automated_Tasks.html#s2-autotasks-cron-service">24.1.3. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-at-batch.html">24.2. At and Batch</a></span></dt><dd><dl><dt><span class="section"><a href="s1-autotasks-at-batch.html#s2-autotasks-at-configuring">24.2.1. Configuring At Jobs</a></span></dt>
<dt><span class="section"><a href="s2-autotasks-batch-configuring.html">24.2.2. Configuring Batch Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-viewing.html">24.2.3. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-commandline-options.html">24.2.4. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-controlling-access.html">24.2.5. Controlling Access to At and Batch</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-service.html">24.2.6. Starting and Stopping the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">24.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-autotasks-additional-resources.html#s2-autotasks-installed-docs">24.3.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Log_Files.html">
25. Log Files</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Log_Files.html#s1-logfiles-locating">25.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="s1-logfiles-viewing.html">25.2. Viewing Log Files</a></span></dt><dt><span class="section"><a href="s1-logfiles-adding.html">25.3. Adding a Log File</a></span></dt><dt><span class="section"><a href="s1-logfiles-examining.html">25.4. Monitoring Log Files</a></span></dt></dl></dd></dl></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>15.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="ch-Console_Access.html"><strong>Next</strong>Chapter 16. Console Access</a></li></ul
></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-system-monitoring.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-system-monitoring.html
new file mode 100644
index 0000000..1470035
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/pt-system-monitoring.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="s1-logfiles-examining.html" title="25.4. Monitoring Log Files" /><link rel="next" href="ch-Gathering_System_Information.html" title="Chapter 26. Gathering System Information" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enabl
e iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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" href="ch-Gathering_System_Information.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES" class="part" title="Part IV. System Monitoring" id="pt-system-monitoring" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN,fr-FR,es-ES"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part IV. System Monitoring</h1></div></div></div><div class="partintro" title="System Monitori
ng" id="id728406"><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">26. Gathering System Information</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">26.1. System Processes</a></span></dt><dt><span class="section"><a href="s1-sysinfo-memory-usage.html">26.2. Memory Usage</a></span></dt><dt><span class="section"><a href="s1-sysinfo-filesystems.html">26.3. File Systems</a></span></dt><dt><span class="section"><a href="s1-sysinfo-hardware.html">26.4. Hardware</a></span></dt><dt><span class="section"><a href="s1-sysinfo-additional-resources.html">26.5. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">26.5.1. Installed Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-OProfile.html">27. OProfile</a></span></dt><d
d><dl><dt><span class="section"><a href="ch-OProfile.html#s1-oprofile-overview-tools">27.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="s1-oprofile-configuring.html">27.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">27.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">27.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-starting-separate.html">27.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-starting.html">27.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">27.4. Saving Data</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">27.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1
-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">27.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">27.5.2. Using <code class="command">opreport</code> on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">27.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">27.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">27.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">27.7. Example Usage</a></span></dt><dt><span class="section"><a href="s1-oprofile-gui.html">27.8. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-additional-res
ources.html">27.9. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-additional-resources.html#s1-oprofile-installed-docs">27.9.1. Installed Docs</a></span></dt><dt><span class="section"><a href="s2-oprofile-useful-websites.html">27.9.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-abrt.html">28. ABRT</a></span></dt><dd><dl><dt><span class="section"><a href="ch-abrt.html#id883853">28.1. Overview</a></span></dt><dt><span class="section"><a href="ch28s02.html">28.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="configuring.html">28.3. Configuring ABRT</a></span></dt><dt><span class="section"><a href="ch28s04.html">28.4. Plugins and Sending Crash Reports</a></span></dt><dt><span class="section"><a href="ch28s05.html">28.5. Using the Command Line Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch28s05.html#id648054">28.5.1. Viewing Crashes</a><
/span></dt><dt><span class="section"><a href="ch28s05s02.html">28.5.2. Reporting Crashes</a></span></dt><dt><span class="section"><a href="ch28s05s03.html">28.5.3. Deleting Crashes</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-examining.html"><strong>Prev</strong>25.4. 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="ch-Gathering_System_Information.html"><strong>Next</strong>Chapter 26. Gathering System Information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-define.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-define.html
new file mode 100644
index 0000000..e9f2694
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-define.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Defining the Console</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Console_Access.html" title="Chapter 16. Console Access" /><link rel="prev" href="s1-access-console-program.html" title="16.2. Disabling Console Program Access" /><link rel="next" href="s1-access-console-files.html" title="16.4. Making Files Accessible From the Console" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to v
iew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-access-console-program.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-access-console-files.html"><strong>Next</strong></a></li></ul><div class="section" title="16.3. Defining the Console" id="s1-access-console-define"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-console-define">16.3. Defining the Console</h2></div></div></div><div class="para">
+ The <code class="filename">pam_console.so</code> module uses the <code class="filename">/etc/security/console.perms</code> file to determine the permissions for users at the system console. The syntax of the file is very flexible; you can edit the file so that these instructions no longer apply. However, the default file has a line that looks like this:
+ </div><pre class="screen">
+<code class="command"><console>=tty[0-9][0-9]* vc/[0-9][0-9]* :[0-9]\.[0-9] :[0-9]</code>
+</pre><div class="para">
+ When users log in, they are attached to some sort of named terminal, which can be either an X server with a name like <code class="command">:0</code> or <code class="command">mymachine.example.com:1.0</code>, or a device like <code class="filename">/dev/ttyS0</code> or <code class="filename">/dev/pts/2</code>. The default is to define that local virtual consoles and local X servers are considered local, but if you want to consider the serial terminal next to you on port <code class="filename">/dev/ttyS1</code> to also be local, you can change that line to read:
+ </div><pre class="screen">
+<code class="command"><console>=tty[0-9][0-9]* vc/[0-9][0-9]* :[0-9]\.[0-9] :[0-9] /dev/ttyS1</code>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-access-console-program.html"><strong>Prev</strong>16.2. Disabling Console Program Access</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-access-console-files.html"><strong>Next</strong>16.4. Making Files Accessible From the Console</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-enable.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-enable.html
new file mode 100644
index 0000000..7716491
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-enable.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>16.5. Enabling Console Access for Other Applications</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Console_Access.html" title="Chapter 16. Console Access" /><link rel="prev" href="s1-access-console-files.html" title="16.4. Making Files Accessible From the Console" /><link rel="next" href="s1-access-floppy.html" title="16.6. The floppy Group" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to
view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-access-console-files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-access-floppy.html"><strong>Next</strong></a></li></ul><div class="section" title="16.5. Enabling Console Access for Other Applications" id="s1-access-console-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-console-enable">16.5. Enabling Console Access for Other Applications</h2></div></div></div><div class="para">
+ To make other applications accessible to console users, a bit more work is required.
+ </div><div class="para">
+ First of all, console access <span class="emphasis"><em>only</em></span> works for applications which reside in <code class="filename">/sbin/</code> or <code class="filename">/usr/sbin/</code>, so the application that you wish to run must be there. After verifying that, perform the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Create a link from the name of your application, such as our sample <code class="filename">foo</code> program, to the <code class="command">/usr/bin/consolehelper</code> application:
+ </div><pre class="screen">
+<code class="command">cd /usr/bin ln -s consolehelper foo</code>
+</pre></li><li class="listitem"><div class="para">
+ Create the file <code class="filename">/etc/security/console.apps/foo</code>:
+ </div><pre class="screen">
+<code class="command">touch /etc/security/console.apps/foo</code>
+</pre></li><li class="listitem"><div class="para">
+ Create a PAM configuration file for the <code class="filename">foo</code> service in <code class="filename">/etc/pam.d/</code>. An easy way to do this is to copy the PAM configuration file of the <code class="command">halt</code> service, and then modify the copy if you want to change the behavior:
+ </div><pre class="screen">
+<code class="command">cp /etc/pam.d/halt /etc/pam.d/foo</code>
+</pre></li></ol></div><div class="para">
+ Now, when <code class="command">/usr/bin/<em class="replaceable"><code>foo</code></em> </code> is executed, <code class="command">consolehelper</code> is called, which authenticates the user with the help of <code class="command">/usr/sbin/userhelper</code>. To authenticate the user, <code class="command">consolehelper</code> asks for the user's password if <code class="filename">/etc/pam.d/<em class="replaceable"><code>foo</code></em> </code> is a copy of <code class="filename">/etc/pam.d/halt</code> (otherwise, it does precisely what is specified in <code class="filename">/etc/pam.d/<em class="replaceable"><code>foo</code></em> </code>) and then runs <code class="filename">/usr/sbin/<em class="replaceable"><code>foo</code></em> </code> with root permissions.
+ </div><div class="para">
+ In the PAM configuration file, an application can be configured to use the <em class="firstterm">pam_timestamp</em> module to remember (or cache) a successful authentication attempt. When an application is started and proper authentication is provided (the root password), a timestamp file is created. By default, a successful authentication is cached for five minutes. During this time, any other application that is configured to use <code class="filename">pam_timestamp</code> and run from the same session is automatically authenticated for the user — the user does not have to enter the root password again.
+ </div><div class="para">
+ This module is included in the <code class="filename">pam</code> package. To enable this feature, add the following lines to your PAM configuration file in <code class="filename">etc/pam.d/</code>:
+ </div><pre class="screen">auth include config-util account include config-util session include config-util</pre><div class="para">
+ These lines can be copied from any of the <code class="filename">/etc/pam.d/system-config-<em class="replaceable"><code>*</code></em> </code> configuration files. Note that these lines must be added <span class="emphasis"><em>below</em></span> any other <code class="computeroutput">auth sufficient</code> <code class="computeroutput">session optional</code> lines in your PAM configuration file.
+ </div><div class="para">
+ If an application configured to use <code class="filename">pam_timestamp</code> is successfully authenticated from the Applications (the main menu on the panel), the
+ <span class="inlinemediaobject"><img src="images/pam-icon.png" /></span>
+ icon is displayed in the notification area of the panel if you are running the <span class="application"><strong>GNOME</strong></span> or <span class="application"><strong>KDE</strong></span> desktop environment. After the authentication expires (the default is five minutes), the icon disappears.
+ </div><div class="para">
+ The user can select to forget the cached authentication by clicking on the icon and selecting the option to forget authentication.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-access-console-files.html"><strong>Prev</strong>16.4. Making Files Accessible From the Console</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-access-floppy.html"><strong>Next</strong>16.6. The floppy Group</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-files.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-files.html
new file mode 100644
index 0000000..7a7ef02
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-files.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>16.4. Making Files Accessible From the Console</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Console_Access.html" title="Chapter 16. Console Access" /><link rel="prev" href="s1-access-console-define.html" title="16.3. Defining the Console" /><link rel="next" href="s1-access-console-enable.html" title="16.5. Enabling Console Access for Other Applications" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is a
n iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-access-console-define.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-access-console-enable.html"><strong>Next</strong></a></li></ul><div class="section" title="16.4. Making Files Accessible From the Console" id="s1-access-console-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-console-files">16.4. Making Files Accessible From the Console</h2></div></div></div><div class="para">
+ The default settings for individual device classes and permission definitions are defined in <code class="filename">/etc/security/console.perms.d/50-default.perms</code>. To edit file and device permissions, it is advisable to create a new default file in <code class="filename">/etc/security/console.perms.d/</code> containing your preferred settings for a specified set of files or devices. The name of the new default file must begin with a number higher than 50 (for example, <code class="filename">51-default.perms</code>) in order to override <code class="filename">50-default.perms</code>.
+ </div><div class="para">
+ To do this, create a new file named <code class="filename">51-default.perms</code> in <code class="filename">/etc/security/console.perms.d/</code>:
+ </div><pre class="screen">
+<code class="command">touch /etc/security/console.perms.d/51-default.perms</code>
+</pre><div class="para">
+ Open the original default <code class="filename">perms</code> file, <code class="filename">50-default.perms</code>. The first section defines <em class="firstterm">device classes</em>, with lines similar to the following:
+ </div><pre class="screen"><floppy>=/dev/fd[0-1]* \ /dev/floppy/* /mnt/floppy* <sound>=/dev/dsp* /dev/audio* /dev/midi* \ /dev/mixer* /dev/sequencer \ /dev/sound/* /dev/beep \ /dev/snd/* <cdrom>=/dev/cdrom* /dev/cdroms/* /dev/cdwriter* /mnt/cdrom*</pre><div class="para">
+ Items enclosed in brackets name the device; in the above example, <code class="computeroutput"><cdrom></code> refers to the CD-ROM drive. To add a new device, do not define it in the default <code class="filename">50-default.perms</code> file; instead, define it in <code class="filename">51-default.perms</code>. For example, to define a scanner, add the following line to <code class="filename">51-default.perms</code>:
+ </div><pre class="screen"><scanner>=/dev/scanner /dev/usb/scanner*</pre><div class="para">
+ Of course, you must use the appropriate name for the device. Ensure that <code class="filename">/dev/scanner</code> is really your scanner and not some other device, such as your hard drive.
+ </div><div class="para">
+ Once you have properly defined a device or file, the second step is to specify its <em class="firstterm">permission definitions</em>. The second section of <code class="filename">/etc/security/console.perms.d/50-default.perms</code> defines this, with lines similar to the following:
+ </div><pre class="screen"><console> 0660 <floppy> 0660 root.floppy <console> 0600 <sound> 0640 root <console> 0600 <cdrom> 0600 root.disk</pre><div class="para">
+ To define permissions for a scanner, add a line similar to the following in <code class="filename">51-default.perms</code>:
+ </div><pre class="screen">
+<code class="command"><console> 0600 <scanner> 0600 root</code>
+</pre><div class="para">
+ Then, when you log in at the console, you are given ownership of the <code class="filename">/dev/scanner</code> device with the permissions of 0600 (readable and writable by you only). When you log out, the device is owned by root, and still has the permissions 0600 (now readable and writable by root only).
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ You must <span class="emphasis"><em>never</em></span> edit the default <code class="filename">50-default.perms</code> file. To edit permissions for a device already defined in <code class="filename">50-default.perms</code>, add the desired permission definition for that device in <code class="filename">51-default.perms</code>. This will override whatever permissions are defined in <code class="filename">50-default.perms</code>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-access-console-define.html"><strong>Prev</strong>16.3. Defining the Console</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-access-console-enable.html"><strong>Next</strong>16.5. Enabling Console Access for Other Applicati...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-program.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-program.html
new file mode 100644
index 0000000..fecb390
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-console-program.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Disabling Console Program Access</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Console_Access.html" title="Chapter 16. Console Access" /><link rel="prev" href="ch-Console_Access.html" title="Chapter 16. Console Access" /><link rel="next" href="s1-access-console-define.html" title="16.3. Defining the Console" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browse
r or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Console_Access.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-access-console-define.html"><strong>Next</strong></a></li></ul><div class="section" title="16.2. Disabling Console Program Access" id="s1-access-console-program"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-console-program">16.2. Disabling Console Program Access</h2></div></div></div><div class="para">
+ To disable access by users to console programs, run the following command as root:
+ </div><pre class="screen">
+<code class="command">rm -f /etc/security/console.apps/*</code>
+</pre><div class="para">
+ In environments where the console is otherwise secured (BIOS and boot loader passwords are set, <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Delete</strong></span> is disabled, the power and reset switches are disabled, and so forth), you may not want to allow any user at the console to run <code class="command">poweroff</code>, <code class="command">halt</code>, and <code class="command">reboot</code>, which are accessible from the console by default.
+ </div><div class="para">
+ To disable these abilities, run the following commands as root:
+ </div><pre class="screen"><code class="command">rm -f /etc/security/console.apps/poweroff</code>
+<code class="command">rm -f /etc/security/console.apps/halt</code>
+<code class="command">rm -f /etc/security/console.apps/reboot</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Console_Access.html"><strong>Prev</strong>Chapter 16. Console Access</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-access-console-define.html"><strong>Next</strong>16.3. Defining the Console</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-floppy.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-floppy.html
new file mode 100644
index 0000000..04cfc8a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-access-floppy.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.6. The floppy Group</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Console_Access.html" title="Chapter 16. Console Access" /><link rel="prev" href="s1-access-console-enable.html" title="16.5. Enabling Console Access for Other Applications" /><link rel="next" href="ch-proc.html" title="Chapter 17. The proc File System" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your
browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-access-console-enable.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="16.6. The floppy Group" id="s1-access-floppy"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-access-floppy">16.6. The <code class="filename">floppy</code> Group</h2></div></div></div><div class="para">
+ If, for whatever reason, console access is not appropriate for you and your non-root users require access to your system's diskette drive, this can be done using the <code class="filename">floppy</code> group. Add the user(s) to the <code class="filename">floppy</code> group using the tool of your choice. For example, the <code class="command">gpasswd</code> command can be used to add user <code class="command">fred</code> to the <code class="filename">floppy</code> group:
+ </div><pre class="screen">
+<code class="command">gpasswd -a fred floppy</code>
+</pre><div class="para">
+ Now, user <code class="command">fred</code> is able to access the system's diskette drive from the console.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-access-console-enable.html"><strong>Prev</strong>16.5. Enabling Console Access for Other Applicati...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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 17. The proc File System</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-additional-resources.html
new file mode 100644
index 0000000..66d9daf
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-additional-resources.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.9. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-use-new-key.html" title="11.8.6. How to configure the server to use the new key" /><link rel="next" href="ch-FTP.html" title="Chapter 12. FTP" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browse
r or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-use-new-key.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-FTP.html"><strong>Next</strong></a></li></ul><div class="section" title="11.9. Additional Resources" id="s1-apache-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-additional-resources">11.9. Additional Resources</h2></div></div></div><a id="id935663" class="indexterm"></a><div class="para">
+ To learn more about the Apache HTTP Server, refer to the following resources.
+ </div><div class="section" title="11.9.1. Useful Websites" id="s2-apache-additional-resources-web"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-additional-resources-web">11.9.1. Useful Websites</h3></div></div></div><a id="id935691" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/">http://httpd.apache.org/</a> — The official website for the Apache HTTP Server with documentation on all the directives and default modules.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.modssl.org/">http://www.modssl.org/</a> — The official website for <code class="filename">mod_ssl</code>.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.apacheweek.com/">http://www.apacheweek.com/</a> — A comprehensive online weekly newsletter about all things Apache.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-use-new-key.html"><strong>Prev</strong>11.8.6. How to configure the server to use the ne...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-FTP.html"><strong>Next</strong>Chapter 12. FTP</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-addmods.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-addmods.html
new file mode 100644
index 0000000..a7af087
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-addmods.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.6. Adding 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-containers.html" title="11.5.3. MPM Specific Server-Pool Directives" /><link rel="next" href="s1-apache-virtualhosts.html" title="11.7. Virtual Hosts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade
your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-containers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-virtualhosts.html"><strong>Next</strong></a></li></ul><div class="section" title="11.6. Adding Modules" id="s1-apache-addmods"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-addmods">11.6. Adding Modules</h2></div></div></div><a id="id811166" class="indexterm"></a><a id="id811184" class="indexterm"></a><a id="id811199" class="indexterm"></a><a id="id811213" class="indexterm"></a><a id="id811224" class="indexterm"></a><div c
lass="para">
+ The Apache HTTP Server is distributed with a number of modules. More information about Apache HTTP modules can be found on <a href="http://httpd.apache.org/docs/2.2/mod/">http://httpd.apache.org/docs/2.2/mod/</a>.
+ </div><div class="para">
+ The Apache HTTP Server supports <em class="firstterm">Dynamically Shared Objects</em> (<em class="firstterm">DSO</em>s), or modules, which can easily be loaded at runtime as necessary.
+ </div><div class="para">
+ The Apache Project provides complete DSO documentation online at <a href="http://httpd.apache.org/docs/2.2/dso.html">http://httpd.apache.org/docs/2.2/dso.html</a>. Or, if the <code class="filename">http-manual</code> package is installed, documentation about DSOs can be found online at <a href="http://localhost/manual/mod/">http://localhost/manual/mod/</a>.
+ </div><div class="para">
+ For the Apache HTTP Server to use a DSO, it must be specified in a <code class="command">LoadModule</code> directive within <code class="filename">/etc/httpd/conf/httpd.conf</code>. If the module is provided by a separate package, the line must appear within the modules configuration file in the <code class="filename">/etc/httpd/conf.d/</code> directory. Refer to <a class="xref" href="s1-apache-config.html#s2-apache-loadmodule" title="LoadModule">LoadModule</a> for more information.
+ </div><div class="para">
+ If adding or deleting modules from <code class="filename">http.conf</code>, Apache HTTP Server must be reloaded or restarted, as referred to in <a class="xref" href="s1-apache-startstop.html" title="11.3. Starting and Stopping httpd">Section 11.3, “Starting and Stopping <code class="command">httpd</code> ”</a>.
+ </div><div class="para">
+ If creating a new module, first install the <code class="filename">httpd-devel</code> package which contains the include files, the header files, as well as the <em class="firstterm">APache eXtenSion</em> (<code class="command">/usr/sbin/apxs</code>) application, which uses the include files and the header files to compile DSOs.
+ </div><div class="para">
+ After writing a module, use <code class="command">/usr/sbin/apxs</code> to compile the module sources outside the Apache source tree. For more information about using the <code class="command">/usr/sbin/apxs</code> command, refer to the the Apache documentation online at <a href="http://httpd.apache.org/docs/2.2/dso.html">http://httpd.apache.org/docs/2.2/dso.html</a> as well as the <code class="command">apxs</code> man page.
+ </div><div class="para">
+ Once compiled, put the module in the <code class="filename">/usr/lib/httpd/modules/</code> directory. For 64-bit Fedora hosts using the defaut 64-bit user-space, this path will be <code class="filename">/usr/lib64/httpd/modules/</code>. Then add a <code class="command">LoadModule</code> line to the <code class="filename">httpd.conf</code>, using the following structure:
+ </div><pre class="screen">
+<code class="command">LoadModule <em class="replaceable"><code><module-name> <path/to/module.so></code></em> </code>
+</pre><div class="para">
+ Where <em class="replaceable"><code><module-name></code></em> is the name of the module and <em class="replaceable"><code><path/to/module.so></code></em> is the path to the DSO.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-mpm-containers.html"><strong>Prev</strong>11.5.3. MPM Specific Server-Pool 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-virtualhosts.html"><strong>Next</strong>11.7. Virtual Hosts</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-config-ui.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-config-ui.html
new file mode 100644
index 0000000..ce51f44
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-config-ui.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>11.4. Apache HTTP Server 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-startstop.html" title="11.3. Starting and Stopping httpd" /><link rel="next" href="s2-httpd-default-settings.html" title="11.4.2. Default Settings" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-startstop.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-httpd-default-settings.html"><strong>Next</strong></a></li></ul><div class="section" title="11.4. Apache HTTP Server Configuration" id="s1-apache-config-ui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-config-ui">11.4. Apache HTTP Server Configuration</h2></div></div></div><a id="id655473" class="indexterm"></a><a id="id655488" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>HTTP Configuration Tool</strong></span> allows you to configure the <code class="filename">/etc/httpd/conf/httpd.conf</code> configuration file for the Apache HTTP Server. It does not use the old <code class="filename">srm.conf</code> or <code class="filename">access.conf</code> configuration files; leave them empty. Through the graphical interface, you can configure directives such as virtual hosts, logging attributes, and maximum number of connections. To start the HTTD Configuration Tool, click on <code class="filename">System > Administration > Server Settings > HTTP</code>.
+ </div><a id="id655531" class="indexterm"></a><div class="para">
+ Only modules provided with Fedora can be configured with the <span class="application"><strong>HTTP Configuration Tool</strong></span>. If additional modules are installed, they can not be configured using this tool.
+ </div><div class="warning"><h2>Caution</h2><a id="id691874" class="indexterm"></a><div class="para">
+ Do not edit the <code class="filename">/etc/httpd/conf/httpd.conf</code> configuration file by hand if you wish to use this tool. The <span class="application"><strong>HTTP Configuration Tool</strong></span> generates this file after you save your changes and exit the program. If you want to add additional modules or configuration options that are not available in <span class="application"><strong>HTTP Configuration Tool</strong></span>, you cannot use this tool.
+ </div></div><div class="para">
+ The general steps for configuring the Apache HTTP Server using the <span class="application"><strong>HTTP Configuration Tool</strong></span> are as follows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Configure the basic settings under the <span class="guilabel"><strong>Main</strong></span> tab.
+ </div></li><li class="listitem"><div class="para">
+ Click on the <span class="guilabel"><strong>Virtual Hosts</strong></span> tab and configure the default settings.
+ </div></li><li class="listitem"><div class="para">
+ Under the <span class="guilabel"><strong>Virtual Hosts</strong></span> tab, configure the Default Virtual Host.
+ </div></li><li class="listitem"><div class="para">
+ To serve more than one URL or virtual host, add any additional virtual hosts.
+ </div></li><li class="listitem"><div class="para">
+ Configure the server settings under the <span class="guilabel"><strong>Server</strong></span> tab.
+ </div></li><li class="listitem"><div class="para">
+ Configure the connections settings under the <span class="guilabel"><strong>Performance Tuning</strong></span> tab.
+ </div></li><li class="listitem"><div class="para">
+ Copy all necessary files to the <code class="filename">DocumentRoot</code> and <code class="filename">cgi-bin</code> directories.
+ </div></li><li class="listitem"><div class="para">
+ Exit the application and select to save your settings.
+ </div></li></ol></div><div class="section" title="11.4.1. Basic Settings" id="s2-httpd-basic-settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-httpd-basic-settings">11.4.1. Basic Settings</h3></div></div></div><div class="para">
+ Use the <span class="guilabel"><strong>Main</strong></span> tab to configure the basic server settings.
+ </div><div class="figure" title="Figure 11.1. Basic Settings" id="httpd-main"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-main.png" alt="Basic Settings" /><div class="longdesc"><div class="para">
+ Basic Settings
+ </div></div></div></div><h6>Figure 11.1. Basic Settings</h6></div><br class="figure-break" /><a id="id934984" class="indexterm"></a><div class="para">
+ Enter a fully qualified domain name that you have the right to use in the <span class="guilabel"><strong>Server Name</strong></span> text area. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#servername"><code class="command">ServerName</code> </a> directive in <code class="filename">httpd.conf</code>. The <code class="command">ServerName</code> directive sets the hostname of the Web server. It is used when creating redirection URLs. If you do not define a server name, the Web server attempts to resolve it from the IP address of the system. The server name does not have to be the domain name resolved from the IP address of the server. For example, you might set the server name to www.example.com while the server's real DNS name is foo.example.com.
+ </div><a id="id935031" class="indexterm"></a><div class="para">
+ Enter the email address of the person who maintains the Web server in the <span class="guilabel"><strong>Webmaster email address</strong></span> text area. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#serveradmin"><code class="command">ServerAdmin</code> </a> directive in <code class="filename">httpd.conf</code>. If you configure the server's error pages to contain an email address, this email address is used so that users can report a problem to the server's administrator. The default value is root at localhost.
+ </div><a id="id935072" class="indexterm"></a><div class="para">
+ Use the <span class="guilabel"><strong>Available Addresses</strong></span> area to define the ports on which the server accepts incoming requests. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/mpm_common.html#listen"><code class="command">Listen</code> </a> directive in <code class="filename">httpd.conf</code>. By default, Red Hat configures the Apache HTTP Server to listen to port 80 for non-secure Web communications.
+ </div><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button to define additional ports on which to accept requests. A window as shown in <a class="xref" href="s1-apache-config-ui.html#httpd-listen" title="Figure 11.2. Available Addresses">Figure 11.2, “Available Addresses”</a> appears. Either choose the <span class="guilabel"><strong>Listen to all addresses</strong></span> option to listen to all IP addresses on the defined port or specify a particular IP address over which the server accepts connections in the <span class="guilabel"><strong>Address</strong></span> field. Only specify one IP address per port number. To specify more than one IP address with the same port number, create an entry for each IP address. If at all possible, use an IP address instead of a domain name to prevent a DNS lookup failure. Refer to <a href="http://httpd.apache.org/docs/2.2/dns-caveats.html">http://httpd.apache.org/docs/2.2/dns-caveats.html</a> for more information about
<em class="citetitle">Issues Regarding DNS and Apache</em>.
+ </div><div class="para">
+ Entering an asterisk (*) in the <span class="guilabel"><strong>Address</strong></span> field is the same as choosing <span class="guilabel"><strong>Listen to all addresses</strong></span>. Clicking the <span class="guibutton"><strong>Edit</strong></span> button in the <span class="guilabel"><strong>Available Addresses</strong></span> frame shows the same window as the <span class="guibutton"><strong>Add</strong></span> button except with the fields populated for the selected entry. To delete an entry, select it and click the <span class="guibutton"><strong>Delete</strong></span> button.
+ </div><div class="note"><h2>Tip</h2><div class="para">
+ If you set the server to listen to a port under 1024, you must be root to start it. For port 1024 and above, <code class="command">httpd</code> can be started as a regular user.
+ </div></div><div class="figure" title="Figure 11.2. Available Addresses" id="httpd-listen"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-listen.png" alt="Available Addresses" /><div class="longdesc"><div class="para">
+ Available Addresses
+ </div></div></div></div><h6>Figure 11.2. Available Addresses</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-startstop.html"><strong>Prev</strong>11.3. Starting and Stopping httpd </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-httpd-default-settings.html"><strong>Next</strong>11.4.2. Default Settings</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-config.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-config.html
new file mode 100644
index 0000000..06ba1d4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-config.html
@@ -0,0 +1,327 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Configuration Directives in httpd.conf</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-httpd-default-settings.html" title="11.4.2. Default Settings" /><link rel="next" href="s2-apache-sslcommands.html" title="11.5.2. Configuration Directives for SSL" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an
iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-httpd-default-settings.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-apache-sslcommands.html"><strong>Next</strong></a></li></ul><div class="section" title="11.5. Configuration Directives in httpd.conf" id="s1-apache-config"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-config">11.5. Configuration Directives in <code class="filename">httpd.conf</code> </h2></div></div></div><a id="id803029" class="indexterm"></a><a id="id803044" class="indexterm"></a><a id="id803058" cla
ss="indexterm"></a><a id="id803073" class="indexterm"></a><a id="id803095" class="indexterm"></a><div class="para">
+ The Apache HTTP Server configuration file is <code class="filename">/etc/httpd/conf/httpd.conf</code>. The <code class="filename">httpd.conf</code> file is well-commented and mostly self-explanatory. The default configuration works for most situations; however, it is a good idea to become familiar some of the more important configuration options.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ With the release of Apache HTTP Server 2.2, many configuration options have changed. If migrating from version 1.3 to 2.2, please firstly read <a class="xref" href="s3-httpd-v2-mig.html" title="11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0">Section 11.2.2, “Migrating Apache HTTP Server 1.3 Configuration Files to 2.0”</a>.
+ </div></div><div class="section" title="11.5.1. General Configuration Tips" id="s2-apache-tips"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-tips">11.5.1. General Configuration Tips</h3></div></div></div><div class="para">
+ If configuring the Apache HTTP Server, edit <code class="filename">/etc/httpd/conf/httpd.conf</code> and then either reload, restart, or stop and start the <code class="command">httpd</code> process as outlined in <a class="xref" href="s1-apache-startstop.html" title="11.3. Starting and Stopping httpd">Section 11.3, “Starting and Stopping <code class="command">httpd</code> ”</a>.
+ </div><div class="para">
+ Before editing <code class="filename">httpd.conf</code>, make a copy the original file. Creating a backup makes it easier to recover from mistakes made while editing the configuration file.
+ </div><div class="para">
+ If a mistake is made and the Web server does not work correctly, first review recently edited passages in <code class="filename">httpd.conf</code> to verify there are no typos.
+ </div><div class="para">
+ Next look in the Web server's error log, <code class="filename">/var/log/httpd/error_log</code>. The error log may not be easy to interpret, depending on your level of expertise. However, the last entries in the error log should provide useful information.
+ </div><div class="para">
+ The following subsections contain a list of short descriptions for many of the directives included in <code class="filename">httpd.conf</code>. These descriptions are not exhaustive. For more information, refer to the Apache documentation online at <a href="http://httpd.apache.org/docs/2.2/">http://httpd.apache.org/docs/2.2/</a>.
+ </div><div class="para">
+ For more information about <code class="filename">mod_ssl</code> directives, refer to the documentation online at <a href="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html">http://httpd.apache.org/docs/2.2/mod/mod_ssl.html</a>.
+ </div><a id="id914161" class="indexterm"></a><a id="id914179" class="indexterm"></a><div class="formalpara" id="s2-apache-accessfilename"><h5 class="formalpara">AccessFileName</h5><a id="id914204" class="indexterm"></a><a id="id757083" class="indexterm"></a>
+ <code class="command">AccessFileName</code> names the file which the server should use for access control information in each directory. The default is <code class="filename">.htaccess</code>.
+ </div><div class="para">
+ Immediately after the <code class="command">AccessFileName</code> directive, a set of <code class="command">Files</code> tags apply access control to any file beginning with a <code class="filename">.ht</code>. These directives deny Web access to any <code class="filename">.htaccess</code> files (or other files which begin with <code class="filename">.ht</code>) for security reasons.
+ </div><div class="formalpara" id="s2-apache-action"><h5 class="formalpara">Action</h5><a id="id757153" class="indexterm"></a><a id="id757171" class="indexterm"></a>
+ <code class="command">Action</code> specifies a MIME content type and CGI script pair, so that when a file of that media type is requested, a particular CGI script is executed.
+ </div><div class="formalpara" id="s2-apache-adddescription"><h5 class="formalpara">AddDescription</h5><a id="id757215" class="indexterm"></a><a id="id757233" class="indexterm"></a>
+ When using <code class="command">FancyIndexing</code> as an <code class="command">IndexOptions</code> parameter, the <code class="command">AddDescription</code> directive can be used to display user-specified descriptions for certain files or file types in a server generated directory listing. The <code class="command">AddDescription</code> directive supports listing specific files, wildcard expressions, or file extensions.
+ </div><div class="formalpara" id="s2-apache-addencoding"><h5 class="formalpara">AddEncoding</h5><a id="id866450" class="indexterm"></a><a id="id866468" class="indexterm"></a>
+ <code class="command">AddEncoding</code> names file name extensions which should specify a particular encoding type. <code class="command">AddEncoding</code> can also be used to instruct some browsers to uncompress certain files as they are downloaded.
+ </div><div class="formalpara" id="s2-apache-addhandler"><h5 class="formalpara">AddHandler</h5><a id="id866517" class="indexterm"></a><a id="id866535" class="indexterm"></a><a id="id866554" class="indexterm"></a>
+ <code class="command">AddHandler</code> maps file extensions to specific handlers. For example, the <code class="command">cgi-script</code> handler can be matched with the extension <code class="filename">.cgi</code> to automatically treat a file ending with <code class="filename">.cgi</code> as a CGI script. The following is a sample <code class="command">AddHandler</code> directive for the <code class="filename">.cgi</code> extension.
+ </div><pre class="screen">
+<code class="command">AddHandler cgi-script .cgi</code>
+</pre><div class="para">
+ This directive enables CGIs outside of the <code class="filename">cgi-bin</code> to function in any directory on the server which has the <code class="command">ExecCGI</code> option within the directories container. Refer to <a class="xref" href="s1-apache-config.html#s2-apache-directory" title="Directory">Directory</a> for more information about setting the <code class="command">ExecCGI</code> option for a directory.
+ </div><div class="para">
+ In addition to CGI scripts, the <code class="command">AddHandler</code> directive is used to process server-parsed HTML and image-map files.
+ </div><div class="formalpara" id="s2-apache-addicon"><h5 class="formalpara">AddIcon</h5><a id="id870029" class="indexterm"></a><a id="id870047" class="indexterm"></a>
+ <code class="command">AddIcon</code> specifies which icon to show in server generated directory listings for files with certain extensions. For example, the Web server is set to show the icon <code class="filename">binary.gif</code> for files with <code class="filename">.bin</code> or <code class="filename">.exe</code> extensions.
+ </div><div class="formalpara" id="s2-apache-addiconbyencoding"><h5 class="formalpara">AddIconByEncoding</h5><a id="id870103" class="indexterm"></a><a id="id849953" class="indexterm"></a>
+ This directive names icons which are displayed by files with MIME encoding in server generated directory listings. For example, by default, the Web server shows the <code class="filename">compressed.gif</code> icon next to MIME encoded x-compress and x-gzip files in server generated directory listings.
+ </div><div class="formalpara" id="s2-apache-addiconbytype"><h5 class="formalpara">AddIconByType</h5><a id="id849998" class="indexterm"></a><a id="id850017" class="indexterm"></a>
+ This directive names icons which are displayed next to files with MIME types in server generated directory listings. For example, the server shows the icon <code class="filename">text.gif</code> next to files with a mime-type of <code class="computeroutput">text</code>, in server generated directory listings.
+ </div><div class="formalpara" id="s2-apache-addlanguage"><h5 class="formalpara">AddLanguage</h5><a id="id850065" class="indexterm"></a><a id="id850083" class="indexterm"></a>
+ <code class="command">AddLanguage</code> associates file name extensions with specific languages. This directive is useful for Apache HTTP Servers which serve content in multiple languages based on the client Web browser's language settings.
+ </div><div class="formalpara" id="s2-apache-addtype"><h5 class="formalpara">AddType</h5><a id="id990644" class="indexterm"></a><a id="id990662" class="indexterm"></a><a id="id990680" class="indexterm"></a><a id="id990691" class="indexterm"></a>
+ Use the <code class="command">AddType</code> directive to define or override a default MIME type and file extension pairs. The following example directive tells the Apache HTTP Server to recognize the <code class="command">.tgz</code> file extension:
+ </div><pre class="screen">
+<code class="command">AddType application/x-tar .tgz</code>
+</pre><div class="formalpara" id="s2-apache-alias"><h5 class="formalpara">Alias</h5><a id="id990743" class="indexterm"></a><a id="id990762" class="indexterm"></a>
+ The <code class="command">Alias</code> setting allows directories outside the <code class="command">DocumentRoot</code> directory to be accessible. Any URL ending in the alias automatically resolves to the alias' path. By default, one alias for an <code class="filename">icons/</code> directory is already set up. An <code class="filename">icons/</code> directory can be accessed by the Web server, but the directory is not in the <code class="command"> DocumentRoot</code>.
+ </div><div class="formalpara" id="s2-apache-allow"><h5 class="formalpara">Allow</h5><a id="id795434" class="indexterm"></a><a id="id795452" class="indexterm"></a>
+ <code class="command">Allow</code> specifies which client can access a given directory. The client can be <code class="command">all</code>, a domain name, an IP address, a partial IP address, a network/netmask pair, and so on. The <code class="command">DocumentRoot</code> directory is configured to <code class="command">Allow</code> requests from <code class="command">all</code>, meaning everyone has access.
+ </div><div class="formalpara" id="s2-apache-allowoverride"><h5 class="formalpara">AllowOverride</h5><a id="id795512" class="indexterm"></a><a id="id795531" class="indexterm"></a>
+ The <code class="command">AllowOverride</code> directive sets whether any <code class="command">Options</code> can be overridden by the declarations in an <code class="filename">.htaccess</code> file. By default, both the root directory and the <code class="command">DocumentRoot</code> are set to allow no <code class="filename">.htaccess</code> overrides.
+ </div><div class="formalpara" id="s2-apache-browsermatch"><h5 class="formalpara">BrowserMatch</h5><a id="id944167" class="indexterm"></a><a id="id944186" class="indexterm"></a>
+ The <code class="command">BrowserMatch</code> directive allows the server to define environment variables and take appropriate actions based on the User-Agent HTTP header field — which identifies the client's Web browser type. By default, the Web server uses <code class="command">BrowserMatch</code> to deny connections to specific browsers with known problems and also to disable keepalives and HTTP header flushes for browsers that are known to have problems with those actions.
+ </div><div class="formalpara" id="s2-apache-cachedirectives"><h5 class="formalpara">Cache Directives</h5><a id="id944235" class="indexterm"></a><a id="id944246" class="indexterm"></a><a id="id944256" class="indexterm"></a>
+ A number of commented cache directives are supplied by the default Apache HTTP Server configuration file. In most cases, uncommenting these lines by removing the hash mark (<code class="command">#</code>) from the beginning of the line is sufficient. The following, however, is a list of some of the more important cache-related directives.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">CacheEnable</code> — Specifies whether the cache is a disk, memory, or file descriptor cache. By default <code class="command">CacheEnable</code> configures a disk cache for URLs at or below <code class="filename">/</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">CacheRoot</code> — Specifies the name of the directory containing cached files. The default <code class="command">CacheRoot</code> is the <code class="filename">/var/httpd/proxy/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">CacheSize</code> — Specifies how much space the cache can use in kilobytes. The default <code class="command">CacheSize</code> is <code class="command">5</code> KB.
+ </div></li></ul></div><div class="para">
+ The following is a list of some of the other common cache-related directives.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">CacheMaxExpire</code> — Specifies how long HTML documents are retained (without a reload from the originating Web server) in the cache. The default is <code class="command">24</code> hours (<code class="command">86400</code> seconds).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">CacheLastModifiedFactor</code> — Specifies the creation of an expiry (expiration) date for a document which did not come from its originating server with its own expiry set. The default <code class="command">CacheLastModifiedFactor</code> is set to <code class="command">0.1</code>, meaning that the expiry date for such documents equals one-tenth of the amount of time since the document was last modified.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">CacheDefaultExpire</code> — Specifies the expiry time in hours for a document that was received using a protocol that does not support expiry times. The default is set to <code class="command">1</code> hour (<code class="command">3600</code> seconds).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">NoProxy</code> — Specifies a space-separated list of subnets, IP addresses, domains, or hosts whose content is not cached. This setting is most useful for Intranet sites.
+ </div></li></ul></div><div class="formalpara" id="s2-apache-cachenegotiateddocs"><h5 class="formalpara">CacheNegotiatedDocs</h5><a id="id775035" class="indexterm"></a><a id="id775053" class="indexterm"></a>
+ By default, the Web server asks proxy servers not to cache any documents which were negotiated on the basis of content (that is, they may change over time or because of the input from the requester). If <code class="command">CacheNegotiatedDocs</code> is set to <code class="option">on</code>, this function is disabled and proxy servers are allowed to cache such documents.
+ </div><div class="formalpara" id="s2-apache-customlog"><h5 class="formalpara">CustomLog</h5><a id="id922707" class="indexterm"></a><a id="id922725" class="indexterm"></a><a id="id922743" class="indexterm"></a>
+ <code class="command">CustomLog</code> identifies the log file and the log file format. By default, the access log is recorded to the <code class="filename">/var/log/httpd/access_log</code> file while errors are recorded in the <code class="filename">/var/log/httpd/error_log</code> file.
+ </div><div class="para">
+ The default <code class="command">CustomLog</code> format is the <code class="option">combined</code> log file format, as illustrated here:
+ </div><pre class="screen">
+<code class="command"><em class="replaceable"><code>remotehost rfc931 user date "request" status bytes referrer user-agent</code></em> </code>
+</pre><div class="formalpara" id="s2-apache-defaulticon"><h5 class="formalpara">DefaultIcon</h5><a id="id922817" class="indexterm"></a><a id="id922836" class="indexterm"></a>
+ <code class="command">DefaultIcon</code> specifies the icon displayed in server generated directory listings for files which have no other icon specified. The <code class="filename">unknown.gif</code> image file is the default.
+ </div><div class="formalpara" id="s2-apache-defaulttype"><h5 class="formalpara">DefaultType</h5><a id="id995673" class="indexterm"></a><a id="id995692" class="indexterm"></a>
+ <code class="command">DefaultType</code> sets a default content type for the Web server to use for documents whose MIME types cannot be determined. The default is <code class="command"> text/plain</code>.
+ </div><div class="formalpara" id="s2-apache-deny"><h5 class="formalpara">Deny</h5><a id="id995740" class="indexterm"></a><a id="id995758" class="indexterm"></a>
+ <code class="command">Deny</code> works similar to <code class="command">Allow</code>, except it specifies who is denied access. The <code class="command">DocumentRoot</code> is not configured to <code class="command">Deny</code> requests from anyone by default.
+ </div><div class="formalpara" id="s2-apache-directory"><h5 class="formalpara">Directory</h5><a id="id995813" class="indexterm"></a><a id="id664620" class="indexterm"></a>
+ <code class="command"><Directory /path/to/directory></code> and <code class="command"></Directory></code> tags create a container used to enclose a group of configuration directives which apply only to a specific directory and its subdirectories. Any directive which is applicable to a directory may be used within <code class="command">Directory</code> tags.
+ </div><div class="para">
+ By default, very restrictive parameters are applied to the root directory (<code class="filename">/</code>), using the <code class="command">Options</code> (refer to <a class="xref" href="s1-apache-config.html#s2-apache-options" title="Options">Options</a>) and <code class="command">AllowOverride</code> (refer to <a class="xref" href="s1-apache-config.html#s2-apache-allowoverride" title="AllowOverride">AllowOverride</a>) directives. Under this configuration, any directory on the system which needs more permissive settings has to be explicitly given those settings.
+ </div><div class="para">
+ In the default configuration, another <code class="command">Directory</code> container is configured for the <code class="command">DocumentRoot</code> which assigns less rigid parameters to the directory tree so that the Apache HTTP Server can access the files residing there.
+ </div><a id="id664698" class="indexterm"></a><div class="para">
+ The <code class="command">Directory</code> container can be also be used to configure additional <code class="filename">cgi-bin</code> directories for server-side applications outside of the directory specified in the <code class="command">ScriptAlias</code> directive (refer to <a class="xref" href="s1-apache-config.html#s2-apache-scriptalias" title="ScriptAlias">ScriptAlias</a> for more information).
+ </div><div class="para">
+ To accomplish this, the <code class="command">Directory</code> container must set the <code class="command">ExecCGI</code> option for that directory.
+ </div><div class="para">
+ For example, if CGI scripts are located in <code class="command">/home/my_cgi_directory</code>, add the following <code class="command">Directory</code> container to the <code class="filename">httpd.conf</code> file:
+ </div><pre class="screen">
+<code class="command"><Directory /home/my_cgi_directory> Options +ExecCGI </Directory></code>
+</pre><div class="para">
+ Next, the <code class="command">AddHandler</code> directive must be uncommented to identify files with the <code class="filename">.cgi</code> extension as CGI scripts. Refer to <a class="xref" href="s1-apache-config.html#s2-apache-addhandler" title="AddHandler">AddHandler</a> for instructions on setting <code class="command">AddHandler</code>.
+ </div><div class="para">
+ For this to work, permissions for CGI scripts, and the entire path to the scripts, must be set to 0755.
+ </div><div class="formalpara" id="s2-apache-directoryindex"><h5 class="formalpara">DirectoryIndex</h5><a id="id922516" class="indexterm"></a><a id="id922534" class="indexterm"></a>
+ The <code class="command">DirectoryIndex</code> is the default page served by the server when a user requests an index of a directory by specifying a forward slash (/) at the end of the directory name.
+ </div><div class="para">
+ When a user requests the page http://<em class="replaceable"><code>example</code></em>/<em class="replaceable"><code>this_directory</code></em>/, they get either the <code class="command">DirectoryIndex</code> page, if it exists, or a server-generated directory list. The default for <code class="command">DirectoryIndex</code> is <code class="filename">index.html</code> and the <code class="filename">index.html.var</code> type map. The server tries to find either of these files and returns the first one it finds. If it does not find one of these files and <code class="command">Options Indexes</code> is set for that directory, the server generates and returns a listing, in HTML format, of the subdirectories and files within the directory, unless the directory listing feature is turned off.
+ </div><div class="formalpara" id="s2-apache-documentroot"><h5 class="formalpara">DocumentRoot</h5><a id="id922614" class="indexterm"></a><a id="id922632" class="indexterm"></a>
+ <code class="command">DocumentRoot</code> is the directory which contains most of the HTML files which are served in response to requests. The default <code class="command">DocumentRoot</code>, for both the non-secure and secure Web servers, is the <code class="filename">/var/www/html</code> directory. For example, the server might receive a request for the following document:
+ </div><pre class="screen">
+<code class="command">http://example.com/foo.html</code>
+</pre><div class="para">
+ The server looks for the following file in the default directory:
+ </div><pre class="screen">
+<code class="filename">/var/www/html/foo.html</code>
+</pre><div class="para">
+ To change the <code class="command">DocumentRoot</code> so that it is not shared by the secure and the non-secure Web servers, refer to <a class="xref" href="s1-apache-virtualhosts.html" title="11.7. Virtual Hosts">Section 11.7, “Virtual Hosts”</a>.
+ </div><div class="formalpara" id="s2-apache-errordocument"><h5 class="formalpara">ErrorDocument</h5><a id="id686559" class="indexterm"></a><a id="id686577" class="indexterm"></a>
+ The <code class="command">ErrorDocument</code> directive associates an HTTP response code with a message or a URL to be sent back to the client. By default, the Web server outputs a simple and usually cryptic error message when an error occurs. The <code class="command">ErrorDocument</code> directive forces the Web server to instead output a customized message or page.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ To be valid, the message <span class="emphasis"><em>must</em></span> be enclosed in a pair of double quotes <code class="command">"</code>.
+ </div></div><div class="formalpara" id="s2-apache-errorlog"><h5 class="formalpara">ErrorLog</h5><a id="id686646" class="indexterm"></a><a id="id686664" class="indexterm"></a>
+ <code class="command">ErrorLog</code> specifies the file where server errors are logged. By default, this directive is set to <code class="filename">/var/log/httpd/error_log</code>.
+ </div><a id="id644449" class="indexterm"></a><div class="formalpara" id="s2-apache-extendedstatus"><h5 class="formalpara">ExtendedStatus</h5><a id="id644478" class="indexterm"></a><a id="id644497" class="indexterm"></a>
+ The <code class="command">ExtendedStatus</code> directive controls whether Apache generates basic (<code class="command">off</code>) or detailed server status information (<code class="command">on</code>), when the <code class="command">server-status</code> handler is called. The <code class="command">server-status</code> handler is called using <code class="command">Location</code> tags. More information on calling <code class="command">server-status</code> is included in <a class="xref" href="s1-apache-config.html#s2-apache-location" title="Location">Location</a>.
+ </div><div class="formalpara" id="s2-apache-group"><h5 class="formalpara">Group</h5><a id="id644568" class="indexterm"></a><a id="id644586" class="indexterm"></a>
+ Specifies the group name of the Apache HTTP Server processes.
+ </div><div class="para">
+ This directive has been deprecated for the configuration of virtual hosts.
+ </div><div class="para">
+ By default, <code class="command">Group</code> is set to <code class="command">apache</code>.
+ </div><div class="formalpara" id="s2-apache-headername"><h5 class="formalpara">HeaderName</h5><a id="id642087" class="indexterm"></a><a id="id642106" class="indexterm"></a>
+ <code class="command">HeaderName</code> names the file which, if it exists in the directory, is prepended to the start of server generated directory listings. Like <code class="command">ReadmeName</code>, the server tries to include it as an HTML document if possible or in plain text if not.
+ </div><div class="formalpara" id="s2-apache-hostnamelookups"><h5 class="formalpara">HostnameLookups</h5><a id="id642154" class="indexterm"></a><a id="id642172" class="indexterm"></a><a id="id642190" class="indexterm"></a>
+ <code class="command">HostnameLookups</code> can be set to <code class="option">on</code>, <code class="option">off</code>, or <code class="option">double</code>. If <code class="command">HostnameLookups</code> is set to <code class="option">on</code>, the server automatically resolves the IP address for each connection. Resolving the IP address means that the server makes one or more connections to a DNS server, adding processing overhead. If <code class="command">HostnameLookups</code> is set to <code class="option">double</code>, the server performs a double-reverse DNS look up adding even more processing overhead.
+ </div><div class="para">
+ To conserve resources on the server, <code class="command">HostnameLookups</code> is set to <code class="option">off</code> by default.
+ </div><div class="para">
+ If hostnames are required in server log files, consider running one of the many log analyzer tools that perform the DNS lookups more efficiently and in bulk when rotating the Web server log files.
+ </div><div class="formalpara" id="s2-apache-ifdefine"><h5 class="formalpara">IfDefine</h5><a id="id595060" class="indexterm"></a><a id="id595078" class="indexterm"></a>
+ The <code class="command">IfDefine</code> tags surround configuration directives that are applied if the "test" stated in the <code class="command">IfDefine</code> tag is true. The directives are ignored if the test is false.
+ </div><div class="para">
+ The test in the <code class="command">IfDefine</code> tags is a parameter name (for example, <code class="command">HAVE_PERL</code>). If the parameter is defined, meaning that it is provided as an argument to the server's start-up command, then the test is true. In this case, when the Web server is started, the test is true and the directives contained in the <code class="command">IfDefine</code> tags are applied.
+ </div><div class="formalpara" id="s2-apache-ifmodule"><h5 class="formalpara">IfModule</h5><a id="id595144" class="indexterm"></a><a id="id595162" class="indexterm"></a>
+ <code class="command"><IfModule></code> and <code class="command"></IfModule></code> tags create a conditional container which are only activated if the specified module is loaded. Directives within the <code class="command">IfModule</code> container are processed under one of two conditions. The directives are processed if the module contained within the starting <code class="command"><IfModule></code> tag is loaded. Or, if an exclamation point <span class="keycap"><strong>!</strong></span> appears before the module name, the directives are processed only if the module specified in the <code class="command"><IfModule></code> tag is <span class="emphasis"><em>not</em></span> loaded.
+ </div><div class="para">
+ For more information about Apache HTTP Server modules, refer to <a class="xref" href="s1-apache-addmods.html" title="11.6. Adding Modules">Section 11.6, “Adding Modules”</a>.
+ </div><div class="formalpara" id="s2-apache-include"><h5 class="formalpara">Include</h5><a id="id903478" class="indexterm"></a><a id="id903496" class="indexterm"></a>
+ <code class="command">Include</code> allows other configuration files to be included at runtime.
+ </div><div class="para">
+ The path to these configuration files can be absolute or relative to the <code class="command">ServerRoot</code>.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ For the server to use individually packaged modules, such as <code class="filename">mod_ssl</code>, <code class="filename">mod_perl</code>, and <code class="filename">php</code>, the following directive must be included in <code class="command">Section 1: Global Environment</code> of <code class="filename">httpd.conf</code>:
+ </div><pre class="screen">
+<code class="command">Include conf.d/*.conf</code>
+</pre></div><div class="formalpara" id="s2-apache-indexignore"><h5 class="formalpara">IndexIgnore</h5><a id="id903588" class="indexterm"></a><a id="id740413" class="indexterm"></a>
+ <code class="command">IndexIgnore</code> lists file extensions, partial file names, wildcard expressions, or full file names. The Web server does not include any files which match any of those parameters in server generated directory listings.
+ </div><div class="formalpara" id="s2-apache-indexoptions"><h5 class="formalpara">IndexOptions</h5><a id="id740458" class="indexterm"></a><a id="id740476" class="indexterm"></a>
+ <code class="command">IndexOptions</code> controls the appearance of server generated directing listings, by adding icons, file descriptions, and so on. If <code class="command">Options Indexes</code> is set (refer to <a class="xref" href="s1-apache-config.html#s2-apache-options" title="Options">Options</a>), the Web server generates a directory listing when the Web server receives an HTTP request for a directory without an index.
+ </div><div class="para">
+ First, the Web server looks in the requested directory for a file matching the names listed in the <code class="command">DirectoryIndex</code> directive (usually, <code class="filename">index.html</code>). If an <code class="filename">index.html</code> file is not found, Apache HTTP Server creates an HTML directory listing of the requested directory. The appearance of this directory listing is controlled, in part, by the <code class="command">IndexOptions</code> directive.
+ </div><div class="para">
+ The default configuration turns on <code class="command">FancyIndexing</code>. This means that a user can re-sort a directory listing by clicking on column headers. Another click on the same header switches from ascending to descending order. <code class="command">FancyIndexing</code> also shows different icons for different files, based upon file extensions.
+ </div><div class="para">
+ The <code class="command">AddDescription</code> option, when used in conjunction with <code class="command">FancyIndexing</code>, presents a short description for the file in server generated directory listings.
+ </div><div class="para">
+ <code class="command">IndexOptions</code> has a number of other parameters which can be set to control the appearance of server generated directories. The <code class="command">IconHeight</code> and <code class="command">IconWidth</code> parameters require the server to include HTML <code class="command">HEIGHT</code> and <code class="command">WIDTH</code> tags for the icons in server generated webpages. The <code class="command">IconsAreLinks</code> parameter combines the graphical icon with the HTML link anchor, which contains the URL link target.
+ </div><div class="formalpara" id="s2-apache-keepalive"><h5 class="formalpara">KeepAlive</h5><a id="id769221" class="indexterm"></a><a id="id769239" class="indexterm"></a><a id="id769261" class="indexterm"></a><a id="id769288" class="indexterm"></a>
+ <code class="command">KeepAlive</code> sets whether the server allows more than one request per connection and can be used to prevent any one client from consuming too much of the server's resources.
+ </div><div class="para">
+ By default <code class="command">Keepalive</code> is set to <code class="command">off</code>. If <code class="command">Keepalive</code> is set to <code class="command">on</code> and the server becomes very busy, the server can quickly spawn the maximum number of child processes. In this situation, the server slows down significantly. If <code class="command">Keepalive</code> is enabled, it is a good idea to set the the <code class="command">KeepAliveTimeout</code> low (refer to <a class="xref" href="s1-apache-config.html#s2-apache-keepalivetimeout" title="KeepAliveTimeout">KeepAliveTimeout</a> for more information about the <code class="command">KeepAliveTimeout</code> directive) and monitor the <code class="filename">/var/log/httpd/error_log</code> log file on the server. This log reports when the server is running out of child processes.
+ </div><div class="formalpara" id="s2-apache-keepalivetimeout"><h5 class="formalpara">KeepAliveTimeout</h5><a id="id836478" class="indexterm"></a><a id="id836496" class="indexterm"></a>
+ <code class="command">KeepAliveTimeout</code> sets the number of seconds the server waits after a request has been served before it closes the connection. Once the server receives a request, the <code class="command">Timeout</code> directive applies instead. The <code class="command">KeepAliveTimeout</code> directive is set to 15 seconds by default.
+ </div><div class="formalpara" id="s2-apache-languagepriority"><h5 class="formalpara">LanguagePriority</h5><a id="id836547" class="indexterm"></a><a id="id836565" class="indexterm"></a>
+ <code class="command">LanguagePriority</code> sets precedence for different languages in case the client Web browser has no language preference set.
+ </div><div class="formalpara" id="s2-apache-listen"><h5 class="formalpara">Listen</h5><a id="id836609" class="indexterm"></a><a id="id836628" class="indexterm"></a>
+ The <code class="command">Listen</code> command identifies the ports on which the Web server accepts incoming requests. By default, the Apache HTTP Server is set to listen to port 80 for non-secure Web communications and (in the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file which defines any secure servers) to port 443 for secure Web communications.
+ </div><div class="para">
+ If the Apache HTTP Server is configured to listen to a port under 1024, only the root user can start it. For port 1024 and above, <code class="command">httpd</code> can be started as a regular user.
+ </div><div class="para">
+ The <code class="command">Listen</code> directive can also be used to specify particular IP addresses over which the server accepts connections.
+ </div><div class="formalpara" id="s2-apache-loadmodule"><h5 class="formalpara">LoadModule</h5><a id="id871344" class="indexterm"></a><a id="id871362" class="indexterm"></a>
+ <code class="command">LoadModule</code> is used to load Dynamic Shared Object (DSO) modules. More information on the Apache HTTP Server's DSO support, including instructions for using the <code class="command">LoadModule</code> directive, can be found in <a class="xref" href="s1-apache-addmods.html" title="11.6. Adding Modules">Section 11.6, “Adding Modules”</a>. Note, the load order of the modules is <span class="emphasis"><em>no longer important</em></span> with Apache HTTP Server 2.0. Refer to <a class="xref" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-dso" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support">Section 11.2.2.1.3, “Dynamic Shared Object (DSO) Support”</a> for more information about Apache HTTP Server 2.0 DSO support.
+ </div><div class="formalpara" id="s2-apache-location"><h5 class="formalpara">Location</h5><a id="id871424" class="indexterm"></a><a id="id871443" class="indexterm"></a><a id="id871461" class="indexterm"></a>
+ The <code class="command"><Location></code> and <code class="command"></Location></code> tags create a container in which access control based on URL can be specified.
+ </div><div class="para">
+ For instance, to allow people connecting from within the server's domain to see status reports, use the following directives:
+ </div><pre class="screen">
+<code class="command"><Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from <em class="replaceable"><code><.example.com></code></em> </Location></code>
+</pre><div class="para">
+ Replace <em class="replaceable"><code><.example.com></code></em> with the second-level domain name for the Web server.
+ </div><div class="para">
+ To provide server configuration reports (including installed modules and configuration directives) to requests from inside the domain, use the following directives:
+ </div><pre class="screen">
+<code class="command"><Location /server-info> SetHandler server-info Order deny,allow Deny from all Allow from <em class="replaceable"><code><.example.com></code></em> </Location></code>
+</pre><div class="para">
+ Again, replace <em class="replaceable"><code><.example.com></code></em> with the second-level domain name for the Web server.
+ </div><div class="formalpara" id="s2-apache-logformat"><h5 class="formalpara">LogFormat</h5><a id="id881979" class="indexterm"></a><a id="id881997" class="indexterm"></a><a id="id882020" class="indexterm"></a><a id="id882038" class="indexterm"></a>
+ The <code class="command">LogFormat</code> directive configures the format of the various Web server log files. The actual <code class="command">LogFormat</code> used depends on the settings given in the <code class="command">CustomLog</code> directive (refer to <a class="xref" href="s1-apache-config.html#s2-apache-customlog" title="CustomLog">CustomLog</a>).
+ </div><div class="para">
+ The following are the format options if the <code class="command">CustomLog</code> directive is set to <code class="command">combined</code>:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">%h</code> (remote host's IP address or hostname) </span></dt><dd><div class="para">
+ Lists the remote IP address of the requesting client. If <code class="command">HostnameLookups</code> is set to <code class="option">on</code>, the client hostname is recorded unless it is not available from DNS.
+ </div></dd><dt><span class="term"> <code class="command">%l</code> (rfc931) </span></dt><dd><div class="para">
+ Not used. A hyphen <span class="keycap"><strong>-</strong></span> appears in the log file for this field.
+ </div></dd><dt><span class="term"> <code class="command">%u</code> (authenticated user) </span></dt><dd><div class="para">
+ Lists the username of the user recorded if authentication was required. Usually, this is not used, so a hyphen <span class="keycap"><strong>-</strong></span> appears in the log file for this field.
+ </div></dd><dt><span class="term"> <code class="command">%t</code> (date) </span></dt><dd><div class="para">
+ Lists the date and time of the request.
+ </div></dd><dt><span class="term"> <code class="command">%r</code> (request string) </span></dt><dd><div class="para">
+ Lists the request string exactly as it came from the browser or client.
+ </div></dd><dt><span class="term"> <code class="command">%s</code> (status) </span></dt><dd><div class="para">
+ Lists the HTTP status code which was returned to the client host.
+ </div></dd><dt><span class="term"> <code class="command">%b</code> (bytes) </span></dt><dd><div class="para">
+ Lists the size of the document.
+ </div></dd><dt><span class="term"> <code class="command">%\"%{Referer}i\"</code> (referrer) </span></dt><dd><div class="para">
+ Lists the URL of the webpage which referred the client host to Web server.
+ </div></dd><dt><span class="term"> <code class="command">%\"%{User-Agent}i\"</code> (user-agent) </span></dt><dd><div class="para">
+ Lists the type of Web browser making the request.
+ </div></dd></dl></div><div class="formalpara" id="s2-apache-loglevel"><h5 class="formalpara">LogLevel</h5><a id="id602781" class="indexterm"></a><a id="id602799" class="indexterm"></a>
+ <code class="command">LogLevel</code> sets how verbose the error messages in the error logs are. <code class="command">LogLevel</code> can be set (from least verbose to most verbose) to <code class="command">emerg</code>, <code class="command">alert</code>, <code class="command">crit</code>, <code class="command">error</code>, <code class="command">warn</code>, <code class="command">notice</code>, <code class="command">info</code>, or <code class="command">debug</code>. The default <code class="command">LogLevel</code> is <code class="command">warn</code>.
+ </div><div class="formalpara" id="s2-apache-maxkeepaliverequests"><h5 class="formalpara">MaxKeepAliveRequests</h5><a id="id602886" class="indexterm"></a><a id="id716614" class="indexterm"></a>
+ This directive sets the maximum number of requests allowed per persistent connection. The Apache Project recommends a high setting, which improves the server's performance. <code class="command">MaxKeepAliveRequests</code> is set to <code class="command">100</code> by default, which should be appropriate for most situations.
+ </div><div class="formalpara" id="s2-apache-namevirtualhost"><h5 class="formalpara">NameVirtualHost</h5><a id="id716662" class="indexterm"></a><a id="id716680" class="indexterm"></a>
+ The <code class="command">NameVirtualHost</code> directive associates an IP address and port number, if necessary, for any name-based virtual hosts. Name-based virtual hosting allows one Apache HTTP Server to serve different domains without using multiple IP addresses.
+ </div><div class="note"><h2>Note</h2><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 class="para">
+ To enable name-based virtual hosting, uncomment the <code class="command">NameVirtualHost</code> configuration directive and add the correct IP address. Then add additional <code class="command">VirtualHost</code> containers for each virtual host as is necessary for your configuration.
+ </div><div class="formalpara" id="s2-apache-options"><h5 class="formalpara">Options</h5><a id="id716755" class="indexterm"></a><a id="id716773" class="indexterm"></a><a id="id716792" class="indexterm"></a><a id="id822702" class="indexterm"></a>
+ The <code class="command">Options</code> directive controls which server features are available in a particular directory. For example, under the restrictive parameters specified for the root directory, <code class="command">Options</code> is only set to the <code class="command">FollowSymLinks</code> directive. No features are enabled, except that the server is allowed to follow symbolic links in the root directory.
+ </div><div class="para">
+ By default, in the <code class="command">DocumentRoot</code> directory, <code class="command">Options</code> is set to include <code class="command">Indexes</code> and <code class="command">FollowSymLinks</code>. <code class="command">Indexes</code> permits the server to generate a directory listing for a directory if no <code class="command">DirectoryIndex</code> (for example, <code class="filename">index.html</code>) is specified. <code class="command">FollowSymLinks</code> allows the server to follow symbolic links in that directory.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ <code class="command">Options</code> statements from the main server configuration section need to be replicated to each <code class="command">VirtualHost</code> container individually. Refer to <a class="xref" href="s1-apache-config.html#s2-apache-virtualhost" title="VirtualHost">VirtualHost</a> for more information.
+ </div></div><div class="formalpara" id="s2-apache-order"><h5 class="formalpara">Order</h5><a id="id822808" class="indexterm"></a><a id="id822827" class="indexterm"></a>
+ The <code class="command">Order</code> directive controls the order in which <code class="command">allow</code> and <code class="command">deny</code> directives are evaluated. The server is configured to evaluate the <code class="command">Allow</code> directives before the <code class="command">Deny</code> directives for the <code class="command">DocumentRoot</code> directory.
+ </div><div class="formalpara" id="s2-apache-pidfile"><h5 class="formalpara">PidFile</h5><a id="id770443" class="indexterm"></a><a id="id770461" class="indexterm"></a>
+ <code class="command">PidFile</code> names the file where the server records its process ID (PID). By default the PID is listed in <code class="filename">/var/run/httpd.pid</code>.
+ </div><div class="formalpara" id="s2-apache-proxy"><h5 class="formalpara">Proxy</h5><a id="id770509" class="indexterm"></a><a id="id770527" class="indexterm"></a>
+ <code class="command"><Proxy *></code> and <code class="command"></Proxy></code> tags create a container which encloses a group of configuration directives meant to apply only to the proxy server. Many directives which are allowed within a <code class="command"><Directory></code> container may also be used within <code class="command"><Proxy></code> container.
+ </div><div class="formalpara" id="s2-apache-proxyrequests"><h5 class="formalpara">ProxyRequests</h5><a id="id770583" class="indexterm"></a><a id="id802744" class="indexterm"></a><a id="id802762" class="indexterm"></a>
+ To configure the Apache HTTP Server to function as a proxy server, remove the hash mark (<code class="command">#</code>) from the beginning of the <code class="command"><IfModule mod_proxy.c></code> line, the ProxyRequests, and each line in the <code class="command"><Proxy></code> stanza. Set the <code class="command">ProxyRequests</code> directive to <code class="command">On</code>, and set which domains are allowed access to the server in the <code class="command">Allow from</code> directive of the <code class="command"><Proxy></code> stanza.
+ </div><div class="formalpara" id="s2-apache-readmename"><h5 class="formalpara">ReadmeName</h5><a id="id802822" class="indexterm"></a><a id="id802840" class="indexterm"></a>
+ <code class="command">ReadmeName</code> names the file which, if it exists in the directory, is appended to the end of server generated directory listings. The Web server first tries to include the file as an HTML document and then tries to include it as plain text. By default, <code class="command">ReadmeName</code> is set to <code class="filename">README.html</code>.
+ </div><div class="formalpara" id="s2-apache-redirect"><h5 class="formalpara">Redirect</h5><a id="id802894" class="indexterm"></a><a id="id802912" class="indexterm"></a>
+ When a webpage is moved, <code class="command">Redirect</code> can be used to map the file location to a new URL. The format is as follows:
+ </div><pre class="screen">
+<code class="command">Redirect /<em class="replaceable"><code><old-path></code></em>/<em class="replaceable"><code><file-name></code></em> http://<em class="replaceable"><code><current-domain></code></em>/<em class="replaceable"><code><current-path></code></em>/<em class="replaceable"><code><file-name></code></em> </code>
+</pre><div class="para">
+ In this example, replace <em class="replaceable"><code><old-path></code></em> with the old path information for <em class="replaceable"><code><file-name></code></em> and <em class="replaceable"><code><current-domain></code></em> and <em class="replaceable"><code><current-path></code></em> with the current domain and path information for <em class="replaceable"><code><file-name></code></em>.
+ </div><div class="para">
+ In this example, any requests for <em class="replaceable"><code><file-name></code></em> at the old location is automatically redirected to the new location.
+ </div><div class="para">
+ For more advanced redirection techniques, use the <code class="command">mod_rewrite</code> module included with the Apache HTTP Server. For more information about configuring the <code class="command">mod_rewrite</code> module, refer to the Apache Software Foundation documentation online at <a href="http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html"> http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html</a>.
+ </div><div class="formalpara" id="s2-apache-scriptalias"><h5 class="formalpara">ScriptAlias</h5><a id="id882386" class="indexterm"></a><a id="id882404" class="indexterm"></a>
+ The <code class="command">ScriptAlias</code> directive defines where CGI scripts are located. Generally, it is not good practice to leave CGI scripts within the <code class="command">DocumentRoot</code>, where they can potentially be viewed as text documents. For this reason, a special directory outside of the <code class="command">DocumentRoot</code> directory containing server-side executables and scripts is designated by the <code class="command">ScriptAlias</code> directive. This directory is known as a <code class="filename">cgi-bin</code> and is set to <code class="filename">/var/www/cgi-bin/</code> by default.
+ </div><div class="para">
+ It is possible to establish directories for storing executables outside of the <code class="filename">cgi-bin/</code> directory. For instructions on doing so, refer to <a class="xref" href="s1-apache-config.html#s2-apache-addhandler" title="AddHandler">AddHandler</a> and <a class="xref" href="s1-apache-config.html#s2-apache-directory" title="Directory">Directory</a>.
+ </div><div class="formalpara" id="s2-apache-serveradmin"><h5 class="formalpara">ServerAdmin</h5><a id="id592644" class="indexterm"></a><a id="id592662" class="indexterm"></a><a id="id592680" class="indexterm"></a>
+ Sets the <code class="command">ServerAdmin</code> directive to the email address of the Web server administrator. This email address shows up in error messages on server-generated Web pages, so users can report a problem by sending email to the server administrator.
+ </div><div class="para">
+ By default, <code class="command">ServerAdmin</code> is set to <code class="command">root at localhost</code>.
+ </div><div class="para">
+ A common way to set up <code class="command">ServerAdmin</code> is to set it to <code class="command">webmaster at example.com</code>. Once set, alias <code class="command">webmaster</code> to the person responsible for the Web server in <code class="filename">/etc/aliases</code> and run <code class="command">/usr/bin/newaliases</code>.
+ </div><div class="formalpara" id="s2-apache-servername"><h5 class="formalpara">ServerName</h5><a id="id592757" class="indexterm"></a><a id="id592775" class="indexterm"></a>
+ <code class="command">ServerName</code> specifies a hostname and port number (matching the <code class="command">Listen</code> directive) for the server. The <code class="command">ServerName</code> does not need to match the machine's actual hostname. For example, the Web server may be <code class="computeroutput">www.example.com</code>, but the server's hostname is actually <code class="computeroutput">foo.example.com</code>. The value specified in <code class="command">ServerName</code> must be a valid Domain Name Service (DNS) name that can be resolved by the system — do not make something up.
+ </div><div class="para">
+ The following is a sample <code class="command">ServerName</code> directive:
+ </div><pre class="screen">
+<code class="command">ServerName www.example.com:80</code>
+</pre><div class="para">
+ When specifying a <code class="command">ServerName</code>, be sure the IP address and server name pair are included in the <code class="filename">/etc/hosts</code> file.
+ </div><div class="formalpara" id="s2-apache-serverroot"><h5 class="formalpara">ServerRoot</h5><a id="id709050" class="indexterm"></a><a id="id709069" class="indexterm"></a>
+ The <code class="command">ServerRoot</code> directive specifies the top-level directory containing website content. By default, <code class="command">ServerRoot</code> is set to <code class="filename">"/etc/httpd"</code> for both secure and non-secure servers.
+ </div><div class="formalpara" id="s2-apache-serversignature"><h5 class="formalpara">ServerSignature</h5><a id="id709119" class="indexterm"></a><a id="id709137" class="indexterm"></a>
+ The <code class="command">ServerSignature</code> directive adds a line containing the Apache HTTP Server server version and the <code class="command">ServerName</code> to any server-generated documents, such as error messages sent back to clients. <code class="command">ServerSignature</code> is set to <code class="command">on</code> by default.
+ </div><div class="para">
+ <code class="command">ServerSignature</code> can be set to <code class="command">EMail</code> which adds a <code class="command">mailto:ServerAdmin</code> HTML tag to the signature line of auto-generated responses. <code class="command">ServerSignature</code> can also be set to <code class="command">Off</code> to stop Apache from sending out its version number and module information. Please also check the <code class="command">ServerTokens</code> settings.
+ </div><div class="formalpara" id="s2-apache-servertoken"><h5 class="formalpara">ServerTokens</h5><a id="id960132" class="indexterm"></a><a id="id960150" class="indexterm"></a>
+ The <code class="command">ServerTokens</code> directive determines if the Server response header field sent back to clients should include details of the Operating System type and information about compiled-in modules. By default, <code class="command">ServerTokens</code> is set to <code class="command">Full</code> which sends information about the Operating System type and compiled-in modules. Setting the <code class="command">ServerTokens</code> to <code class="command">Prod</code> sends the product name only and is recommended as many hackers check information in the Server header when scanning for vulnerabilities. You can also set the <code class="command">ServerTokens</code> to <code class="command">Min</code> (minimal) or to <code class="command">OS</code> (operating system).
+ </div><div class="formalpara" id="s2-apache-suexecusergroup"><h5 class="formalpara">SuexecUserGroup</h5><a id="id960224" class="indexterm"></a><a id="id867032" class="indexterm"></a><a id="id867050" class="indexterm"></a>
+ The <code class="command">SuexecUserGroup</code> directive, which originates from the <code class="command">mod_suexec</code> module, allows the specification of user and group execution privileges for CGI programs. Non-CGI requests are still processed with the user and group specified in the <code class="command">User</code> and <code class="command">Group</code> directives.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ From version 2.0, the <code class="command">SuexecUserGroup</code> directive replaced the Apache HTTP Server 1.3 configuration of using the <code class="command">User</code> and <code class="command">Group</code> directives inside the configuration of <code class="command">VirtualHosts</code> sections.
+ </div></div><div class="formalpara" id="s2-apache-timeout"><h5 class="formalpara">Timeout</h5><a id="id867134" class="indexterm"></a><a id="id867153" class="indexterm"></a>
+ <code class="command">Timeout</code> defines, in seconds, the amount of time that the server waits for receipts and transmissions during communications. <code class="command">Timeout</code> is set to <code class="command">300</code> seconds by default, which is appropriate for most situations.
+ </div><div class="formalpara" id="s2-apache-typesconfig"><h5 class="formalpara">TypesConfig</h5><a id="id867205" class="indexterm"></a><a id="id957124" class="indexterm"></a>
+ <code class="command">TypesConfig</code> names the file which sets the default list of MIME type mappings (file name extensions to content types). The default <code class="command"> TypesConfig</code> file is <code class="filename">/etc/mime.types</code>. Instead of editing <code class="filename">/etc/mime.types</code>, the recommended way to add MIME type mappings is to use the <code class="command"> AddType</code> directive.
+ </div><div class="para">
+ For more information about <code class="command">AddType</code>, refer to <a class="xref" href="s1-apache-config.html#s2-apache-addtype" title="AddType">AddType</a>.
+ </div><div class="formalpara" id="s2-apache-usecanonicalname"><h5 class="formalpara">UseCanonicalName</h5><a id="id957196" class="indexterm"></a><a id="id957214" class="indexterm"></a>
+ When set to <code class="option">on</code>, this directive configures the Apache HTTP Server to reference itself using the value specified in the <code class="command">ServerName</code> and <code class="command">Port</code> directives. When <code class="command">UseCanonicalName</code> is set to <code class="option">off</code>, the server instead uses the value used by the requesting client when referring to itself.
+ </div><div class="para">
+ <code class="command">UseCanonicalName</code> is set to <code class="option">off</code> by default.
+ </div><div class="formalpara" id="s2-apache-user"><h5 class="formalpara">User</h5><a id="id957287" class="indexterm"></a><a id="id954019" class="indexterm"></a>
+ The <code class="command">User</code> directive sets the username of the server process and determines what files the server is allowed to access. Any files inaccessible to this user are also inaccessible to clients connecting to the Apache HTTP Server.
+ </div><div class="para">
+ By default <code class="command">User</code> is set to <code class="command">apache</code>.
+ </div><div class="para">
+ This directive has been deprecated for the configuration of virtual hosts.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ For security reasons, the Apache HTTP Server does not run as the root user.
+ </div></div><div class="formalpara" id="s2-apache-userdir"><h5 class="formalpara">UserDir</h5><a id="id954093" class="indexterm"></a><a id="id954111" class="indexterm"></a><a id="id954130" class="indexterm"></a><a id="id954144" class="indexterm"></a>
+ <code class="command">UserDir</code> is the subdirectory within each user's home directory where they should place personal HTML files which are served by the Web server. This directive is set to <code class="option"> disable</code> by default.
+ </div><div class="para">
+ The name for the subdirectory is set to <code class="filename">public_html</code> in the default configuration. For example, the server might receive the following request:
+ </div><pre class="screen">
+<code class="command">http://<em class="replaceable"><code>example.com</code></em>/~<em class="replaceable"><code>username</code></em>/foo.html</code>
+</pre><div class="para">
+ The server would look for the file:
+ </div><pre class="screen">
+<code class="filename">/home/username/public_html/foo.html</code>
+</pre><div class="para">
+ In the above example, <code class="filename">/home/username/</code> is the user's home directory (note that the default path to users' home directories may vary).
+ </div><div class="para">
+ Make sure that the permissions on the users' home directories are set correctly. Users' home directories must be set to 0711. The read (r) and execute (x) bits must be set on the users' <code class="filename">public_html</code> directories (0755 also works). Files that are served in a users' <code class="filename">public_html</code> directories must be set to at least 0644.
+ </div><div class="formalpara" id="s2-apache-virtualhost"><h5 class="formalpara">VirtualHost</h5><a id="id992390" class="indexterm"></a><a id="id992408" class="indexterm"></a>
+ <code class="command"><VirtualHost></code> and <code class="command"></VirtualHost></code> tags create a container outlining the characteristics of a virtual host. The <code class="command">VirtualHost</code> container accepts most configuration directives.
+ </div><div class="para">
+ A commented <code class="command">VirtualHost</code> container is provided in <code class="filename">httpd.conf</code>, which illustrates the minimum set of configuration directives necessary for each virtual host. Refer to <a class="xref" href="s1-apache-virtualhosts.html" title="11.7. Virtual Hosts">Section 11.7, “Virtual Hosts”</a> for more information about virtual hosts.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ The default SSL virtual host container now resides in the file <code class="filename">/etc/httpd/conf.d/ssl.conf</code>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-httpd-default-settings.html"><strong>Prev</strong>11.4.2. Default 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="s2-apache-sslcommands.html"><strong>Next</strong>11.5.2. Configuration Directives for SSL</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-startstop.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-startstop.html
new file mode 100644
index 0000000..34f7579
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-startstop.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>11.3. Starting and Stopping httpd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-httpd-v2-mig.html" title="11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0" /><link rel="next" href="s1-apache-config-ui.html" title="11.4. Apache HTTP Server Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc
.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-httpd-v2-mig.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-config-ui.html"><strong>Next</strong></a></li></ul><div class="section" title="11.3. Starting and Stopping httpd" id="s1-apache-startstop"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-startstop">11.3. Starting and Stopping <code class="command">httpd</code> </h2></div></div></div><a id="id928028" class="indexterm"></a><a id="id928043" class="indexterm"></a><a id="id928057" class="indexte
rm"></a><a id="id928072" class="indexterm"></a><div class="para">
+ After installing the <code class="filename">httpd</code> package, review the Apache HTTP Server's documentation available online at <a href="http://httpd.apache.org/docs/2.2/">http://httpd.apache.org/docs/2.2/</a>.
+ </div><div class="para">
+ The <code class="filename">httpd</code> RPM installs the <code class="filename">/etc/init.d/httpd</code> script, which can be accessed using the <code class="command">/sbin/service</code> command.
+ </div><div class="para">
+ Starting <code class="command">httpd</code> using the <code class="command">apachectl</code> control script sets the environmental variables in <code class="filename">/etc/sysconfig/httpd</code> and starts <code class="command">httpd</code>. You can also set the environment variables using the init script.
+ </div><div class="para">
+ To start the server using the <code class="command">apachectl</code> control script as root type:
+ </div><pre class="screen">
+<code class="command">apachectl start</code>
+</pre><div class="para">
+ You can also start <code class="command">httpd</code> using <code class="command">/sbin/service httpd start</code>. This starts <code class="command">httpd</code> but does not set the environment variables. If you are using the default <code class="command">Listen</code> directive in <code class="command">httpd.conf</code>, which is port 80, you will need to have root privileges to start the apache server.
+ </div><div class="para">
+ To stop the server, as root type:
+ </div><pre class="screen">
+<code class="command">apachectl stop</code>
+</pre><div class="para">
+ You can also stop <code class="command">httpd</code> using <code class="command">/sbin/service httpd stop</code>. The <code class="option">restart</code> option is a shorthand way of stopping and then starting the Apache HTTP Server.
+ </div><div class="para">
+ You can restart the server as root by typing:
+ </div><pre class="screen">
+<code class="command">apachectl restart</code>
+or:
+<code class="command">/sbin/service httpd restart</code>
+</pre><div class="para">
+ Apache will display a message on the console or in the <code class="filename">ErrorLog</code> if it encounters an error while starting.
+ </div><div class="para">
+ By default, the <code class="command">httpd</code> service does <span class="emphasis"><em>not</em></span> start automatically at boot time. If you would wish to have Apache startup at boot time, you will need to add a call to <code class="command">apachectl</code> in your startup files within the <code class="filename">rc.N</code> directory. A typical file used is <code class="filename">rc.local</code>. As this starts Apache as root, it is recommended to properly configure your security and authentication before adding this call.
+ </div><div class="para">
+ You can also configure the <code class="command">httpd</code> service to start up at boot time, using an initscript utility, such as <code class="command">/sbin/chkconfig</code>, <span class="application"><strong>/usr/sbin/ntsysv</strong></span>, or the <span class="application"><strong>Services Configuration Tool</strong></span> program.
+ </div><div class="para">
+ You can also display the status of your httpd server by typing:
+ </div><pre class="screen">
+<code class="command">apachectl status</code>
+</pre><div class="para">
+ The status module <code class="command">mod_status</code> however needs to be enabled in your <code class="filename">httpd.conf</code> configuration file for this to work. For more details on <code class="command">mod_status</code> can be found on <a href="http://httpd.apache.org/docs/2.2/mod/mod_status.html">http://httpd.apache.org/docs/2.2/mod/mod_status.html</a>.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ If running the Apache HTTP Server as a secure server, the secure server's password is required after the machine boots when using an encrypted private SSL key.
+ </div><div class="para">
+ You can find more information on <a href="http://httpd.apache.org/docs/2.2/ssl">http://httpd.apache.org/docs/2.2/ssl</a>
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s3-httpd-v2-mig.html"><strong>Prev</strong>11.2.2. Migrating Apache HTTP Server 1.3 Configur...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-config-ui.html"><strong>Next</strong>11.4. Apache HTTP Server Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-virtualhosts.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-virtualhosts.html
new file mode 100644
index 0000000..5a3807a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-apache-virtualhosts.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>11.7. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-addmods.html" title="11.6. Adding Modules" /><link rel="next" href="s1-httpd-secure-server.html" title="11.8. Apache HTTP Secure Server Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your
browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-addmods.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-httpd-secure-server.html"><strong>Next</strong></a></li></ul><div class="section" title="11.7. Virtual Hosts" id="s1-apache-virtualhosts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-virtualhosts">11.7. Virtual Hosts</h2></div></div></div><a id="id943365" class="indexterm"></a><a id="id943379" class="indexterm"></a><a id="id943393" class="indexterm"></a><a id="id943408" class="indexterm"></a><a id="id943422" class="indexterm"></a><a id="id1
385773" 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. A complete guide to using virtual hosts is available online at <a href="http://httpd.apache.org/docs/2.2/vhosts/">http://httpd.apache.org/docs/2.2/vhosts/</a>.
+ </div><div class="section" title="11.7.1. Setting Up Virtual Hosts" id="s2-apache-settingupvhosts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-settingupvhosts">11.7.1. Setting Up Virtual Hosts</h3></div></div></div><div class="para">
+ To create a name-based virtual host, it is best to use the virtual host container provided in <code class="filename">httpd.conf</code> as an example.
+ </div><div class="para">
+ The virtual host example read as follows:
+ </div><pre class="screen">#<VirtualHost *:80>
+# ServerAdmin webmaster at dummy-host.example.com
+# DocumentRoot /www/docs/dummy-host.example.com
+# ServerName dummy-host.example.com
+# ErrorLog logs/dummy-host.example.com-error_log
+# CustomLog logs/dummy-host.example.com-access_log common
+#</VirtualHost></pre><pre class="screen">#NameVirtualHost *:80
+#
+#<VirtualHost *:80>
+# ServerAdmin webmaster at dummy-host.example.com
+# DocumentRoot /www/docs/dummy-host.example.com
+# ServerName dummy-host.example.com
+# ErrorLog logs/dummy-host.example.com-error_log
+# CustomLog logs/dummy-host.example.com-access_log common #</VirtualHost></pre><div class="para">
+ To activate name-based virtual hosting, uncomment the <code class="command">NameVirtualHost</code> line by removing the hash mark (<code class="command">#</code>) and replace the asterisk (<code class="command">*</code>) with the IP address assigned to the machine.
+ </div><div class="para">
+ Next, configure a virtual host by uncommenting and customizing the <code class="command"><VirtualHost></code> container.
+ </div><div class="para">
+ On the <code class="command"><VirtualHost></code> line, change the asterisk (<code class="command">*</code>) to the server's IP address. Change the <code class="command">ServerName</code> to a <span class="emphasis"><em>valid</em></span> DNS name assigned to the machine, and configure the other directives as necessary.
+ </div><div class="para">
+ The <code class="command"><VirtualHost></code> container is highly customizable and accepts almost every directive available within the main server configuration.
+ </div><a id="id1385886" class="indexterm"></a><div class="note"><h2>Tip</h2><div class="para">
+ If configuring a virtual host to listen on a non-default port, that port must be added to the <code class="command">Listen</code> directive in the global settings section of <code class="filename">/etc/httpd/conf/httpd.conf</code> file.
+ </div></div><div class="para">
+ To activate a newly created virtual host, the Apache HTTP Server must be reloaded or restarted. Refer to <a class="xref" href="s1-apache-startstop.html" title="11.3. Starting and Stopping httpd">Section 11.3, “Starting and Stopping <code class="command">httpd</code> ”</a> for further instructions.
+ </div><div class="para">
+ Comprehensive information about creating and configuring both name-based and IP address-based virtual hosts is provided online at <a href="http://httpd.apache.org/docs/2.2/vhosts/">http://httpd.apache.org/docs/2.2/vhosts/</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-addmods.html"><strong>Prev</strong>11.6. Adding 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-httpd-secure-server.html"><strong>Next</strong>11.8. Apache HTTP Secure Server Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-autotasks-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-autotasks-additional-resources.html
new file mode 100644
index 0000000..2542e0e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-autotasks-additional-resources.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Automated_Tasks.html" title="Chapter 24. Automated Tasks" /><link rel="prev" href="s2-autotasks-at-batch-service.html" title="24.2.6. Starting and Stopping the Service" /><link rel="next" href="ch-Log_Files.html" title="Chapter 25. Log Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browse
r or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="24.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">24.3. Additional Resources</h2></div></div></div><a id="id821768" class="indexterm"></a><a id="id821782" class="indexterm"></a><a id="id821796" class="indexterm"></a><div class="para">
+ To learn more about configuring automated tasks, refer to the following resources.
+ </div><div class="section" title="24.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">24.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 — 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">/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>24.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 25. Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-autotasks-at-batch.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-autotasks-at-batch.html
new file mode 100644
index 0000000..8d794bc
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-autotasks-at-batch.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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Automated_Tasks.html" title="Chapter 24. Automated Tasks" /><link rel="prev" href="ch-Automated_Tasks.html" title="Chapter 24. Automated Tasks" /><link rel="next" href="s2-autotasks-batch-configuring.html" title="24.2.2. Configuring Batch Jobs" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or e
nable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="24.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">24.2. At and Batch</h2></div></div></div><a id="id1019948" class="indexterm"></a><a id="id1019962" 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="24.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">24.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 type <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 type <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 typing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> on a blank line to exit. If a script is en
tered, 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 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="24.2.3. Viewing Pending Jobs">Section 24.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="24.2.5. Controlling Access to At and Batch">Section 24.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 24. 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>24.2.2. Configuring Batch Jobs</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-additional-resources.html
new file mode 100644
index 0000000..e6132bc
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-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>7.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 7. The BIND DNS Server" /><link rel="prev" href="s1-bind-mistakes.html" title="7.6. Common Mistakes to Avoid" /><link rel="next" href="s2-bind-useful-websites.html" title="7.7.2. Useful Websites" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or ena
ble iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s2-bind-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" title="7.7. 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">7.7. Additional Resources</h2></div></div></div><a id="id953229" class="indexterm"></a><div class="para">
+ The following sources of information provide additional resources regarding BIND.
+ </div><div class="section" title="7.7.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">7.7.1. Installed Documentation</h3></div></div></div><a id="id639214" 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-number></code></em> with the version of <code class="filename">bind</code> installed on the system:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code><version-number></code></em>/</code> </span></dt><dd><div class="para">
+ This directory lists the most recent features.
+ </div></dd><dt><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code><version-number></code></em>/arm/</code> </span></dt><dd><div class="para">
+ This directory contains 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><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code><version-number></code></em>/draft/</code> </span></dt><dd><div class="para">
+ This directory contains assorted technical documents that review issues related to DNS service and propose some methods to address them.
+ </div></dd><dt><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code><version-number></code></em>/misc/</code> </span></dt><dd><div class="para">
+ This directory contains documents 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><span class="term"> <code class="filename">/usr/share/doc/bind-<em class="replaceable"><code><version-number></code></em>/rfc/</code> </span></dt><dd><div class="para">
+ This directory provides every RFC document related to BIND.
+ </div></dd></dl></div><div class="para">
+ There are also a number of man pages for the various applications and configuration files involved with BIND. The following lists some of the more important man pages.
+ </div><div class="variablelist"><dl><dt><span class="term">Administrative Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man rndc</code> — Explains the different options available when using the <code class="command">rndc</code> command to control a BIND nameserver.
+ </div></li></ul></div></dd><dt><span class="term">Server Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man named</code> — Explores assorted arguments that can be used to control the BIND nameserver daemon.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man lwresd</code> — Describes the purpose of and options available for the lightweight resolver daemon.
+ </div></li></ul></div></dd><dt><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man named.conf</code> — A comprehensive list of options available within the <code class="command">named</code> configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man rndc.conf</code> — A comprehensive list of options available within the <code class="command">rndc</code> configuration file.
+ </div></li></ul></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-mistakes.html"><strong>Prev</strong>7.6. 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>7.7.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-features.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-features.html
new file mode 100644
index 0000000..57a031e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-features.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.5. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 7. The BIND DNS Server" /><link rel="prev" href="s2-bind-rndc-options.html" title="7.4.3. Command Line Options" /><link rel="next" href="s2-bind-features-views.html" title="7.5.2. Multiple Views" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser o
r enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-features-views.html"><strong>Next</strong></a></li></ul><div class="section" title="7.5. 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">7.5. Advanced Features of BIND</h2></div></div></div><a id="id656460" class="indexterm"></a><div class="para">
+ Most BIND implementations only use <code class="command">named</code> to provide name resolution services or to act as an authority for a particular domain or sub-domain. However, BIND version 9 has a number of advanced features that allow for a more secure and efficient DNS service.
+ </div><div class="warning"><h2>Caution</h2><div class="para">
+ Some of these advanced features, such as DNSSEC, TSIG, and IXFR (which are defined in the following section), should only be used in network environments with nameservers that support the features. If the network environment includes non-BIND or older BIND nameservers, verify that each advanced feature is supported before attempting to use it.
+ </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="7.7.1. Installed Documentation">Section 7.7.1, “Installed Documentation”</a>.
+ </div><div class="section" title="7.5.1. DNS Protocol Enhancements" id="s2-bind-features-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-protocol">7.5.1. DNS Protocol Enhancements</h3></div></div></div><a id="id656520" class="indexterm"></a><div class="para">
+ BIND supports Incremental Zone Transfers (IXFR), where a slave nameserver only downloads the updated portions of a zone modified on a master nameserver. The standard transfer process requires that the entire zone be transferred to each slave nameserver for even the smallest change. For very popular domains with very lengthy zone files and many slave nameservers, IXFR makes the notification and update process much less resource-intensive.
+ </div><div class="para">
+ Note that IXFR is only available when using <em class="firstterm">dynamic updating</em> to make changes to master zone records. If manually editing zone files to make changes, Automatic Zone Transfer (AXFR) is used. More information on dynamic updating is available 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="7.7.1. Installed Documentation">Section 7.7.1, “Installed Documentation”</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-options.html"><strong>Prev</strong>7.4.3. 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-bind-features-views.html"><strong>Next</strong>7.5.2. Multiple Views</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-mistakes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-mistakes.html
new file mode 100644
index 0000000..a871aa9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-mistakes.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>7.6. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 7. The BIND DNS Server" /><link rel="prev" href="s2-bind-features-ipv6.html" title="7.5.4. IP version 6" /><link rel="next" href="s1-bind-additional-resources.html" title="7.7. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="7.6. 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">7.6. Common Mistakes to Avoid</h2></div></div></div><a id="id886626" class="indexterm"></a><div class="para">
+ It is very common for beginners to make mistakes when editing BIND configuration files. Be sure to avoid the following issues:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Take care to increment the serial number when editing a zone file.</em></span>
+ </div><div class="para">
+ If the serial number is not incremented, the master nameserver has the correct, new information, but the slave nameservers are never notified of the change and do not attempt to refresh their data of that zone.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Be careful to use ellipses and semi-colons correctly in the <code class="filename">/etc/named.conf</code> file.</em></span>
+ </div><div class="para">
+ An omitted semi-colon or unclosed ellipse section can cause <code class="command">named</code> to refuse to start.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Remember to place periods (<code class="command">.</code>) in zone files after all FQDNs and omit them on hostnames.</em></span>
+ </div><div class="para">
+ A period at the end of a domain name denotes a fully qualified domain name. If the period is omitted, then <code class="command">named</code> appends the name of the zone or the <code class="command">$ORIGIN</code> value to complete it.
+ </div></li><li class="listitem"><div class="para">
+ If a firewall is blocking connections from the <code class="command">named</code> daemon to other nameservers, the recommended best practice is to change the firewall settings whenever possible.
+ </div><div class="warning"><h2>Warning: Avoid Using Fixed UDP Source Ports</h2><div class="para">
+ Recent research in DNS security has shown that using a fixed UDP source port for DNS queries is a potential security vulnerability that could allow an attacker to more easily conduct cache-poisoning attacks. Due to this security threat, Red Hat issued a security update<sup>[<a id="id953171" href="#ftn.id953171" class="footnote">3</a>]</sup> for all versions of Red Hat Enterprise Linux which updated the default sample caching-nameserver configuration files so that they do not specify a fixed query-source port, thus causing the BIND nameserver to use a new, randomly-selected source port for each DNS query by default. This method had previously only been used during <span class="application"><strong>named</strong></span> service startup.
+ </div><div class="para">
+ DNS resolving is at risk whenever <span class="application"><strong>named</strong></span> is configured to use a static UDP source port. To avoid this risk, we recommend configuring your firewall to allow queries from a random UDP source port.
+ </div><div class="para">
+ BIND administrators with existing configurations who wish to take advantage of randomized UDP source ports should check their configuration files to ensure that they have not specified fixed query-source ports.
+ </div></div></li></ul></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id953171" href="#id953171" class="para">3</a>] </sup>
+ The security update was <a href="https://rhn.redhat.com/errata/RHSA-2008-0533.html">RHSA-2008:0533</a>.
+ </p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-ipv6.html"><strong>Prev</strong>7.5.4. IP version 6</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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>7.7. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-namedconf.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-namedconf.html
new file mode 100644
index 0000000..ed03038
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-namedconf.html
@@ -0,0 +1,193 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. /etc/named.conf</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 7. The BIND DNS Server" /><link rel="prev" href="ch-The_BIND_DNS_Server.html" title="Chapter 7. The BIND DNS Server" /><link rel="next" href="s2-bind-namedconf-state-other.html" title="7.2.2. Other Statement Types" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade you
r browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="7.2. /etc/named.conf" id="s1-bind-namedconf"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-namedconf">7.2. <code class="filename">/etc/named.conf</code> </h2></div></div></div><a id="id652646" class="indexterm"></a><a id="id877959" class="indexterm"></a><a id="id877976" class="indexterm"></a><div class="para">
+ The <code class="filename">named.conf</code> file is a collection of statements using nested options surrounded by opening and closing ellipse characters, <code class="command">{ }</code>. Administrators must be careful when editing <code class="filename">named.conf</code> to avoid syntax errors as many seemingly minor errors prevent the <code class="command">named</code> service from starting.
+ </div><div class="para">
+ A typical <code class="filename">named.conf</code> file is organized similar to the following example:
+ </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="section" title="7.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">7.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="section" title="7.2.1.1. acl Statement" id="s3-bind-namedconf-state-acl"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-namedconf-state-acl">7.2.1.1. <code class="command">acl</code> Statement</h4></div></div></div><div class="para">
+ The <code class="command">acl</code> (Access Control List) statement defines groups of hosts which can then be permitted or denied access to the nameserver.
+ </div><div class="para">
+ An <code class="command">acl</code> statement 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>;
+[<em class="replaceable"><code><match-element></code></em>; ...]
+};</pre><div class="para">
+ In this statement, replace <em class="replaceable"><code><acl-name></code></em> with the name of the access control list and replace <em class="replaceable"><code><match-element></code></em> with a semi-colon separated list of IP addresses. Most of the time, an individual IP address or CIDR network notation (such as <code class="command">10.0.1.0/24</code>) is used to identify the IP addresses within the <code class="command">acl</code> statement.
+ </div><div class="para">
+ The following access control lists are already defined as keywords to simplify configuration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">any</code> — Matches every IP address
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">localhost</code> — Matches any IP address in use by the local system
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">localnets</code> — Matches any IP address on any network to which the local system is connected
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">none</code> — Matches no IP addresses
+ </div></li></ul></div><div class="para">
+ When used in conjunction with other statements (such as the <code class="command">options</code> statement), <code class="command">acl</code> statements can be very useful in preventing the misuse of a BIND nameserver.
+ </div><div class="para">
+ The following example defines two access control lists and uses an <code class="command">options</code> statement to define how they are treated by the nameserver:
+ </div><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 class="para">
+ This example contains two access control lists, <code class="command">black-hats</code> and <code class="command">red-hats</code>. Hosts in the <code class="command">black-hats</code> list are denied access to the nameserver, while hosts in the <code class="command">red-hats</code> list are given normal access.
+ </div></div><div class="section" title="7.2.1.2. include Statement" id="s3-bind-namedconf-state-inc"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-namedconf-state-inc">7.2.1.2. <code class="command">include</code> Statement</h4></div></div></div><div class="para">
+ The <code class="command">include</code> statement allows files to be included in a <code class="filename">named.conf</code> file. In this way, sensitive configuration data (such as <code class="command">keys</code>) can be placed in a separate file with restrictive permissions.
+ </div><div class="para">
+ An <code class="command">include</code> statement takes the following form:
+ </div><pre class="screen">include "<em class="replaceable"><code><file-name></code></em>"</pre><div class="para">
+ In this statement, <em class="replaceable"><code><file-name></code></em> is replaced with an absolute path to a file.
+ </div></div><div class="section" title="7.2.1.3. options Statement" id="s3-bind-namedconf-state-opt"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-namedconf-state-opt">7.2.1.3. <code class="command">options</code> Statement</h4></div></div></div><div class="para">
+ The <code class="command">options</code> statement defines global server configuration options and sets defaults for other statements. It can be used to specify the location of the <code class="command">named</code> working directory, the types of queries allowed, and much more.
+ </div><div class="para">
+ The <code class="command">options</code> statement takes the following form:
+ </div><pre class="screen">options {
+<em class="replaceable"><code><option></code></em>;
+[<em class="replaceable"><code><option></code></em>; ...]
+};</pre><div class="para">
+ In this statement, the <em class="replaceable"><code><option></code></em> directives are replaced with a valid option.
+ </div><div class="para">
+ The following are commonly used options:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">allow-query</code> </span></dt><dd><div class="para">
+ Specifies which hosts are allowed to query this nameserver for authoritative RRs. By default, all hosts are allowed to query. An access control lists, or collection of IP addresses or networks, may be used here to allow only particular hosts to query the nameserver.
+ </div></dd><dt><span class="term"> <code class="command">allow-query-cache</code> </span></dt><dd><div class="para">
+ Similar to <code class="command">allow-query</code>, this option applies to non-authoritative data, like recursive queries. By default, only <code class="command">localhost;</code> and <code class="command">localnets;</code> are allowed to obtain non-authoritative data.
+ </div></dd><dt><span class="term"> <code class="command">blackhole</code> </span></dt><dd><div class="para">
+ Specifies which hosts are banned from the server. This option should be used when particular host or network floods the server with requests. Default is <code class="command">none;</code>
+ </div></dd><dt><span class="term"> <code class="command">directory</code> </span></dt><dd><div class="para">
+ Specifies the <code class="command">named</code> working directory if different from the default value, <code class="filename">/var/named/</code>.
+ </div></dd><dt><span class="term"> <code class="command">forwarders</code> </span></dt><dd><div class="para">
+ Specifies a list of valid IP addresses for nameservers where requests should be forwarded for resolution.
+ </div></dd><dt><span class="term"> <code class="command">forward</code> </span></dt><dd><div class="para">
+ Specifies the forwarding behavior of a <code class="command">forwarders</code> directive.
+ </div><div class="para">
+ The following options are accepted:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">first</code> — Specifies that the nameservers listed in the <code class="command">forwarders</code> directive be queried before <code class="command">named</code> attempts to resolve the name itself.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">only</code> — Specifies that <code class="command">named</code> does not attempt name resolution itself in the event that queries to nameservers specified in the <code class="command">forwarders</code> directive fail.
+ </div></li></ul></div></dd><dt><span class="term"> <code class="command">listen-on</code> </span></dt><dd><div class="para">
+ Specifies the IPv4 network interface on which <code class="command">named</code> listens for queries. By default, all IPv4 interfaces are used.
+ </div><div class="para">
+ Using this directive on a DNS server which also acts a gateway, BIND can be configured to only answer queries that originate from one of the networks.
+ </div><div class="para">
+ The following is an example of a <code class="command">listen-on</code> directive:
+ </div><pre class="screen">options { listen-on { 10.0.1.1; }; };</pre><div class="para">
+ In this example, server listens only on (<code class="command">10.0.1.1</code>) address.
+ </div></dd><dt><span class="term"> <code class="command">listen-on-v6</code> </span></dt><dd><div class="para">
+ Same as <code class="command">listen-on</code> except for IPv6 interfaces.
+ </div><div class="para">
+ The following is an example of a <code class="command">listen-on-v6</code> directive:
+ </div><pre class="screen">options { listen-on-v6 { 1234:5678::9abc; }; };</pre><div class="para">
+ In this example, server listens only on (<code class="command">1234:5678::9abc</code>) address.
+ </div></dd><dt><span class="term"> <code class="command">max-cache-size</code> </span></dt><dd><div class="para">
+ Specifies the maximum amount of memory to use for server caches. When the amount of data in the cache reaches this limit, the server will cause 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. Default is 32M.
+ </div><pre class="screen">options { max-cache-size 256M; };</pre></dd><dt><span class="term"> <code class="command">notify</code> </span></dt><dd><div class="para">
+ Controls whether <code class="command">named</code> notifies the slave servers when a zone is updated. It accepts the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Notifies slave servers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Does not notify slave servers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">master-only</code> - Send notify only when server is a master server for the zone.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">explicit</code> — Only notifies slave servers specified in an <code class="command">also-notify</code> list within a zone statement.
+ </div></li></ul></div></dd><dt><span class="term"> <code class="command">pid-file</code> </span></dt><dd><div class="para">
+ Specifies the location of the process ID file created by <code class="command">named</code>.
+ </div></dd><dt><span class="term"> <code class="command">recursion</code> </span></dt><dd><div class="para">
+ Specifies if <code class="command">named</code> acts as a recursive server. The default is <code class="command">yes</code>.
+ </div><pre class="screen">options { recursion no; };</pre></dd><dt><span class="term"> <code class="command">statistics-file</code> </span></dt><dd><div class="para">
+ Specifies an alternate location for statistics files. By default, <code class="command">named</code> statistics are saved to the <code class="filename">/var/named/named.stats</code> file.
+ </div></dd></dl></div><div class="para">
+ There are many other options also available, many of which rely upon one another to work properly. 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="7.7.1. Installed Documentation">Section 7.7.1, “Installed Documentation”</a> and the <code class="filename">named.conf</code> man page for more details.
+ </div></div><div class="section" title="7.2.1.4. zone Statement" id="s3-bind-namedconf-state-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-namedconf-state-zone">7.2.1.4. <code class="command">zone</code> Statement</h4></div></div></div><div class="para">
+ A <code class="command">zone</code> statement defines the characteristics of a zone, such as the location of its configuration file and zone-specific options. This statement can be used to override the global <code class="command">options</code> statements.
+ </div><div class="para">
+ A <code class="command">zone</code> statement 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><zone-options></code></em>;
+[<em class="replaceable"><code><zone-options></code></em>; ...]
+};</pre><div class="para">
+ In this statement, <em class="replaceable"><code><zone-name></code></em> 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><zone-options></code></em> is a list of options characterizing the zone.
+ </div><div class="para">
+ The <em class="replaceable"><code><zone-name></code></em> attribute for the zone statement is particularly important. It is the default value assigned for the <code class="command">$ORIGIN</code> directive used within the corresponding zone file located in the <code class="filename">/var/named/</code> directory. The <code class="command">named</code> daemon appends the name of the zone to any non-fully qualified domain name listed in the zone file.
+ </div><div class="para">
+ For example, if a <code class="command">zone</code> statement defines the namespace for <code class="command">example.com</code>, use <code class="command">example.com</code> as the <em class="replaceable"><code><zone-name></code></em> so it is placed at the end of hostnames within the <code class="command">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="7.3. Zone Files">Section 7.3, “Zone Files”</a>.
+ </div><div class="para">
+ The most common <code class="command">zone</code> statement options include the following:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">allow-query</code> </span></dt><dd><div class="para">
+ Specifies the clients that are allowed to request information about this zone. Setting of this option overrides global <code class="command">allow-query</code> option. The default is to allow all query requests.
+ </div></dd><dt><span class="term"> <code class="command">allow-transfer</code> </span></dt><dd><div class="para">
+ Specifies the slave servers that are allowed to request a transfer of the zone's information. The default is to allow all transfer requests.
+ </div></dd><dt><span class="term"> <code class="command">allow-update</code> </span></dt><dd><div class="para">
+ Specifies the hosts that are allowed to dynamically update information in their zone. The default is to deny all dynamic update requests.
+ </div><div class="para">
+ 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. Use TSIG key instead .
+ </div></dd><dt><span class="term"> <code class="command">file</code> </span></dt><dd><div class="para">
+ Specifies the name of the file in the <code class="command">named</code> working directory that contains the zone's configuration data.
+ </div></dd><dt><span class="term"> <code class="command">masters</code> </span></dt><dd><div class="para">
+ Specifies the IP addresses from which to request authoritative zone information and is used only if the zone is defined as <code class="command">type</code> <code class="command">slave</code>.
+ </div></dd><dt><span class="term"> <code class="command">notify</code> </span></dt><dd><div class="para">
+ Specifies whether or not <code class="command">named</code> notifies the slave servers when a zone is updated. This option has same parameters as a global <code class="command">notify</code> parameter.
+ </div></dd><dt><span class="term"> <code class="command">type</code> </span></dt><dd><div class="para">
+ Defines the type of zone.
+ </div><div class="para">
+ Below is a list of valid options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">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="command">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="command">forward</code> — Forwards all requests for information about this zone to other nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">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="command">hint</code> zone.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">master</code> — Designates the nameserver as authoritative for this zone. A zone should be set as the <code class="command">master</code> if the zone's configuration files reside on the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">slave</code> — Designates the nameserver as a slave server for this zone. Master server is specified in <code class="command">masters</code> directive.
+ </div></li></ul></div></dd></dl></div></div><div class="section" title="7.2.1.5. Sample zone Statements" id="s3-bind-configuration-named-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-configuration-named-zone">7.2.1.5. Sample <code class="command">zone</code> Statements</h4></div></div></div><a id="id956556" class="indexterm"></a><div class="para">
+ Most changes to the <code class="filename">/etc/named.conf</code> file of a master or slave nameserver involves adding, modifying, or deleting <code class="command">zone</code> statements. While these <code class="command">zone</code> statements can contain many options, most nameservers require only a small subset to function efficiently. The following <code class="command">zone</code> statements are very basic examples illustrating a master-slave nameserver relationship.
+ </div><div class="para">
+ The following is an example of a <code class="command">zone</code> statement for the primary nameserver hosting <code class="command">example.com</code> (<code class="command">192.168.0.1</code>):
+ </div><pre class="screen">zone "example.com" IN {
+type master;
+file "example.com.zone";
+allow-transfer { 192.168.0.2; };
+};</pre><div class="para">
+ In the statement, the zone is identified as <code class="command">example.com</code>, the type is set to <code class="command">master</code>, and the <code class="command">named</code> service is instructed to read the <code class="filename">/var/named/example.com.zone</code> file. It also allows only slave nameserver (<code class="command">192.168.0.2</code>) to transfer the zone.
+ </div><div class="para">
+ A slave server's <code class="command">zone</code> statement for <code class="command">example.com</code> is slightly different from the previous example. For a slave server, the type is set to <code class="command">slave</code> and the <code class="command">masters</code> directive is telling <code class="command">named</code> the IP address of the master server.
+ </div><div class="para">
+ The following is an example slave server <code class="command">zone</code> statement for <code class="command">example.com</code> zone:
+ </div><pre class="screen">zone "example.com"{
+type slave;
+file "slaves/example.com.zone";
+masters { 192.168.0.1; };
+};</pre><div class="para">
+ This <code class="command">zone</code> statement configures <code class="command">named</code> on the slave server to query the master server at the <code class="command">192.168.0.1</code> IP address for information about the <code class="command">example.com</code> zone. The information that the slave server receives from the master server is saved to the <code class="filename">/var/named/slaves/example.com.zone</code> file. Make sure you put all slave zones to <code class="filename">/var/named/slaves</code> directory otherwise <code class="command">named</code> will fail to transfer the zone.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-The_BIND_DNS_Server.html"><strong>Prev</strong>Chapter 7. 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>7.2.2. Other Statement Types</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-rndc.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-rndc.html
new file mode 100644
index 0000000..e3d826c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-rndc.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>7.4. Using rndc</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 7. The BIND DNS Server" /><link rel="prev" href="s2-bind-configuration-zone-reverse.html" title="7.3.4. Reverse Name Resolution Zone Files" /><link rel="next" href="s2-bind-rndc-configuration-rndcconf.html" title="7.4.2. Configuring /etc/rndc.conf" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifr
ame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-configuration-zone-reverse.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-rndc-configuration-rndcconf.html"><strong>Next</strong></a></li></ul><div class="section" title="7.4. Using rndc" id="s1-bind-rndc"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-rndc">7.4. Using <code class="command">rndc</code> </h2></div></div></div><a id="id829472" class="indexterm"></a><div class="para">
+ BIND includes a utility called <code class="command">rndc</code> which allows command line administration of the <code class="command">named</code> daemon from the localhost or a remote host.
+ </div><div class="para">
+ In order to prevent unauthorized access to the <code class="command">named</code> daemon, BIND uses a shared secret key authentication method to grant privileges to hosts. This means an identical key must be present in both <code class="filename">/etc/named.conf</code> and the <code class="command">rndc</code> configuration file, <code class="filename">/etc/rndc.conf</code>.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ If you have installed the <code class="filename">bind-chroot</code> package, the BIND service will run in the <code class="command">/var/named/chroot</code> environment. All configuration files will be moved there. As such, the <code class="filename">rndc.conf</code> file is located in <code class="filename">/var/named/chroot/etc/rndc.conf</code>.
+ </div><div class="para">
+ Note that since the <code class="command">rndc</code> utility does not run in a <code class="command">chroot</code> environment, <code class="filename">/etc/rndc.conf</code> is a symlink to <code class="filename">/var/named/chroot/etc/rndc.conf</code>.
+ </div></div><div class="section" title="7.4.1. Configuring /etc/named.conf" id="s2-bind-rndc-configuration-namedconf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-configuration-namedconf">7.4.1. Configuring <code class="filename">/etc/named.conf</code> </h3></div></div></div><a id="id983457" class="indexterm"></a><div class="para">
+ In order for <code class="command">rndc</code> to connect to a <code class="command">named</code> service, there must be a <code class="command">controls</code> statement in the BIND server's <code class="filename">/etc/named.conf</code> file.
+ </div><div class="para">
+ The <code class="command">controls</code> statement, shown in the following example, allows <code class="command">rndc</code> to connect from the localhost.
+ </div><pre class="screen">
+controls {
+ inet 127.0.0.1
+ allow { localhost; } keys { <em class="replaceable"><code><key-name></code></em>; };
+};
+</pre><div class="para">
+ This statement tells <code class="command">named</code> to listen on the default TCP port 953 of the loopback address and allow <code class="command">rndc</code> commands coming from the localhost, if the proper key is given. The <em class="replaceable"><code><key-name></code></em> specifies a name in the <code class="command">key</code> statement within the <code class="filename">/etc/named.conf</code> file. The next example illustrates a sample <code class="command">key</code> statement.
+ </div><pre class="screen">
+key "<em class="replaceable"><code><key-name></code></em>" {
+ algorithm hmac-md5;
+ secret "<em class="replaceable"><code><key-value></code></em>";
+};
+</pre><div class="para">
+ In this case, the <em class="replaceable"><code><key-value></code></em> uses the HMAC-MD5 algorithm. Use the following command to generate keys using the HMAC-MD5 algorithm:
+ </div><pre class="screen">
+<code class="command">dnssec-keygen -a hmac-md5 -b <em class="replaceable"><code><bit-length></code></em> -n HOST <em class="replaceable"><code><key-file-name></code></em> </code>
+</pre><div class="para">
+ A key with at least a 256-bit length is a good idea. The actual key that should be placed in the <em class="replaceable"><code><key-value></code></em> area can be found in the <code class="filename"><em class="replaceable"><code><key-file-name></code></em> </code> file generated by this command.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ Because <code class="filename">/etc/named.conf</code> is world-readable, it is advisable to place the <code class="command">key</code> statement in a separate file, readable only by root, and then use an <code class="command">include</code> statement to reference it. For example:
+ </div><pre class="screen">include "/etc/rndc.key";</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-configuration-zone-reverse.html"><strong>Prev</strong>7.3.4. Reverse Name Resolution 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-rndc-configuration-rndcconf.html"><strong>Next</strong>7.4.2. Configuring /etc/rndc.conf </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-zone.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-zone.html
new file mode 100644
index 0000000..8af480a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-bind-zone.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>7.3. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 7. The BIND DNS Server" /><link rel="prev" href="s2-bind-namedconf-comm.html" title="7.2.3. Comment Tags" /><link rel="next" href="s3-bind-zone-rr.html" title="7.3.2. Zone File Resource Records" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s3-bind-zone-rr.html"><strong>Next</strong></a></li></ul><div class="section" title="7.3. Zone Files" id="s1-bind-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-zone">7.3. Zone Files</h2></div></div></div><a id="id968381" class="indexterm"></a><div class="para">
+ <em class="firstterm">Zone files</em> contain information about a namespace and are stored in the <code class="command">named</code> working directory (<code class="filename">/var/named/</code>) by default. Each zone file is named according to the <code class="command">file</code> option data in the <code class="command">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="note"><h2>Note</h2><div class="para">
+ If you have installed the <code class="filename">bind-chroot</code> package, the BIND service will run in the <code class="command">/var/named/chroot</code> environment. All configuration files will be moved there. As such, you can find the zone files in <code class="filename">/var/named/chroot/var/named</code>.
+ </div></div><div class="para">
+ Each zone file may contain <em class="firstterm">directives</em> and <em class="firstterm">resource records</em>. 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. Directives are optional, but resource records are required 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="para">
+ Comments can be placed after semicolon characters (<code class="command">;</code>) in zone files.
+ </div><div class="section" title="7.3.1. Zone File Directives" id="s2-bind-zone-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-zone-directives">7.3.1. Zone File Directives</h3></div></div></div><a id="id854752" class="indexterm"></a><div class="para">
+ Directives begin with the dollar sign character (<code class="command">$</code>) followed by the name of the directive. They usually appear at the top of the zone file.
+ </div><div class="para">
+ The following are commonly used directives:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">$INCLUDE</code> </span></dt><dd><div class="para">
+ Configures <code class="command">named</code> to include another zone file in this zone file at the place where the directive appears. This allows additional zone settings to be stored apart from the main zone file.
+ </div></dd><dt><span class="term"> <code class="command">$ORIGIN</code> </span></dt><dd><div class="para">
+ Appends the domain name to unqualified records, such as those with the hostname and nothing more.
+ </div><div class="para">
+ For example, a zone file may contain the following line:
+ </div><pre class="screen">$ORIGIN example.com.</pre><div class="para">
+ Any names used in resource records that do not end in a trailing period (<code class="command">.</code>) are appended with <code class="command">example.com</code>.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ The use of the <code class="command">$ORIGIN</code> directive is unnecessary if the zone is specified in <code class="filename">/etc/named.conf</code> because the zone name is used as the value for the <code class="command">$ORIGIN</code> directive by default.
+ </div></div></dd><dt><span class="term"> <code class="command">$TTL</code> </span></dt><dd><div class="para">
+ Sets the default <em class="firstterm">Time to Live (TTL)</em> value for the zone. This is the length of time, in seconds, that a zone resource record is 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></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-namedconf-comm.html"><strong>Prev</strong>7.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>7.3.2. Zone File Resource Records</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-check-rpm-sig.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-check-rpm-sig.html
new file mode 100644
index 0000000..fa28a4c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-check-rpm-sig.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</ifram
e></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>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="id909265" 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="id596356" class="indexterm"></a><a id="id596370" class="indexterm"></a><a id="id596383" 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_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp-additional-resources.html
new file mode 100644
index 0000000..3eb1f55
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp-additional-resources.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>10.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 10. Dynamic Host Configuration Protocol (DHCP)" /><link rel="prev" href="s1-dhcp_for_ipv6_dhcpv6.html" title="10.5. DHCP for IPv6 (DHCPv6)" /><link rel="next" href="ch-The_Apache_HTTP_Server.html" title="Chapter 11. The Apache HTTP Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../
toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-The_Apache_HTTP_Server.html"><strong>Next</strong></a></li></ul><div class="section" title="10.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">10.6. Additional Resources</h2></div></div></div><a id="id869006" 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="10.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">10.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>10.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-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_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp-configuring-client.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp-configuring-client.html
new file mode 100644
index 0000000..4829685
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp-configuring-client.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>10.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 10. Dynamic Host Configuration Protocol (DHCP)" /><link rel="prev" href="dhcp-relay-agent.html" title="10.2.4. DHCP Relay Agent" /><link rel="next" href="sect-Configuring_a_Multihomed_DHCP_Server.html" title="10.4. Configuring a Multihomed DHCP Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-relay-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="10.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">10.3. Configuring a DHCP Client</h2></div></div></div><a id="id740821" class="indexterm"></a><a id="id740835" class="indexterm"></a><div cla
ss="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"><h2>Tip</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="dhcp-relay-agent.html"><strong>Prev</strong>10.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>10.4. Configuring a Multihomed DHCP Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp-configuring-server.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp-configuring-server.html
new file mode 100644
index 0000000..fe2837b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp-configuring-server.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>10.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 10. Dynamic Host Configuration Protocol (DHCP)" /><link rel="prev" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 10. Dynamic Host Configuration Protocol (DHCP)" /><link rel="next" href="lease-database.html" title="10.2.2. Lease Database" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" c
lass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-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="10.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">10.2. Configuring a DHCP Server</h2></div></div></div><a id="id930904" 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="10.2.2. Lease Database">Section 10.2.2, “Lease Database”</a> for more information.
+ </div><div class="section" title="10.2.1. Configuration File" id="config-file"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="config-file">10.2.1. Configuration File</h3></div></div></div><a id="id964802" class="indexterm"></a><a id="id755274" 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 mark (#) 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="id755321" 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="id918795" 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"><h2>Important</h2><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 class="note"><h2>Tip</h2><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 class="para">
+ In <a class="xref" href="s1-dhcp-configuring-server.html#subnet" title="Example 10.1. Subnet Declaration">Example 10.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="id986105" 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 10.1. Subnet Declaration" id="subnet"><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><h6>Example 10.1. Subnet Declaration</h6></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 10.2. Range Parameter">Example 10.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 10.2. Range Parameter" id="dynamic-ip"><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><h6>Example 10.2. Range Parameter</h6></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 10.3. Static IP Address using DHCP">Example 10.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 10.3. Static IP Address using DHCP" id="static-ip"><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><h6>Example 10.3. Static IP Address using DHCP</h6></div><br class="example-break" /><a id="id570636" 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 10.4. Shared-network Declaration">Example 10.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 10.4. Shared-network Declaration" id="shared-network"><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><h6>Example 10.4. Shared-network Declaration</h6></div><br class="example-break" /><a id="id788543" class="indexterm"></a><div class="para">
+ As demonstrated in <a class="xref" href="s1-dhcp-configuring-server.html#group" title="Example 10.5. Group Declaration">Example 10.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 10.5. Group Declaration" id="group"><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><h6>Example 10.5. Group Declaration</h6></div><br class="example-break" /><div class="note"><h2>Tip</h2><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 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 10. Dynamic Host Configuration Protocol (...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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>10.2.2. Lease Database</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.html
new file mode 100644
index 0000000..083ad87
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 10. Dynamic Host Configuration Protocol (DHCP)" /><link rel="prev" href="sect-Configuring_a_Multihomed_DHCP_Server.html" title="10.4. Configuring a Multihomed DHCP Server" /><link rel="next" href="s1-dhcp-additional-resources.html" title="10.6. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" c
lass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="10.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">10.5. DHCP for IPv6 (DHCPv6)</h2></div></div></div><a id="id638603" class="indexterm"></a><a id="id638615" 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>10.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>10.6. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-additional-resources.html
new file mode 100644
index 0000000..e5574c8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-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>13.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 13. Email" /><link rel="prev" href="s1-email-mua.html" title="13.6. Mail User Agents" /><link rel="next" href="s2-email-useful-websites.html" title="13.7.2. Useful Websites" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><
p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="13.7. 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">13.7. Additional Resources</h2></div></div></div><a id="id889623" class="indexterm"></a><a id="id889638" class="indexterm"></a><a id="id889652" class="indexterm"></a><a id="id889667" class="indexterm"></a><div class="para">
+ The following is a list of additional documentation about email applications.
+ </div><div class="section" title="13.7.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">13.7.1. Installed Documentation</h3></div></div></div><a id="id889695" 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 <code class="command">m4</code>, 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>13.6. 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>13.7.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-mda.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-mda.html
new file mode 100644
index 0000000..f81b41a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-mda.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>13.5. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 13. Email" /><link rel="prev" href="s1-email-switchmail.html" title="13.4. Mail Transport Agent (MTA) Configuration" /><link rel="next" href="s2-email-procmail-recipes.html" title="13.5.2. Procmail Recipes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enabl
e iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-switchmail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-email-procmail-recipes.html"><strong>Next</strong></a></li></ul><div class="section" title="13.5. Mail Delivery Agents" id="s1-email-mda"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-mda">13.5. 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.
+ </div><a id="id596254" class="indexterm"></a><a id="id992608" 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">
+ 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 <code class="filename">/etc/procmailrc</code> 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="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="section" title="13.5.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">13.5.1. Procmail Configuration</h3></div></div></div><a id="id992716" class="indexterm"></a><a id="id992731" 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 <code class="filename">.procmailrc</code> 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">
+ If the user wants to turn off Procmail filtering of their email lists but leave spam control in place, they would comment out the first <code class="command">INCLUDERC</code> line with a hash mark character (<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 eight 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 1024 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="s1-email-switchmail.html"><strong>Prev</strong>13.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>13.5.2. Procmail Recipes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-mta.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-mta.html
new file mode 100644
index 0000000..353d3c7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-mta.html
@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 13. Email" /><link rel="prev" href="s2-email-types-mua.html" title="13.2.3. Mail User Agent" /><link rel="next" href="s2-email-mta-postfix.html" title="13.3.2. Postfix" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id
="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-postfix.html"><strong>Next</strong></a></li></ul><div class="section" title="13.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">13.3. Mail Transport Agents</h2></div></div></div><div class="para">
+ Fedora includes two primary MTAs: Sendmail and Postfix. Postfix is configured as the default MTA, although it is easy to switch the default MTA to Sendmail.
+ </div><div class="section" title="13.3.1. Sendmail" id="s2-email-mta-sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-mta-sendmail">13.3.1. Sendmail</h3></div></div></div><a id="id597392" class="indexterm"></a><a id="id597406" class="indexterm"></a><div class="para">
+ Sendmail's core purpose, like other MTAs, is to safely transfer email among hosts, usually using the SMTP 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="13.3.1.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">13.3.1.1. Purpose and Limitations</h4></div></div></div><a id="id597430" class="indexterm"></a><a id="id597444" 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 POP or IMAP, 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="13.7. Additional Resources">Section 13.7, “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="13.3.1.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">13.3.1.2. The Default Sendmail Installation</h4></div></div></div><a id="id597496" class="indexterm"></a><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 the root user:
+ </div><pre class="screen">yum install m4</pre></li></ul></div><div class="para">
+ More information on configuring Sendmail can be found in <a class="xref" href="s1-email-mta.html#s3-email-mta-sendmail-changes" title="13.3.1.3. Common Sendmail Configuration Changes">Section 13.3.1.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. Restarting the <span class="application"><strong>sendmail</strong></span> service will cause the configuration changes to take effect:
+ </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">service sendmail restart</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="13.3.1.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">13.3.1.3. Common Sendmail Configuration Changes</h4></div></div></div><a id="id878275" class="indexterm"></a><a id="id878288" 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"><h2>Caution</h2><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 class="para">
+ To add the desired functionality to Sendmail, edit the <code class="filename">/etc/mail/sendmail.mc</code> file as the root user. Once you are finished, restart the <span class="application"><strong>Sendmail</strong></span> service and, if the <span class="package">m4</span> package is installed, the m4 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"><h2>Important</h2><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 class="para">
+ The default configuration which ships with Fedora works for most SMTP-only sites. However, it does not work for UUCP (UNIX to UNIX Copy) 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> 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 <code class="filename">/etc/mail/sendmail.cf</code> files.
+ </div></div><div class="section" title="13.3.1.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">13.3.1.4. Masquerading</h4></div></div></div><a id="id939811" class="indexterm"></a><a id="id939824" 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 <code class="command">m4</code>, 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="13.3.1.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">13.3.1.5. Stopping Spam</h4></div></div></div><a id="id640897" 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, relaying denial (default from version 8.9), access database and sender information checks.</em>
+ </div><div class="para">
+ For example, forwarding of SMTP 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><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 <code class="filename">/etc/mail/access.db</code> is a database, use <code class="command">makemap</code> to activate 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. SMTP servers store information about an emails journey in the message header. As the message travels from one MTA to another, each puts in a "Received" header above all the other Received headers. It is however 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="13.5.2.6. Spam Filters">Section 13.5.2.6, “Spam Filters”</a> for more about using SpamAssassin.
+ </div></div><div class="section" title="13.3.1.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">13.3.1.6. Using Sendmail with LDAP</h4></div></div></div><a id="id748668" class="indexterm"></a><div class="para">
+ Using the <em class="firstterm">Lightweight Directory Access Protocol (LDAP)</em> is a very quick and powerful way to find specific information about a particular user from a much larger group. For example, an LDAP 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, LDAP is largely separate from Sendmail, with LDAP storing the hierarchical user information and Sendmail only being given the result of LDAP queries in pre-addressed email messages.
+ </div><div class="para">
+ However, Sendmail supports a much greater integration with LDAP, where it uses LDAP to replace separately maintained files, such as <code class="filename">aliases</code> and <code class="filename">virtusertables</code>, on different mail servers that work together to support a medium- to enterprise-level organization. In short, LDAP abstracts the mail routing level from Sendmail and its separate configuration files to a powerful LDAP cluster that can be leveraged by many different applications.
+ </div><div class="para">
+ The current version of Sendmail contains support for LDAP. To extend the Sendmail server using LDAP, first get an LDAP 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"><h2>Note</h2><div class="para">
+ This is only for a very basic configuration of Sendmail with LDAP. The configuration can differ greatly from this depending on the implementation of LDAP, especially when configuring several Sendmail machines to use a common LDAP server.
+ </div><div class="para">
+ Consult <code class="filename">/usr/share/sendmail-cf/README</code> for detailed LDAP routing configuration instructions and examples.
+ </div></div><div class="para">
+ Next, recreate the <code class="filename">/etc/mail/sendmail.cf</code> file by running <code class="command">m4</code> and again restarting Sendmail. Refer to <a class="xref" href="s1-email-mta.html#s3-email-mta-sendmail-changes" title="13.3.1.3. Common Sendmail Configuration Changes">Section 13.3.1.3, “Common Sendmail Configuration Changes”</a> for instructions.
+ </div><div class="para">
+ For more information on LDAP, refer to <a class="xref" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)">Chapter 14, <i>Lightweight Directory Access Protocol (LDAP)</i></a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-types-mua.html"><strong>Prev</strong>13.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-postfix.html"><strong>Next</strong>13.3.2. Postfix</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-mua.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-mua.html
new file mode 100644
index 0000000..c9482d3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-mua.html
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.6. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 13. Email" /><link rel="prev" href="s2-email-procmail-recipes.html" title="13.5.2. Procmail Recipes" /><link rel="next" href="s1-email-additional-resources.html" title="13.7. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe displ
ay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="13.6. Mail User Agents" id="s1-email-mua"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-mua">13.6. Mail User Agents</h2></div></div></div><div class="para">
+ There are scores of mail programs available under Fedora. There are full-featured, graphical email client programs, such as <span class="application"><strong>Evolution</strong></span>, as well as 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 the client and server.
+ </div><div class="section" title="13.6.1. Securing Communication" id="s2-email-security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-security">13.6.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="id841435" 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 POP and IMAP 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="13.6.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">13.6.1.1. Secure Email Clients</h4></div></div></div><a id="id841466" 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 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 IMAP and POP have known port numbers (993 and 995, respectively) that the MUA uses to authenticate and download messages.
+ </div></div><div class="section" title="13.6.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">13.6.1.2. Securing Email Client Communications</h4></div></div></div><a id="id841506" class="indexterm"></a><a id="id841525" class="indexterm"></a><div class="para">
+ Offering SSL encryption to IMAP and POP users on the email server is a simple matter.
+ </div><div class="para">
+ First, create an SSL certificate. This can be done 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"><h2>Caution</h2><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 class="para">
+ To create a self-signed SSL certificate for IMAP, change to the <code class="filename">/etc/pki/tls/certs/</code> directory and type the following commands as root:
+ </div><pre class="screen">
+<code class="command">rm -f cyrus-imapd.pem make cyrus-imapd.pem</code>
+</pre><div class="para">
+ Answer all of the questions to complete the process.
+ </div><div class="para">
+ To create a self-signed SSL certificate for POP, change to the <code class="filename">/etc/pki/tls/certs/</code> directory, and type the following commands as root:
+ </div><pre class="screen">
+<code class="command">rm -f ipop3d.pem make ipop3d.pem</code>
+</pre><div class="para">
+ Again, answer all of the questions to complete the process.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Please be sure to remove the default <code class="filename">imapd.pem</code> and <code class="filename">ipop3d.pem</code> files before issuing each <code class="command">make</code> command.
+ </div></div><div class="para">
+ Once finished, execute the <code class="command">/sbin/service xinetd restart</code> command to restart the <code class="command">xinetd</code> daemon which controls <code class="command">imapd</code> and <code class="command">ipop3d</code>.
+ </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 daemons, <code class="command">imapd</code> or <code class="command">pop3d</code>.
+ </div><div class="para">
+ The <code class="command">stunnel</code> program uses external OpenSSL libraries included with Fedora to provide strong cryptography and protect the connections. It is best to apply to a CA to obtain an SSL certificate, but it is also possible to create a self-signed certificate.
+ </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">
+<code class="command">make stunnel.pem</code>
+</pre><div class="para">
+ Again, answer all of the questions to complete the process.
+ </div><div class="para">
+ Once the certificate is generated, it is possible to use the <code class="command">stunnel</code> command to start the <code class="command">imapd</code> mail daemon using the following command:
+ </div><pre class="screen">
+<code class="command">/usr/sbin/stunnel -d 993 -l /usr/sbin/imapd imapd</code>
+</pre><div class="para">
+ Once this command is issued, it is possible to open an IMAP email client and connect to the email server using SSL encryption.
+ </div><div class="para">
+ To start the <code class="command">pop3d</code> using the <code class="command">stunnel</code> command, type the following command:
+ </div><pre class="screen">
+<code class="command">/usr/sbin/stunnel -d 995 -l /usr/sbin/pop3d pop3d</code>
+</pre><div class="para">
+ For more information about how to use <code class="command">stunnel</code>, read the <code class="command">stunnel</code> man page or refer to 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 for <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>13.5.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>13.7. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-switchmail.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-switchmail.html
new file mode 100644
index 0000000..5cffd0e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-switchmail.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 13. Email" /><link rel="prev" href="s2-email-mta-fetchmail.html" title="13.3.3. Fetchmail" /><link rel="next" href="s1-email-mda.html" title="13.5. Mail Delivery Agents" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.
</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-mda.html"><strong>Next</strong></a></li></ul><div class="section" title="13.4. Mail Transport Agent (MTA) Configuration" id="s1-email-switchmail"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-switchmail">13.4. Mail Transport Agent (MTA) Configuration</h2></div></div></div><a id="id791080" class="indexterm"></a><a id="id791094" class="indexterm"></a><a id="id791109" class="indexterm"></a><a id="id791127" class="indexterm"></a><a id="id596117" class="indexterm"></a><
a id="id596128" 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="id596172" class="indexterm"></a><a id="id596182" class="indexterm"></a><div class="para">
+ Fedora 13 provides two MTAs: Sendmail and Postfix. If both are installed, <code class="command">postfix</code> is the default MTA.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-mta-fetchmail.html"><strong>Prev</strong>13.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>13.5. Mail Delivery Agents</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-types.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-types.html
new file mode 100644
index 0000000..838e891
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-email-types.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>13.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 13. Email" /><link rel="prev" href="ch-email.html" title="Chapter 13. Email" /><link rel="next" href="s2-email-types-mda.html" title="13.2.2. Mail Delivery Agent" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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</strong></a></li></ul><div class="section" title="13.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">13.2. Email Program Classifications</h2></div></div></div><a id="id934819" 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="13.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">13.2.1. Mail Transport Agent</h3></div></div></div><a id="id934849" class="indexterm"></a><a id="id934866" class="indexterm"></a><a id="id934880" 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 SMTP. 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 installs two MTAs—Sendmail and Postfix—email client programs are often not required to act as an MTA. Fedora also includes a special purpose MTA called Fetchmail.
+ </div><div class="para">
+ For more information on Sendmail, Postfix, and Fetchmail, refer to <a class="xref" href="s1-email-mta.html" title="13.3. Mail Transport Agents">Section 13.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 13. 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>13.2.2. Mail Delivery Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-resources.html
new file mode 100644
index 0000000..b44ee28
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-resources.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-FTP.html" title="Chapter 12. FTP" /><link rel="prev" href="s2-ftp-vsftpd-conf-opt-net.html" title="12.5.8. Network Options" /><link rel="next" href="s2-ftp-useful-websites.html" title="12.6.2. Useful Websites" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</ifram
e></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-vsftpd-conf-opt-net.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ftp-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" title="12.6. Additional Resources" id="s1-ftp-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ftp-resources">12.6. Additional Resources</h2></div></div></div><a id="id868177" class="indexterm"></a><div class="para">
+ For more information about <code class="command">vsftpd</code>, refer to the following resources.
+ </div><div class="section" title="12.6.1. Installed Documentation" id="s2-ftp-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-installed-documentation">12.6.1. Installed Documentation</h3></div></div></div><a id="id868212" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="filename">/usr/share/doc/vsftpd-<em class="replaceable"><code><version-number></code></em>/</code> directory — Replace <em class="replaceable"><code><version-number></code></em> with the installed version of the <code class="filename">vsftpd</code> package. This directory contains a <code class="filename">README</code> with basic information about the software. The <code class="filename">TUNING</code> file contains basic performance tuning tips and the <code class="filename">SECURITY/</code> directory contains information about the security model employed by <code class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vsftpd</code> related man pages — There are a number of man pages for the daemon and configuration files. The following lists some of the more important man pages.
+ </div><div class="variablelist"><dl><dt><span class="term">Server Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man vsftpd</code> — Describes available command line options for <code class="command">vsftpd</code>.
+ </div></li></ul></div></dd><dt><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man vsftpd.conf</code> — Contains a detailed list of options available within the configuration file for <code class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man 5 hosts_access </code> — Describes the format and options available within the TCP wrappers configuration files: <code class="filename">hosts.allow</code> and <code class="filename">hosts.deny</code>.
+ </div></li></ul></div></dd></dl></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-vsftpd-conf-opt-net.html"><strong>Prev</strong>12.5.8. Network 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-ftp-useful-websites.html"><strong>Next</strong>12.6.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-servers.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-servers.html
new file mode 100644
index 0000000..667259f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-servers.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>12.2. FTP Servers</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-FTP.html" title="Chapter 12. FTP" /><link rel="prev" href="ch-FTP.html" title="Chapter 12. FTP" /><link rel="next" href="s2-ftp-vsftpd-conf.html" title="12.3. Files Installed with vsftpd" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class
="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-FTP.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ftp-vsftpd-conf.html"><strong>Next</strong></a></li></ul><div class="section" title="12.2. FTP Servers" id="s1-ftp-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ftp-servers">12.2. FTP Servers</h2></div></div></div><a id="id947001" class="indexterm"></a><a id="id947022" class="indexterm"></a><a id="id947044" class="indexterm"></a><a id="id639520" class="indexterm"></a><div class="para">
+ Fedora ships with two different FTP servers:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="application"><strong>Red Hat Content Accelerator</strong></span> — A kernel-based Web server that delivers high performance Web server and FTP services. Since speed as its primary design goal, it has limited functionality and runs only as an anonymous FTP server. For more information about configuring and administering <span class="application"><strong>Red Hat Content Accelerator</strong></span>, consult the documentation available online at <a href="http://www.redhat.com/docs/manuals/tux/">http://www.redhat.com/docs/manuals/tux/</a>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vsftpd</code> — A fast, secure FTP daemon which is the preferred FTP server for Fedora. The remainder of this chapter focuses on <code class="command">vsftpd</code>.
+ </div></li></ul></div><div class="section" title="12.2.1. vsftpd" id="s2-ftp-servers-vsftpd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-servers-vsftpd">12.2.1. <code class="command">vsftpd</code> </h3></div></div></div><div class="para">
+ The Very Secure FTP Daemon (<code class="command">vsftpd</code>) is designed from the ground up to be fast, stable, and, most importantly, secure. <code class="command">vsftpd</code> is the only stand-alone FTP server distributed with Fedora, due to its ability to handle large numbers of connections efficiently and securely.
+ </div><div class="para">
+ The security model used by <code class="command">vsftpd</code> has three primary aspects:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Strong separation of privileged and non-privileged processes</em></span> — Separate processes handle different tasks, and each of these processes run with the minimal privileges required for the task.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Tasks requiring elevated privileges are handled by processes with the minimal privilege necessary</em></span> — By leveraging compatibilities found in the <code class="filename">libcap</code> library, tasks that usually require full root privileges can be executed more safely from a less privileged process.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Most processes run in a <code class="command">chroot</code> jail</em></span> — Whenever possible, processes are change-rooted to the directory being shared; this directory is then considered a <code class="command">chroot</code> jail. For example, if the directory <code class="command">/var/ftp/</code> is the primary shared directory, <code class="command">vsftpd</code> reassigns <code class="command">/var/ftp/</code> to the new root directory, known as <code class="command">/</code>. This disallows any potential malicious hacker activities for any directories not contained below the new root directory.
+ </div></li></ul></div><div class="para">
+ Use of these security practices has the following effect on how <code class="command">vsftpd</code> deals with requests:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>The parent process runs with the least privileges required</em></span> — The parent process dynamically calculates the level of privileges it requires to minimize the level of risk. Child processes handle direct interaction with the FTP clients and run with as close to no privileges as possible.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>All operations requiring elevated privileges are handled by a small parent process</em></span> — Much like the Apache HTTP Server, <code class="command">vsftpd</code> launches unprivileged child processes to handle incoming connections. This allows the privileged, parent process to be as small as possible and handle relatively few tasks.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>All requests from unprivileged child processes are distrusted by the parent process</em></span> — Communication with child processes are received over a socket, and the validity of any information from child processes is checked before being acted on.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Most interaction with FTP clients is handled by unprivileged child processes in a <code class="command">chroot</code> jail</em></span> — Because these child processes are unprivileged and only have access to the directory being shared, any crashed processes only allows the attacker access to the shared files.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-FTP.html"><strong>Prev</strong>Chapter 12. FTP</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ftp-vsftpd-conf.html"><strong>Next</strong>12.3. Files Installed with vsftpd </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-vsftpd-conf.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-vsftpd-conf.html
new file mode 100644
index 0000000..0490884
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-vsftpd-conf.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>12.5. vsftpd Configuration 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-FTP.html" title="Chapter 12. FTP" /><link rel="prev" href="s1-ftp-vsftpd-start.html" title="12.4. Starting and Stopping vsftpd" /><link rel="next" href="s2-ftp-vsftpd-conf-opt-login.html" title="12.5.2. Log In Options and Access Controls" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your br
owser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-vsftpd-start.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ftp-vsftpd-conf-opt-login.html"><strong>Next</strong></a></li></ul><div class="section" title="12.5. vsftpd Configuration Options" id="s1-ftp-vsftpd-conf"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ftp-vsftpd-conf">12.5. <code class="command">vsftpd</code> Configuration Options</h2></div></div></div><a id="id760651" class="indexterm"></a><a id="id760672" class="indexterm"></a><div class="para">
+ Although <code class="command">vsftpd</code> may not offer the level of customization other widely available FTP servers have, it offers enough options to fill most administrator's needs. The fact that it is not overly feature-laden limits configuration and programmatic errors.
+ </div><div class="para">
+ All configuration of <code class="command">vsftpd</code> is handled by its configuration file, <code class="filename">/etc/vsftpd/vsftpd.conf</code>. Each directive is on its own line within the file and follows the following format:
+ </div><pre class="screen">
+<em class="replaceable"><code><directive></code></em>=<em class="replaceable"><code><value></code></em>
+</pre><div class="para">
+ For each directive, replace <em class="replaceable"><code><directive></code></em> with a valid directive and <em class="replaceable"><code><value></code></em> with a valid value.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ There must not be any spaces between the <em class="replaceable"><code><directive></code></em>, equal symbol, and the <em class="replaceable"><code><value></code></em> in a directive.
+ </div></div><div class="para">
+ Comment lines must be preceded by a hash mark (<code class="command">#</code>) and are ignored by the daemon.
+ </div><div class="para">
+ For a complete list of all directives available, refer to the man page for <code class="filename">vsftpd.conf</code>.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ For an overview of ways to secure <code class="command">vsftpd</code>, refer to the Fedora 13 <em class="citetitle">Security Guide</em>.
+ </div></div><div class="para">
+ The following is a list of some of the more important directives within <code class="filename">/etc/vsftpd/vsftpd.conf</code>. All directives not explicitly found within <code class="command">vsftpd</code>'s configuration file are set to their default value.
+ </div><div class="section" title="12.5.1. Daemon Options" id="s2-ftp-vsftpd-conf-opt-daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-daemon">12.5.1. Daemon Options</h3></div></div></div><a id="id929286" class="indexterm"></a><div class="para">
+ The following is a list of directives which control the overall behavior of the <code class="command">vsftpd</code> daemon.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">listen</code> — When enabled, <code class="command">vsftpd</code> runs in stand-alone mode. Fedora sets this value to <code class="command">YES</code>. This directive cannot be used in conjunction with the <code class="command">listen_ipv6</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">listen_ipv6</code> — When enabled, <code class="command">vsftpd</code> runs in stand-alone mode, but listens only to IPv6 sockets. This directive cannot be used in conjunction with the <code class="command">listen</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN" class="listitem" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"><div class="para">
+ <code class="command">session_support</code> — When enabled, <code class="command">vsftpd</code> attempts to maintain login sessions for each user through Pluggable Authentication Modules (PAM). Refer to for more information. If session logging is not necessary, disabling this option allows <code class="command">vsftpd</code> to run with less processes and lower privileges.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ftp-vsftpd-start.html"><strong>Prev</strong>12.4. Starting and Stopping vsftpd </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ftp-vsftpd-conf-opt-login.html"><strong>Next</strong>12.5.2. Log In Options and Access Controls</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-vsftpd-start.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-vsftpd-start.html
new file mode 100644
index 0000000..836ee92
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ftp-vsftpd-start.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Starting and Stopping vsftpd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-FTP.html" title="Chapter 12. FTP" /><link rel="prev" href="s2-ftp-vsftpd-conf.html" title="12.3. Files Installed with vsftpd" /><link rel="next" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifra
me display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-vsftpd-conf.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ftp-vsftpd-conf.html"><strong>Next</strong></a></li></ul><div class="section" title="12.4. Starting and Stopping vsftpd" id="s1-ftp-vsftpd-start"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ftp-vsftpd-start">12.4. Starting and Stopping <code class="command">vsftpd</code> </h2></div></div></div><a id="id949517" class="indexterm"></a><a id="id949534" class="indexterm"></a><a id="id949552" class="indexterm"></a><a id="id949570" class="indexterm"></a><a id="id949587" clas
s="indexterm"></a><div class="para">
+ The <code class="filename">vsftpd</code> RPM installs the <code class="filename">/etc/rc.d/init.d/vsftpd</code> script, which can be accessed using the <code class="command">/sbin/service</code> command.
+ </div><div class="para">
+ To start the server, as root type:
+ </div><pre class="screen">
+<code class="command">/sbin/service vsftpd start</code>
+</pre><div class="para">
+ To stop the server, as root type:
+ </div><pre class="screen">
+<code class="command">/sbin/service vsftpd stop</code>
+</pre><div class="para">
+ The <code class="option">restart</code> option is a shorthand way of stopping and then starting <code class="command">vsftpd</code>. This is the most efficient way to make configuration changes take effect after editing the configuration file for <code class="command">vsftpd</code>.
+ </div><div class="para">
+ To restart the server, as root type:
+ </div><pre class="screen">
+<code class="command">/sbin/service vsftpd restart</code>
+</pre><div class="para">
+ The <code class="option">condrestart</code> (<em class="firstterm">conditional restart</em>) option only starts <code class="command">vsftpd</code> if it is currently running. This option is useful for scripts, because it does not start the daemon if it is not running.
+ </div><div class="para">
+ To conditionally restart the server, as root type:
+ </div><pre class="screen">
+<code class="command">/sbin/service vsftpd condrestart</code>
+</pre><div class="para">
+ By default, the <code class="command">vsftpd</code> service does <span class="emphasis"><em>not</em></span> start automatically at boot time. To configure the <code class="command">vsftpd</code> service to start at boot time, use an initscript utility, such as <code class="command">/sbin/chkconfig</code>, <span class="application"><strong>/usr/sbin/ntsysv</strong></span>, or the <span class="application"><strong>Services Configuration Tool</strong></span> program. Refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a> for more information regarding these tools.
+ </div><div class="section" title="12.4.1. Starting Multiple Copies of vsftpd" id="s2-ftp-vsftpd-start-multi"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-start-multi">12.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </h3></div></div></div><a id="id987559" class="indexterm"></a><a id="id987576" class="indexterm"></a><div class="para">
+ Sometimes one computer is used to serve multiple FTP domains. This is a technique called <em class="firstterm">multihoming</em>. One way to multihome using <code class="command">vsftpd</code> is by running multiple copies of the daemon, each with its own configuration file.
+ </div><div class="para">
+ To do this, first assign all relevant IP addresses to network devices or alias network devices on the system. Refer to <a class="xref" href="ch-Network_Configuration.html" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a> for more information about configuring network devices and device aliases. Additional information can be found about network configuration scripts in <a class="xref" href="ch-Network_Interfaces.html" title="Chapter 4. Network Interfaces">Chapter 4, <i>Network Interfaces</i></a>.
+ </div><div class="para">
+ Next, the DNS server for the FTP domains must be configured to reference the correct machine. For information about BIND and its configuration files, refer to <a class="xref" href="ch-The_BIND_DNS_Server.html" title="Chapter 7. The BIND DNS Server">Chapter 7, <i>The BIND DNS Server</i></a>.
+ </div><div class="para">
+ For <code class="command">vsftpd</code> to answer requests on different IP addresses, multiple copies of the daemon must be running. The first copy must be run using the <code class="command">vsftpd</code> initscripts, as outlined in <a class="xref" href="s1-ftp-vsftpd-start.html" title="12.4. Starting and Stopping vsftpd">Section 12.4, “Starting and Stopping <code class="command">vsftpd</code> ”</a>. This copy uses the standard configuration file, <code class="filename">/etc/vsftpd/vsftpd.conf</code>.
+ </div><div class="para">
+ Each additional FTP site must have a configuration file with a unique name in the <code class="filename">/etc/vsftpd/</code> directory, such as <code class="filename">/etc/vsftpd/vsftpd-site-2.conf</code>. Each configuration file must be readable and writable only by root. Within each configuration file for each FTP server listening on an IPv4 network, the following directive must be unique:
+ </div><pre class="screen">
+<code class="command">listen_address=<em class="replaceable"><code>N.N.N.N</code></em> </code>
+</pre><div class="para">
+ Replace <em class="replaceable"><code>N.N.N.N</code></em> with the <span class="emphasis"><em>unique</em></span> IP address for the FTP site being served. If the site is using IPv6, use the <code class="command">listen_address6</code> directive instead.
+ </div><div class="para">
+ Once each additional server has a configuration file, the <code class="command">vsftpd</code> daemon must be launched from a root shell prompt using the following command:
+ </div><pre class="screen">
+<code class="command">vsftpd /etc/vsftpd/<em class="replaceable"><code><configuration-file></code></em> </code> [amp ]
+</pre><div class="para">
+ In the above command, replace <em class="replaceable"><code><configuration-file></code></em> with the unique name for the server's configuration file, such as <code class="filename">/etc/vsftpd/vsftpd-site-2.conf</code>.
+ </div><div class="para">
+ Other directives to consider altering on a per-server basis are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">anon_root</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">local_root</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vsftpd_log_file</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">xferlog_file</code>
+ </div></li></ul></div><div class="para">
+ For a detailed list of directives available within <code class="command">vsftpd</code>'s configuration file, refer to <a class="xref" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options">Section 12.5, “ <code class="command">vsftpd</code> Configuration Options”</a>.
+ </div><div class="para">
+ To configure any additional servers to start automatically at boot time, add the above command to the end of the <code class="filename">/etc/rc.local</code> file.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-vsftpd-conf.html"><strong>Prev</strong>12.3. Files Installed with vsftpd </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ftp-vsftpd-conf.html"><strong>Next</strong>12.5. vsftpd Configuration Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-httpd-mig.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-httpd-mig.html
new file mode 100644
index 0000000..999199f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-httpd-mig.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. Migrating Apache HTTP Server 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="s3-httpd-v2-mig.html" title="11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="t
oc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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</strong></a></li><li class="next"><a accesskey="n" href="s3-httpd-v2-mig.html"><strong>Next</strong></a></li></ul><div class="section" title="11.2. Migrating Apache HTTP Server Configuration Files" id="s1-httpd-mig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-httpd-mig">11.2. Migrating Apache HTTP Server Configuration Files</h2></div></div></div><a id="id964163" class="indexterm"></a><a id="id964180" class="indexterm"></a><a
id="id964198" class="indexterm"></a><div class="section" title="11.2.1. Migrating Apache HTTP Server 2.0 Configuration Files" id="s1-httpd-v22-mig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-httpd-v22-mig">11.2.1. Migrating Apache HTTP Server 2.0 Configuration Files</h3></div></div></div><a id="id604889" class="indexterm"></a><div class="para">
+ This section outlines migration from version 2.0 to 2.2. If you are migrating from version 1.3, please refer to <a class="xref" href="s3-httpd-v2-mig.html" title="11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0">Section 11.2.2, “Migrating Apache HTTP Server 1.3 Configuration Files to 2.0”</a>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Configuration files and startup scripts from version 2.0 need minor adjustments particularly in module names which may have changed. Third party modules which worked in version 2.0 can also work in version 2.2 but need to be recompiled before you load them. Key modules that need to be noted are authentication and authorization modules. For each of the modules which has been renamed the <a href="http://httpd.apache.org/docs/2.2/mod/mod_so.html#loadmodule"><code class="command">LoadModule</code> </a> line will need to be updated.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">mod_userdir</code> module will only act on requests if you provide a <code class="command">UserDir</code> directive indicating a directory name. If you wish to maintain the procedures used in version 2.0, add the directive <code class="command">UserDir public_html</code> in your configuration file.
+ </div></li><li class="listitem"><div class="para">
+ To enable SSL, edit the <code class="filename">httpd.conf</code> file adding the necessary <code class="command">mod_ssl</code> directives. Use <code class="command">apachectl start</code> as <code class="command">apachectl startssl</code> is unavailable in version 2.2. You can view an example of SSL configuration for httpd in <code class="filename">conf/extra/httpd-ssl.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ To test your configuration it is advisable to use <code class="command">service httpd configtest</code> which will detect configuration errors.
+ </div></li></ul></div><div class="para">
+ More information on upgrading from version 2.0 to 2.2 can be found on <a href="http://httpd.apache.org/docs/2.2/upgrading.html">http://httpd.apache.org/docs/2.2/upgrading.html</a>.
+ </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="s3-httpd-v2-mig.html"><strong>Next</strong>11.2.2. Migrating Apache HTTP Server 1.3 Configur...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-httpd-secure-server.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-httpd-secure-server.html
new file mode 100644
index 0000000..1992b5c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-httpd-secure-server.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.8. Apache HTTP Secure Server 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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.7. Virtual Hosts" /><link rel="next" href="s2-secureserver-overview-certs.html" title="11.8.2. An Overview of Certificates and Security" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">T
his is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-secureserver-overview-certs.html"><strong>Next</strong></a></li></ul><div class="section" title="11.8. Apache HTTP Secure Server Configuration" id="s1-httpd-secure-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-httpd-secure-server">11.8. Apache HTTP Secure Server Configuration</h2></div></div></div><a id="id997932" class="indexterm"></a><div class="para">
+ This section provides basic information on the Apache HTTP Server with the <code class="filename">mod_ssl</code> security module enabled to use the OpenSSL library and toolkit. The combination of these three components are referred to in this section as the secure Web server or just as the secure server.
+ </div><div class="para">
+ The <code class="filename">mod_ssl</code> module is a security module for the Apache HTTP Server. The <code class="filename">mod_ssl</code> module uses the tools provided by the OpenSSL Project to add a very important feature to the Apache HTTP Server — the ability to encrypt communications. In contrast, regular HTTP communications between a browser and a Web server are sent in plain text, which could be intercepted and read by someone along the route between the browser and the server.
+ </div><div class="para">
+ This section is not meant to be complete and exclusive documentation for any of these programs. When possible, this guide points to appropriate places where you can find more in-depth documentation on particular subjects.
+ </div><div class="para">
+ This section shows you how to install these programs. You can also learn the steps necessary to generate a private key and a certificate request, how to generate your own self-signed certificate, and how to install a certificate to use with your secure server.
+ </div><div class="para">
+ The <code class="filename">mod_ssl</code> configuration file is located at <code class="filename">/etc/httpd/conf.d/ssl.conf</code>. For this file to be loaded, and hence for <code class="filename">mod_ssl</code> to work, you must have the statement <code class="computeroutput">Include conf.d/*.conf</code> in the <code class="filename">/etc/httpd/conf/httpd.conf</code> file. This statement is included by default in the default Apache HTTP Server configuration file.
+ </div><div class="section" title="11.8.1. An Overview of Security-Related Packages" id="s2-secureserver-optionalpackages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-secureserver-optionalpackages">11.8.1. An Overview of Security-Related Packages</h3></div></div></div><a id="id998016" class="indexterm"></a><div class="para">
+ To enable the secure server, you must have the following packages installed at a minimum:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="filename">httpd</code> </span></dt><dd><div class="para">
+ The <code class="filename">httpd</code> package contains the <code class="command">httpd</code> daemon and related utilities, configuration files, icons, Apache HTTP Server modules, man pages, and other files used by the Apache HTTP Server.
+ </div></dd><dt><span class="term"> <code class="filename">mod_ssl</code> </span></dt><dd><div class="para">
+ The <code class="filename">mod_ssl</code> package includes the <code class="filename">mod_ssl</code> module, which provides strong cryptography for the Apache HTTP Server via the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols.
+ </div></dd><dt><span class="term"> <code class="filename">openssl</code> </span></dt><dd><div class="para">
+ The <code class="filename">openssl</code> package contains the OpenSSL toolkit. The OpenSSL toolkit implements the SSL and TLS protocols, and also includes a general purpose cryptography library.
+ </div></dd></dl></div><div class="para">
+ Additionally, other software packages provide certain security functionalities (but are not required by the secure server to function):
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-virtualhosts.html"><strong>Prev</strong>11.7. 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-secureserver-overview-certs.html"><strong>Next</strong>11.8.2. An Overview of Certificates and Security</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-boot-loader.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-boot-loader.html
new file mode 100644
index 0000000..e390a9e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-boot-loader.html
@@ -0,0 +1,98 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>29.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 29. Manually Upgrading the Kernel" /><link rel="prev" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="29.5. Verifying the Initial RAM Disk Image" /><link rel="next" href="s2-kernel-boot-loader-iseries.html" title="29.6.2. Configuring the OS/400® Boot Loader" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" clas
s="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-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="29.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">29.6. Verifying the Boot Loader</h2></div></div></div><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
+ <a id="id642528" class="indexterm"></a>
+ 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 29.1. Boot Loaders by Architecture" id="tb-grub-arch-loaders"><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="29.6.1. Configuring the GRUB Boot Loader">Section 29.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="29.6.1. Configuring the GRUB Boot Loader">Section 29.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="29.6.2. Configuring the OS/400® Boot Loader">Section 29.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="29.6.3. Configuring the YABOOT Boot Loader">Section 29.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><h6>Table 29.1. Boot Loaders by Architecture</h6></div><br class="table-break" /><div class="section" title="29.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">29.6.1. Configuring the GRUB Boot Loader</h3></div></div></div><div class="para">
+ GRUB's configuration file
+ <a id="id935862" class="indexterm"></a>
+ <a id="id935874" class="indexterm"></a>
+ , <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&
gt;</code></em> </code> line of the same stanza.
+ </div><div class="example" title="Example 29.2. /boot/grub/grub.conf" id="ex-_boot_grub_grub.conf"><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/sda2
+# initrd /initramfs-[generic-]version.img
+#boot=/dev/sda
+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><h6>Example 29.2. /boot/grub/grub.conf</h6></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 29.2. /boot/grub/grub.conf">Example 29.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"><h2>The initrd directive in grub.conf refers to an initramfs image</h2><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 13, 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="29.5. Verifying the Initial RAM Disk Image">Section 29.5, “Verifying the Initial RAM Disk Image”</a>.
+ </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 29.1. Verifying the Initial RAM Disk Image">Procedure 29.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 29.2. /boot/grub/grub.conf">Example 29.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 29.2. /boot/grub/grub.conf">Example 29.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 0), 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"><h2>Important: Causing the GRUB boot menu to display</h2><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 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>29.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>29.6.2. Configuring the OS/400® Boot Loader</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-download.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-download.html
new file mode 100644
index 0000000..89f9946
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-download.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>29.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 29. Manually Upgrading the Kernel" /><link rel="prev" href="s1-kernel-preparing.html" title="29.2. Preparing to Upgrade" /><link rel="next" href="s1-kernel-perform-upgrade.html" title="29.4. Performing the Upgrade" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifram
e, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="29.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">29.3. Downloading the Upgraded Kernel</h2></div></div></div><a id="id921213" class="indexterm"></a><div class="para">
+ There are several ways to determine
+ <a id="id712981" class="indexterm"></a>
+ if an updated kernel is available for the system.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Security Errata —
+ <a id="id713001" class="indexterm"></a>
+ 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 —
+ <a id="id713028" class="indexterm"></a>
+ 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="29.5. Verifying the Initial RAM Disk Image">Section 29.5, “Verifying the Initial RAM Disk Image”</a> and <a class="xref" href="s1-kernel-boot-loader.html" title="29.6. Verifying the Boot Loader">Section 29.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="29.4. Performing the Upgrade">Section 29.4, “Performing the Upgrade”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-preparing.html"><strong>Prev</strong>29.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>29.4. Performing the Upgrade</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-modules-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-modules-additional-resources.html
new file mode 100644
index 0000000..c3d987a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-modules-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>30.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-General_Parameters_and_Modules.html" title="Chapter 30. General Parameters and Modules" /><link rel="prev" href="s2-modules-bonding.html" title="30.5.2. The Channel Bonding Module" /><link rel="next" href="app-Revision_History.html" title="Appendix A. Revision History" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to
view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-modules-bonding.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="30.6. 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">30.6. Additional Resources</h2></div></div></div><div class="para">
+ For more information on kernel modules and their utilities, refer to the following resources.
+ </div><div class="variablelist"><dl><dt><span class="term">man pages</span></dt><dd><div class="para">
+ <code class="command">lsmod</code>, <code class="command">modprobe</code>, <code class="command">mmod</code>, <code class="command">modinfo</code> — Refer to the man pages for these commands to learn how to display module information and manipulate modules.
+ </div></dd><dt><span class="term"> <span class="package">kernel-doc</span> package documentation</span></dt><dd><div class="para">
+ For in-depth documentation on the Fedora kernel, kernel modules and their parameters, install the <span class="package">kernel-doc</span> package:
+ </div><pre class="screen">~]# <code class="command">yum install kernel-doc</code>
+</pre><div class="para">
+ This package installs documentation under <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation</code>.
+ </div></dd><dt><span class="term"> <em class="citetitle">Linux Loadable Kernel Module HOWTO</em> </span></dt><dd><div class="para">
+ <a href="http://tldp.org/HOWTO/Module-HOWTO/">http://tldp.org/HOWTO/Module-HOWTO/</a> — The <em class="citetitle">Linux Loadable Kernel Module HOWTO</em> from the Linux Documentation Project.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-modules-bonding.html"><strong>Prev</strong>30.5.2. The Channel Bonding 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="app-Revision_History.html"><strong>Next</strong>Appendix A. Revision History</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-modules-persistant.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-modules-persistant.html
new file mode 100644
index 0000000..bcc36ef
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-modules-persistant.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>30.2. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-General_Parameters_and_Modules.html" title="Chapter 30. General Parameters and Modules" /><link rel="prev" href="ch-General_Parameters_and_Modules.html" title="Chapter 30. General Parameters and Modules" /><link rel="next" href="s1-modules-parameters-specifying.html" title="30.3. Specifying Module Parameters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src
="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-General_Parameters_and_Modules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-modules-parameters-specifying.html"><strong>Next</strong></a></li></ul><div class="section" title="30.2. Persistent Module Loading" id="s1-kernel-modules-persistant"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-modules-persistant">30.2. Persistent Module Loading</h2></div></div></div><a id="id606100" class="indexterm"></a><a id="id606112" class="indexterm"></a
><div class="para">
+ Many kernel modules are loaded automatically at boot time, as <code class="command">/sbin/lsmod</code> shows. You can specify other modules to be loaded at boot time by creating a file in the <code class="filename">/etc/sysconfig/modules/</code> directory. You can use any name you like for the file that you create, but you must give it a <code class="filename">.modules</code> extension, and you must make it executable by running the following command:
+ </div><pre class="screen">modules]# <code class="command">chmod 755 <em class="replaceable"><code><filename.modules></code></em> </code>
+</pre><div class="note"><h2>No Need to Load Network and SCSI Modules</h2><div class="para">
+ Networking and SCSI modules do not generally need to be manually loaded as they have their own particular loading mechanisms.
+ </div></div><div class="para">
+ Here is a complete sample script named <code class="filename">bluez-uinput.modules</code> that loads the <code class="systemitem">uinput</code> module:
+ </div><div class="example" title="Example 30.1. /etc/sysconfig/modules/bluez-uinput.modules" id="ex-bluez-uinput.modules"><div class="example-contents"><pre class="programlisting">#!/bin/sh
+
+if [ ! -c /dev/input/uinput ] ; then
+ exec /sbin/modprobe uinput >/dev/null 2>&1
+fi</pre></div><h6>Example 30.1. /etc/sysconfig/modules/bluez-uinput.modules</h6></div><br class="example-break" /><div class="para">
+ The first line of any <code class="filename">.modules</code> file should be a shebang line that gives the location of the bash shell interpreter:
+ </div><pre class="programlisting">#!/bin/sh</pre><div class="para">
+ Like many configuration files, all <code class="filename">.modules</code> files are bash scripts. The if-conditional on line 3 tests to make sure that the /dev/input/uinput files does <span class="emphasis"><em>not</em></span> exist (the <span class="keycap"><strong>!</strong></span> symbol negates the condition), and, if that is the case, then executes <code class="command">/sbin/modprobe</code> with the name of the kernel module to load—<code class="systemitem">uinput</code> in this example. The remainder of the line simply redirects any output so that the <code class="command">modprobe</code> command is quiet.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-General_Parameters_and_Modules.html"><strong>Prev</strong>Chapter 30. General Parameters and 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-modules-parameters-specifying.html"><strong>Next</strong>30.3. Specifying Module Parameters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-perform-upgrade.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-perform-upgrade.html
new file mode 100644
index 0000000..0156b78
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-perform-upgrade.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>29.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 29. Manually Upgrading the Kernel" /><link rel="prev" href="s1-kernel-download.html" title="29.3. Downloading the Upgraded Kernel" /><link rel="next" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="29.5. Verifying the Initial RAM Disk Image" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../..
/../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-download.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="29.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">29.4. Performing the Upgrade</h2></div></div></div><div class="para">
+ After retrieving all of the necessary packages
+ <a id="id713088" class="indexterm"></a>
+ , it is time to upgrade the existing kernel.
+ </div><div class="important"><h2>Important</h2><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 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="29.5. Verifying the Initial RAM Disk Image">Section 29.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>29.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>29.5. Verifying the Initial RAM Disk Image</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-preparing.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-preparing.html
new file mode 100644
index 0000000..1d48775
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-kernel-preparing.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>29.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 29. Manually Upgrading the Kernel" /><link rel="prev" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 29. Manually Upgrading the Kernel" /><link rel="next" href="s1-kernel-download.html" title="29.3. Downloading the Upgraded Kernel" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.ht
ml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="29.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">29.2. Preparing to Upgrade</h2></div></div></div><a id="id932584" class="indexterm"></a><div class="para">
+ Before upgrading the kernel
+ <a id="id932596" class="indexterm"></a>
+ <a id="id932612" class="indexterm"></a>
+ , it is recommended that you take some precautionary steps.
+ </div><div class="para">
+ In the first step, make sure working boot media exists
+ <a id="id932627" class="indexterm"></a>
+ 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 the <code class="command">mkbootdisk</code> man page 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="29.1. Overview of Kernel Packages">Section 29.1, “Overview of Kernel Packages”</a> for descriptions of the different packages.
+ </div><div class="para">
+ In the file name, each kernel package contains the architecture for which the package was built. The format is kernel-<em class="replaceable"><code><variant></code></em>-<em class="replaceable"><code><version></code></em>.<em class="replaceable"><code><arch></code></em>.rpm, where <em class="replaceable"><code><variant></code></em> is one of either <span class="package">PAE</span>, <span class="package">xen</span>, and so forth. The <em class="replaceable"><code><arch></code></em> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">x86_64</code> for the AMD64 and Intel EM64T architectures
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ppc64</code> for the <span class="trademark">IBM</span>® <span class="trademark">eServer</span>™ <span class="trademark">pSeries</span>™ architecture
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">s390x</code> for the <span class="trademark">IBM</span>® <span class="trademark">eServer</span>™ <span class="trademark">System z</span>® architecture
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">i686</code> for <span class="trademark">Intel</span>® <span class="trademark">Pentium</span>® II, <span class="trademark">Intel</span>® <span class="trademark">Pentium</span>® III, <span class="trademark">Intel</span>® <span class="trademark">Pentium</span>® 4, <span class="trademark">AMD Athlon</span>®, and <span class="trademark">AMD Duron</span>® systems
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Manually_Upgrading_the_Kernel.html"><strong>Prev</strong>Chapter 29. 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>29.3. Downloading the Upgraded Kernel</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-keyboard-break.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-keyboard-break.html
new file mode 100644
index 0000000..76c5348
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-keyboard-break.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Keyboard_Configuration.html" title="Chapter 20. Keyboard Configuration" /><link rel="prev" href="s1-keyboard-indicator.html" title="20.2. Adding the Keyboard Layout Indicator" /><link rel="next" href="ch-The_X_Window_System.html" title="Chapter 21. The X Window System" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe
, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="ch-The_X_Window_System.html"><strong>Next</strong></a></li></ul><div class="section" title="20.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">20.3. Setting Up a Typing Break</h2></div></div></div><a id="id965068" 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 20.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 20.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 20.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 20.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>20.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="ch-The_X_Window_System.html"><strong>Next</strong>Chapter 21. The X Window System</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-keyboard-indicator.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-keyboard-indicator.html
new file mode 100644
index 0000000..6df2748
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-keyboard-indicator.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>20.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Keyboard_Configuration.html" title="Chapter 20. Keyboard Configuration" /><link rel="prev" href="ch-Keyboard_Configuration.html" title="Chapter 20. Keyboard Configuration" /><link rel="next" href="s1-keyboard-break.html" title="20.3. Setting Up a Typing Break" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifra
me, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="20.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">20.2. Adding the Keyboard Layout Indicator</h2></div></div></div><a id="id656980" class="indexterm"></a><a id="id656994" 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 20.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 20.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 20.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 20.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 20.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 20.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 20. 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>20.3. Setting Up a Typing Break</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-additional-resources.html
new file mode 100644
index 0000000..ea4c1d2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-additional-resources.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>14.9. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" /><link rel="prev" href="s1-ldap-migrate.html" title="14.8. Migrating Directories from Earlier Releases" /><link rel="next" href="s2-ldap-additional-resources-web.html" title="14.9.2. Useful Websites" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="
../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-migrate.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ldap-additional-resources-web.html"><strong>Next</strong></a></li></ul><div class="section" title="14.9. Additional Resources" id="s1-ldap-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-additional-resources">14.9. Additional Resources</h2></div></div></div><a id="id843055" class="indexterm"></a><div class="para">
+ The following resources offer additional information on LDAP. It is highly recommended that you review these, especially the OpenLDAP website and the LDAP HOWTO, before configuring LDAP on your system(s).
+ </div><div class="section" title="14.9.1. Installed Documentation" id="s2-ldap-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-installed-docs">14.9.1. Installed Documentation</h3></div></div></div><a id="id992963" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/docs/openldap-<em class="replaceable"><code><versionnumber></code></em>/</code> directory — Contains a general <code class="filename">README</code> document and miscellaneous information.
+ </div></li><li class="listitem"><div class="para">
+ LDAP related man pages — There are a number of man pages for the various applications and configuration files involved with LDAP. The following is a list of some of the more important man pages.
+ </div><div class="variablelist"><dl><dt><span class="term">Client Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man ldapadd</code> — Describes how to add entries to an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapdelete</code> — Describes how to delete entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapmodify</code> — Describes how to modify entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapsearch</code> — Describes how to search for entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldappasswd</code> — Describes how to set or change the password of an LDAP user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapcompare</code> — Describes how to use the <code class="command">ldapcompare</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapwhoami</code> — Describes how to use the <code class="command">ldapwhoami</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ldapmodrdn</code> — Describes how to modify the RDNs of entries.
+ </div></li></ul></div></dd><dt><span class="term">Server Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man slapd</code> — Describes command line options for the LDAP server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slurpd</code> — Describes command line options for the LDAP replication server.
+ </div></li></ul></div></dd><dt><span class="term">Administrative Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man slapadd</code> — Describes command line options used to add entries to a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slapcat</code> — Describes command line options used to generate an LDIF file from a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slapindex</code> — Describes command line options used to regenerate an index based upon the contents of a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slappasswd</code> — Describes command line options used to generate user passwords for LDAP directories.
+ </div></li></ul></div></dd><dt><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man ldap.conf</code> — Describes the format and options available within the configuration file for LDAP clients.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man slapd.conf</code> — Describes the format and options available within the configuration file referenced by both the LDAP server applications (<code class="command">slapd</code> and <code class="command">slurpd</code>) and the LDAP administrative tools (<code class="command">slapadd</code>, <code class="command">slapcat</code>, and <code class="command">slapindex</code>).
+ </div></li></ul></div></dd></dl></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ldap-migrate.html"><strong>Prev</strong>14.8. Migrating Directories from Earlier Releases</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ldap-additional-resources-web.html"><strong>Next</strong>14.9.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-daemonsutils.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-daemonsutils.html
new file mode 100644
index 0000000..f827b11
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-daemonsutils.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>14.3. OpenLDAP Daemons and Utilities</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" /><link rel="prev" href="s1-ldap-terminology.html" title="14.2. LDAP Terminology" /><link rel="next" href="s2-ldap-other-apps.html" title="14.3.2. PHP4, LDAP, and the Apache HTTP Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../.
./../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-terminology.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ldap-other-apps.html"><strong>Next</strong></a></li></ul><div class="section" title="14.3. OpenLDAP Daemons and Utilities" id="s1-ldap-daemonsutils"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-daemonsutils">14.3. OpenLDAP Daemons and Utilities</h2></div></div></div><a id="id986392" class="indexterm"></a><a id="id986406" class="indexterm"></a><a id="id986424" class="indexterm"></a>
<a id="id986441" class="indexterm"></a><a id="id986459" class="indexterm"></a><a id="id986480" class="indexterm"></a><a id="id986498" class="indexterm"></a><a id="id986520" class="indexterm"></a><a id="id646117" class="indexterm"></a><a id="id646139" class="indexterm"></a><a id="id646156" class="indexterm"></a><a id="id646178" class="indexterm"></a><a id="id646195" class="indexterm"></a><a id="id646217" class="indexterm"></a><a id="id646235" class="indexterm"></a><a id="id858314" class="indexterm"></a><a id="id858332" class="indexterm"></a><a id="id858353" class="indexterm"></a><a id="id858371" class="indexterm"></a><a id="id858393" class="indexterm"></a><a id="id858410" class="indexterm"></a><a id="id858432" class="indexterm"></a><a id="id858449" class="indexterm"></a><a id="id927786" class="indexterm"></a><a id="id927804" class="indexterm"></a><div class="para">
+ The suite of OpenLDAP libraries and tools are included within the following packages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">openldap</code> — Contains the libraries necessary to run the OpenLDAP server and client applications.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">openldap-clients</code> — Contains command line tools for viewing and modifying directories on an LDAP server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">openldap-servers</code> — Contains the servers and other utilities necessary to configure and run an LDAP server.
+ </div></li></ul></div><div class="para">
+ There are two servers contained in the <code class="filename">openldap-servers</code> package: the <em class="firstterm">Standalone LDAP Daemon</em> (<code class="command">/usr/sbin/slapd</code>) and the <em class="firstterm">Standalone LDAP Update Replication Daemon</em> (<code class="command">/usr/sbin/slurpd</code>).
+ </div><div class="para">
+ The <code class="command">slapd</code> daemon is the standalone LDAP server while the <code class="command">slurpd</code> daemon is used to synchronize changes from one LDAP server to other LDAP servers on the network. The <code class="command">slurpd</code> daemon is only used when dealing with multiple LDAP servers.
+ </div><div class="para">
+ To perform administrative tasks, the <code class="filename">openldap-servers</code> package installs the following utilities into the <code class="filename">/usr/sbin/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">slapadd</code> — Adds entries from an LDIF file to an LDAP directory. For example, the command <code class="command">/usr/sbin/slapadd -l <em class="replaceable"><code>ldif-input</code></em> </code> reads in the LDIF file, <code class="filename"><em class="replaceable"><code>ldif-input</code></em> </code>, containing the new entries.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Only the root user may use <code class="command">/usr/sbin/slapadd</code>. However, the directory server runs as the <code class="filename">ldap</code> user. Therefore the directory server is unable to modify any files created by <code class="command">slapadd</code>. To correct this issue, after using <code class="command">slapadd</code>, type the following command:
+ </div><pre class="screen">chown -R ldap /var/lib/ldap</pre></div></li><li class="listitem"><div class="para">
+ <code class="command">slapcat</code> — Pulls entries from an LDAP directory in the default format, <em class="firstterm">Sleepycat Software's Berkeley DB</em> system, and saves them in an LDIF file. For example, the command <code class="command">/usr/sbin/slapcat -l <em class="replaceable"><code>ldif-output</code></em> </code> outputs an LDIF file called <code class="filename"><em class="replaceable"><code>ldif-output</code></em> </code> containing the entries from the LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">slapindex</code> — Re-indexes the <code class="command">slapd</code> directory based on the current content. This tool should be run whenever indexing options within <code class="filename">/etc/openldap/slapd.conf</code> are changed.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">slappasswd</code> — Generates an encrypted user password value for use with <code class="command">ldapmodify</code> or the <code class="command">rootpw</code> value in the <code class="command">slapd</code> configuration file, <code class="filename">/etc/openldap/slapd.conf</code>. Execute the <code class="command">/usr/sbin/slappasswd</code> command to create the password.
+ </div></li></ul></div><div class="warning"><h2>Warning</h2><div class="para">
+ You must stop <code class="command">slapd</code> by issuing the <code class="command">/sbin/service ldap stop</code> command before using <code class="command">slapadd</code>, <code class="command">slapcat</code> or <code class="command">slapindex</code>. Otherwise, the integrity of the LDAP directory is at risk.
+ </div></div><div class="para">
+ For more information on using these utilities, refer to their respective man pages.
+ </div><div class="para">
+ The <code class="filename">openldap-clients</code> package installs tools into <code class="filename">/usr/bin/</code> which are used to add, modify, and delete entries in an LDAP directory. These tools include the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">ldapadd</code> — Adds entries to an LDAP directory by accepting input via a file or standard input; <code class="command">ldapadd</code> is actually a hard link to <code class="command">ldapmodify -a</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapdelete</code> — Deletes entries from an LDAP directory by accepting user input at a shell prompt or via a file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapmodify</code> — Modifies entries in an LDAP directory, accepting input via a file or standard input.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldappasswd</code> — Sets the password for an LDAP user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapsearch</code> — Searches for entries in an LDAP directory using a shell prompt.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapcompare</code> — Opens a connection to an LDAP server, binds, and performs a comparison using specified parameters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapwhoami</code> — Opens a connection to an LDAP server, binds, and performs a <code class="command">whoami</code> operation.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ldapmodrdn</code> — Opens a connection to an LDAP server, binds, and modifies the RDNs of entries.
+ </div></li></ul></div><div class="para">
+ With the exception of <code class="command">ldapsearch</code>, each of these utilities is more easily used by referencing a file containing the changes to be made rather than typing a command for each entry to be changed within an LDAP directory. The format of such a file is outlined in the man page for each utility.
+ </div><div class="section" title="14.3.1. NSS, PAM, and LDAP" id="s2-ldap-pam-nss"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-pam-nss">14.3.1. NSS, PAM, and LDAP</h3></div></div></div><a id="id859632" class="indexterm"></a><a id="id859645" class="indexterm"></a><div class="para">
+ In addition to the OpenLDAP packages, Fedora includes a package called <code class="filename">nss_ldap</code>, which enhances LDAP's ability to integrate into both Linux and other UNIX environments.
+ </div><div class="para">
+ The <code class="filename">nss_ldap</code> package provides the following modules (where <em class="replaceable"><code><version></code></em> refers to the version of <code class="filename">libnss_ldap</code> in use):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/lib/libnss_ldap-<em class="replaceable"><code><version></code></em>.so</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/lib/security/pam_ldap.so</code>
+ </div></li></ul></div><div class="para">
+ The <code class="filename">nss_ldap</code> package provides the following modules for 64-bit architectures:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/lib64/libnss_ldap-<em class="replaceable"><code><version></code></em>.so</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/lib64/security/pam_ldap.so</code>
+ </div></li></ul></div><div class="para">
+ The <code class="filename">libnss_ldap-<em class="replaceable"><code><version></code></em>.so</code> module allows applications to look up users, groups, hosts, and other information using an LDAP directory via the <em class="firstterm">Nameservice Switch</em> (NSS) interface of <code class="command">glibc</code>. NSS allows applications to authenticate using LDAP in conjunction with the NIS name service and flat authentication files.
+ </div><div class="para">
+ The <code class="filename">pam_ldap</code> module allows PAM-aware applications to authenticate users using information stored in an LDAP directory. PAM-aware applications include console login, POP and IMAP mail servers, and Samba. By deploying an LDAP server on a network, all of these applications can authenticate using the same user ID and password combination, greatly simplifying administration.
+ </div><div class="para">
+ For more information about configuring PAM, refer to refer to the <em class="citetitle">Pluggable Authentication Modules (PAM)</em> chapter of the Fedora 13 6 <em class="citetitle">Security Guide</em> and the PAM man pages.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ldap-terminology.html"><strong>Prev</strong>14.2. LDAP Terminology</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ldap-other-apps.html"><strong>Next</strong>14.3.2. PHP4, LDAP, and the Apache HTTP Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-files-schemas.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-files-schemas.html
new file mode 100644
index 0000000..f6c9ca0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-files-schemas.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.5. The /etc/openldap/schema/ 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" /><link rel="prev" href="s1-ldap-files.html" title="14.4. OpenLDAP Configuration Files" /><link rel="next" href="s1-ldap-quickstart.html" title="14.6. OpenLDAP Setup Overview" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../.
./toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ldap-quickstart.html"><strong>Next</strong></a></li></ul><div class="section" title="14.5. The /etc/openldap/schema/ Directory" id="s1-ldap-files-schemas"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-files-schemas">14.5. The <code class="filename">/etc/openldap/schema/</code> Directory</h2></div></div></div><a id="id993534" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/openldap/schema/</code> directory holds LDAP definitions, previously located in the <code class="filename">slapd.at.conf</code> and <code class="filename">slapd.oc.conf</code> files. The <code class="filename">/etc/openldap/schema/redhat/</code> directory holds customized schemas distributed by Red Hat for Fedora.
+ </div><div class="para">
+ All <em class="firstterm">attribute syntax definitions</em> and <em class="firstterm">objectclass definitions</em> are now located in the different schema files. The various schema files are referenced in <code class="filename">/etc/openldap/slapd.conf</code> using <code class="filename">include</code> lines, as shown in this example:
+ </div><pre class="screen">
+include /etc/openldap/schema/core.schema
+include /etc/openldap/schema/cosine.schema
+include /etc/openldap/schema/inetorgperson.schema
+include /etc/openldap/schema/nis.schema
+include /etc/openldap/schema/rfc822-MailMember.schema
+include /etc/openldap/schema/redhat/autofs.schema
+</pre><div class="warning"><h2>Caution</h2><div class="para">
+ Do not modify schema items defined in the schema files installed by OpenLDAP.
+ </div></div><div class="para">
+ It is possible to extend the schema used by OpenLDAP to support additional attribute types and object classes using the default schema files as a guide. To do this, create a <code class="filename">local.schema</code> file in the <code class="filename">/etc/openldap/schema/</code> directory. Reference this new schema within <code class="filename">slapd.conf</code> by adding the following line below the default <code class="filename">include</code> schema lines:
+ </div><pre class="screen">include /etc/openldap/schema/local.schema</pre><div class="para">
+ Next, define new attribute types and object classes within the <code class="filename">local.schema</code> file. Many organizations use existing attribute types from the schema files installed by default and add new object classes to the <code class="filename">local.schema</code> file.
+ </div><div class="para">
+ Extending the schema to match certain specialized requirements is quite involved and beyond the scope of this chapter. Refer to <a href="http://www.openldap.org/doc/admin/schema.html">http://www.openldap.org/doc/admin/schema.html</a> for information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ldap-files.html"><strong>Prev</strong>14.4. OpenLDAP 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="s1-ldap-quickstart.html"><strong>Next</strong>14.6. OpenLDAP Setup Overview</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-files.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-files.html
new file mode 100644
index 0000000..8b47827
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-files.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.4. OpenLDAP 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" /><link rel="prev" href="s2-ldap-applications.html" title="14.3.3. LDAP Client Applications" /><link rel="next" href="s1-ldap-files-schemas.html" title="14.5. The /etc/openldap/schema/ Directory" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" sr
c="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-applications.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ldap-files-schemas.html"><strong>Next</strong></a></li></ul><div class="section" title="14.4. OpenLDAP Configuration Files" id="s1-ldap-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-files">14.4. OpenLDAP Configuration Files</h2></div></div></div><a id="id662918" class="indexterm"></a><a id="id662941" class="indexterm"></a><a id="id662963" class="indexterm"></a><a id="
id662986" class="indexterm"></a><div class="para">
+ OpenLDAP configuration files are installed into the <code class="filename">/etc/openldap/</code> directory. The following is a brief list highlighting the most important directories and files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/etc/openldap/ldap.conf</code> — This is the configuration file for all <span class="emphasis"><em>client</em></span> applications which use the OpenLDAP libraries such as <code class="command">ldapsearch</code>, <code class="command">ldapadd</code>, Sendmail, <span class="application"><strong>Evolution</strong></span>, and <span class="application"><strong>Ekiga</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/openldap/slapd.conf</code> — This is the configuration file for the <code class="command">slapd</code> daemon. Refer to <a class="xref" href="s1-ldap-quickstart.html#s2-ldap-files-slapd-conf" title="14.6.1. Editing /etc/openldap/slapd.conf">Section 14.6.1, “Editing <code class="filename">/etc/openldap/slapd.conf</code> ”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/openldap/schema/</code> directory — This subdirectory contains the schema used by the <code class="command">slapd</code> daemon. Refer to <a class="xref" href="s1-ldap-files-schemas.html" title="14.5. The /etc/openldap/schema/ Directory">Section 14.5, “The <code class="filename">/etc/openldap/schema/</code> Directory”</a> for more information.
+ </div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
+ If the <code class="filename">nss_ldap</code> package is installed, it creates a file named <code class="filename">/etc/ldap.conf</code>. This file is used by the PAM and NSS modules supplied by the <code class="filename">nss_ldap</code> package. Refer to <a class="xref" href="s1-ldap-pam.html" title="14.7. Configuring a System to Authenticate Using OpenLDAP">Section 14.7, “Configuring a System to Authenticate Using OpenLDAP”</a> for more information.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ldap-applications.html"><strong>Prev</strong>14.3.3. LDAP Client Applications</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ldap-files-schemas.html"><strong>Next</strong>14.5. The /etc/openldap/schema/ Directory</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-migrate.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-migrate.html
new file mode 100644
index 0000000..b18f858
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-migrate.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.8. Migrating Directories from Earlier Releases</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" /><link rel="prev" href="s2-ldap-migrate.html" title="14.7.2. Migrating Old Authentication Information to LDAP Format" /><link rel="next" href="s1-ldap-additional-resources.html" title="14.9. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><if
rame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-migrate.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ldap-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="14.8. Migrating Directories from Earlier Releases" id="s1-ldap-migrate"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-migrate">14.8. Migrating Directories from Earlier Releases</h2></div></div></div><a id="id842938" class="indexterm"></a><a id="id842956"
class="indexterm"></a><div class="para">
+ With Fedora, OpenLDAP uses Sleepycat Software's Berkeley DB system as its on-disk storage format for directories. Earlier versions of OpenLDAP used <em class="firstterm">GNU Database Manager</em> (<em class="firstterm">gdbm</em>). For this reason, before upgrading an LDAP implementation to Fedora 5.2, original LDAP data should first be exported before the upgrade, and then reimported afterwards. This can be achieved by performing the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Before upgrading the operating system, run the command <code class="command">/usr/sbin/slapcat -l <em class="replaceable"><code>ldif-output</code></em> </code>. This outputs an LDIF file called <code class="filename"><em class="replaceable"><code>ldif-output</code></em> </code> containing the entries from the LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ Upgrade the operating system, being careful not to reformat the partition containing the LDIF file.
+ </div></li><li class="listitem"><div class="para">
+ Re-import the LDAP directory to the upgraded Berkeley DB format by executing the command <code class="command">/usr/sbin/slapadd -l <em class="replaceable"><code>ldif-output</code></em> </code>.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ldap-migrate.html"><strong>Prev</strong>14.7.2. Migrating Old Authentication 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-ldap-additional-resources.html"><strong>Next</strong>14.9. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-pam.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-pam.html
new file mode 100644
index 0000000..87fb4c6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-pam.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>14.7. Configuring a System to Authenticate Using OpenLDAP</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" /><link rel="prev" href="s1-ldap-quickstart.html" title="14.6. OpenLDAP Setup Overview" /><link rel="next" href="s2-ldap-migrate.html" title="14.7.2. Migrating Old Authentication Information to LDAP Format" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><i
frame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-quickstart.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ldap-migrate.html"><strong>Next</strong></a></li></ul><div class="section" title="14.7. Configuring a System to Authenticate Using OpenLDAP" id="s1-ldap-pam"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-pam">14.7. Configuring a System to Authenticate Using OpenLDAP</h2></div></div></div><a id="id885101" class="indexterm"></a><div class="para"
>
+ This section provides a brief overview of how to configure OpenLDAP user authentication. Unless you are an OpenLDAP expert, more documentation than is provided here is necessary. Refer to the references provided in <a class="xref" href="s1-ldap-additional-resources.html" title="14.9. Additional Resources">Section 14.9, “Additional Resources”</a> for more information.
+ </div><a id="id885126" class="indexterm"></a><a id="id885144" class="indexterm"></a><a id="id885167" class="indexterm"></a><a id="id885185" class="indexterm"></a><a id="id887327" class="indexterm"></a><a id="id887350" class="indexterm"></a><a id="id887372" class="indexterm"></a><a id="id887390" class="indexterm"></a><div class="formalpara"><h5 class="formalpara" id="id887416">Install the Necessary LDAP Packages.</h5>
+ First, make sure that the appropriate packages are installed on both the LDAP server and the LDAP client machines. The LDAP server needs the <code class="filename">openldap-servers</code> package.
+ </div><div class="para">
+ The <code class="filename">openldap</code>, <code class="filename">openldap-clients</code>, and <code class="filename">nss_ldap</code> packages need to be installed on all LDAP client machines.
+ </div><h3>Edit the Configuration Files</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On the server, edit the <code class="filename">/etc/openldap/slapd.conf</code> file on the LDAP server to make sure it matches the specifics of the organization. Refer to <a class="xref" href="s1-ldap-quickstart.html#s2-ldap-files-slapd-conf" title="14.6.1. Editing /etc/openldap/slapd.conf">Section 14.6.1, “Editing <code class="filename">/etc/openldap/slapd.conf</code> ”</a> for instructions about editing <code class="filename">slapd.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ On the client machines, both <code class="filename">/etc/ldap.conf</code> and <code class="filename">/etc/openldap/ldap.conf</code> need to contain the proper server and search base information for the organization.
+ </div><div class="para">
+ To do this, run the graphical <span class="application"><strong>Authentication Configuration Tool</strong></span> (<code class="command">system-config-authentication</code>) and select <span class="guilabel"><strong>Enable LDAP Support</strong></span> under the <span class="guilabel"><strong>User Information</strong></span> tab.
+ </div><div class="para">
+ It is also possible to edit these files by hand.
+ </div></li><li class="listitem"><div class="para">
+ On the client machines, the <code class="filename">/etc/nsswitch.conf</code> must be edited to use LDAP.
+ </div><div class="para">
+ To do this, run the <span class="application"><strong>Authentication Configuration Tool</strong></span> (<code class="command">system-config-authentication</code>) and select <span class="guilabel"><strong>Enable LDAP Support</strong></span> under the <span class="guilabel"><strong>User Information</strong></span> tab.
+ </div><div class="para">
+ If editing <code class="filename">/etc/nsswitch.conf</code> by hand, add <code class="command">ldap</code> to the appropriate lines.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+passwd: files ldap
+shadow: files ldap
+group: files ldap
+</pre></li></ul></div><div class="section" title="14.7.1. PAM and LDAP" id="s2-ldap-pamd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-pamd">14.7.1. PAM and LDAP</h3></div></div></div><a id="id826144" class="indexterm"></a><a id="id826162" class="indexterm"></a><div class="para">
+ To have standard PAM-enabled applications use LDAP for authentication, run the <span class="application"><strong>Authentication Configuration Tool</strong></span> (<code class="command">system-config-authentication</code>) and select <span class="guilabel"><strong>Enable LDAP Support</strong></span> under the the <span class="guilabel"><strong>Authentication</strong></span> tab. For more information about configuring PAM, refer to the <em class="citetitle">Pluggable Authentication Modules (PAM)</em> chapter of the Fedora 13 <em class="citetitle">Security Guide</em> and the PAM man pages.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ldap-quickstart.html"><strong>Prev</strong>14.6. OpenLDAP Setup Overview</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ldap-migrate.html"><strong>Next</strong>14.7.2. Migrating Old Authentication Information ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-quickstart.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-quickstart.html
new file mode 100644
index 0000000..c5820c4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-quickstart.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>14.6. OpenLDAP Setup Overview</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" /><link rel="prev" href="s1-ldap-files-schemas.html" title="14.5. The /etc/openldap/schema/ Directory" /><link rel="next" href="s1-ldap-pam.html" title="14.7. Configuring a System to Authenticate Using OpenLDAP" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cla
ss="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-files-schemas.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ldap-pam.html"><strong>Next</strong></a></li></ul><div class="section" title="14.6. OpenLDAP Setup Overview" id="s1-ldap-quickstart"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-quickstart">14.6. OpenLDAP Setup Overview</h2></div></div></div><a id="id946139" class="indexterm"></a><div class="para">
+ This section provides a quick overview for installing and configuring an OpenLDAP directory. For more details, refer to the following URLs:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.openldap.org/doc/admin/quickstart.html">http://www.openldap.org/doc/admin/quickstart.html</a> — The <em class="citetitle">Quick-Start Guide</em> on the OpenLDAP website.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.tldp.org/HOWTO/LDAP-HOWTO/index.html">http://www.tldp.org/HOWTO/LDAP-HOWTO/index.html</a> — The <em class="citetitle">LDAP Linux HOWTO</em> from the Linux Documentation Project.
+ </div></li></ul></div><div class="para">
+ The basic steps for creating an LDAP server are as follows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Install the <code class="filename">openldap</code>, <code class="filename">openldap-servers</code>, and <code class="filename">openldap-clients</code> RPMs.
+ </div></li><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/openldap/slapd.conf</code> file to specify the LDAP domain and server. Refer to <a class="xref" href="s1-ldap-quickstart.html#s2-ldap-files-slapd-conf" title="14.6.1. Editing /etc/openldap/slapd.conf">Section 14.6.1, “Editing <code class="filename">/etc/openldap/slapd.conf</code> ”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ Start <code class="command">slapd</code> with the command:
+ </div><pre class="screen">/sbin/service ldap start</pre><div class="para">
+ After configuring LDAP, use <code class="command">chkconfig</code>, <code class="command">/usr/sbin/ntsysv</code>, or the <span class="application"><strong>Services Configuration Tool</strong></span> to configure LDAP to start at boot time. For more information about configuring services, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a>.
+ </div></li><li class="listitem"><div class="para">
+ Add entries to an LDAP directory with <code class="command">ldapadd</code>.
+ </div></li><li class="listitem"><div class="para">
+ Use <code class="command">ldapsearch</code> to determine if <code class="command">slapd</code> is accessing the information correctly.
+ </div></li><li class="listitem"><div class="para">
+ At this point, the LDAP directory should be functioning properly and can be configured with LDAP-enabled applications.
+ </div></li></ol></div><div class="section" title="14.6.1. Editing /etc/openldap/slapd.conf" id="s2-ldap-files-slapd-conf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-files-slapd-conf">14.6.1. Editing <code class="filename">/etc/openldap/slapd.conf</code> </h3></div></div></div><a id="id995070" class="indexterm"></a><div class="para">
+ To use the <code class="command">slapd</code> LDAP server, modify its configuration file, <code class="filename">/etc/openldap/slapd.conf</code>, to specify the correct domain and server.
+ </div><div class="para">
+ The <code class="command">suffix</code> line names the domain for which the LDAP server provides information and should be changed from:
+ </div><pre class="screen">suffix "dc=your-domain,dc=com"</pre><div class="para">
+ Edit it accordingly so that it reflects a fully qualified domain name. For example:
+ </div><pre class="screen">suffix "dc=example,dc=com"</pre><div class="para">
+ The <code class="command">rootdn</code> entry is the Distinguished Name (DN) for a user who is unrestricted by access controls or administrative limit parameters set for operations on the LDAP directory. The <code class="command">rootdn</code> user can be thought of as the root user for the LDAP directory. In the configuration file, change the <code class="command">rootdn</code> line from its default value as in the following example:
+ </div><pre class="screen">rootdn "cn=root,dc=example,dc=com"</pre><div class="para">
+ When populating an LDAP directory over a network, change the <code class="command">rootpw</code> line — replacing the default value with an encrypted password string. To create an encrypted password string, type the following command:
+ </div><pre class="screen">slappasswd</pre><div class="para">
+ When prompted, type and then re-type a password. The program prints the resulting encrypted password to the shell prompt.
+ </div><div class="para">
+ Next, copy the newly created encrypted password into the <code class="filename">/etc/openldap/slapd.conf</code> on one of the <code class="command">rootpw</code> lines and remove the hash mark (<code class="command">#</code>).
+ </div><div class="para">
+ When finished, the line should look similar to the following example:
+ </div><pre class="screen">rootpw {SSHA}vv2y+i6V6esazrIv70xSSnNAJE18bb2u</pre><div class="warning"><h2>Warning</h2><div class="para">
+ LDAP passwords, including the <code class="command">rootpw</code> directive specified in <code class="filename">/etc/openldap/slapd.conf</code>, are sent over the network <span class="emphasis"><em>unencrypted</em></span>, unless TLS encryption is enabled.
+ </div><div class="para">
+ To enable TLS encryption, review the comments in <code class="filename">/etc/openldap/slapd.conf</code> and refer to the man page for <code class="filename">slapd.conf</code>.
+ </div></div><div class="para">
+ For added security, the <code class="command">rootpw</code> directive should be commented out after populating the LDAP directory by preceding it with a hash mark (<code class="command">#</code>).
+ </div><div class="para">
+ When using the <code class="command">/usr/sbin/slapadd</code> command line tool locally to populate the LDAP directory, use of the <code class="command">rootpw</code> directive is not necessary.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Only the root user can use <code class="command">/usr/sbin/slapadd</code>. However, the directory server runs as the <code class="filename">ldap</code> user. Therefore, the directory server is unable to modify any files created by <code class="command">slapadd</code>. To correct this issue, after using <code class="command">slapadd</code>, type the following command:
+ </div><pre class="screen">chown -R ldap /var/lib/ldap</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ldap-files-schemas.html"><strong>Prev</strong>14.5. The /etc/openldap/schema/ 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-ldap-pam.html"><strong>Next</strong>14.7. Configuring a System to Authenticate Using ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-terminology.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-terminology.html
new file mode 100644
index 0000000..a711e0b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ldap-terminology.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>14.2. LDAP Terminology</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" /><link rel="prev" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" /><link rel="next" href="s1-ldap-daemonsutils.html" title="14.3. OpenLDAP Daemons and Utilities" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><ifr
ame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Lightweight_Directory_Access_Protocol_LDAP.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ldap-daemonsutils.html"><strong>Next</strong></a></li></ul><div class="section" title="14.2. LDAP Terminology" id="s1-ldap-terminology"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ldap-terminology">14.2. LDAP Terminology</h2></div></div></div><a id="id862284" class="indexterm"></a><a id="id862298" class="indexterm"></a><d
iv class="para">
+ Any discussion of LDAP requires a basic understanding of a set of LDAP-specific terms:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="firstterm">entry</em> — A single unit within an LDAP directory. Each entry is identified by its unique <em class="firstterm">Distinguished Name (DN)</em>.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">attributes</em> — Information directly associated with an entry. For example, an organization could be represented as an LDAP entry. Attributes associated with the organization might include a fax number, an address, and so on. People can also be represented as entries in an LDAP directory, with common attributes such as the person's telephone number and email address.
+ </div><div class="para">
+ Some attributes are required, while other attributes are optional. An <em class="firstterm">objectclass</em> definition sets which attributes are required for each entry. Objectclass definitions are found in various schema files, located in the <code class="filename">/etc/openldap/schema/</code> directory. For more information, refer to <a class="xref" href="s1-ldap-files-schemas.html" title="14.5. The /etc/openldap/schema/ Directory">Section 14.5, “The <code class="filename">/etc/openldap/schema/</code> Directory”</a>.
+ </div><div class="para">
+ The assertion of an attribute and its corresponding value is also referred to as a <em class="firstterm">Relative Distinguished Name</em> (RDN). An RDN is only unique per entry, whereas a DN is globally unique.
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">LDIF</em> — The <em class="firstterm">LDAP Data Interchange Format</em> (LDIF) is an ASCII text representation of LDAP entries. Files used for importing data to LDAP servers must be in LDIF format. An LDIF entry looks similar to the following example:
+ </div><pre class="screen">
+[<<em class="replaceable"><code>id</code></em>>] dn: <<em class="replaceable"><code>distinguished name</code></em>>
+<<em class="replaceable"><code>attrtype</code></em>>: <<em class="replaceable"><code>attrvalue</code></em>>
+<<em class="replaceable"><code>attrtype</code></em>>: <<em class="replaceable"><code>attrvalue</code></em>>
+<<em class="replaceable"><code>attrtype</code></em>>: <<em class="replaceable"><code>attrvalue</code></em>>
+</pre><div class="para">
+ Each entry can contain as many <code class="command"><<em class="replaceable"><code>attrtype</code></em>>: <<em class="replaceable"><code>attrvalue</code></em>></code> pairs as needed. A blank line indicates the end of an entry.
+ </div><div class="warning"><h2>Caution</h2><div class="para">
+ All <code class="command"><<em class="replaceable"><code>attrtype</code></em>></code> and <code class="command"><<em class="replaceable"><code>attrvalue</code></em>></code> pairs <span class="emphasis"><em>must</em></span> be defined in a corresponding schema file to use this information.
+ </div></div><div class="para">
+ Any value enclosed within a <code class="command"><</code> and a <code class="command">></code> is a variable and can be set whenever a new LDAP entry is created. This rule does not apply, however, to <code class="command"><<em class="replaceable"><code>id</code></em>></code>. The <code class="command"><<em class="replaceable"><code>id</code></em>></code> is a number determined by the application used to edit the entry.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html"><strong>Prev</strong>Chapter 14. Lightweight Directory Access Protocol...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ldap-daemonsutils.html"><strong>Next</strong>14.3. OpenLDAP Daemons and Utilities</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-logfiles-adding.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-logfiles-adding.html
new file mode 100644
index 0000000..b6b9a75
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-logfiles-adding.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>25.3. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Log_Files.html" title="Chapter 25. Log Files" /><link rel="prev" href="s1-logfiles-viewing.html" title="25.2. Viewing Log Files" /><link rel="next" href="s1-logfiles-examining.html" title="25.4. Monitoring Log Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</i
frame></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-logfiles-examining.html"><strong>Next</strong></a></li></ul><div class="section" title="25.3. 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">25.3. 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="guimenu"><strong>Open Log</strong></span> window where you can select the directory and filename of the log file you wish to view.The figure below illustrates the <span class="guimenu"><strong>Open Log</strong></span> window.
+ </div><div class="figure" title="Figure 25.4. Adding a Log File" id="fig-redhat-logviewer-add"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-add.png" width="444" alt="Adding a Log File" /><div class="longdesc"><div class="para">
+ Adding a Log File
+ </div></div></div></div><h6>Figure 25.4. 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 the contents.
+ </div><div class="para">
+ Please also note that the System Log Viewer also allows you to open zipped logs whose filenames end in ".gz".
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-viewing.html"><strong>Prev</strong>25.2. 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>25.4. Monitoring Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-logfiles-examining.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-logfiles-examining.html
new file mode 100644
index 0000000..34fb971
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-logfiles-examining.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>25.4. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Log_Files.html" title="Chapter 25. Log Files" /><link rel="prev" href="s1-logfiles-adding.html" title="25.3. Adding a Log File" /><link rel="next" href="pt-system-monitoring.html" title="Part IV. System Monitoring" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.<
/iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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" href="pt-system-monitoring.html"><strong>Next</strong></a></li></ul><div class="section" title="25.4. Monitoring Log Files" id="s1-logfiles-examining"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-examining">25.4. Monitoring Log Files</h2></div></div></div><a id="id974504" class="indexterm"></a><a id="id974518" class="indexterm"></a><div class="para">
+ <span class="application"><strong>System Log 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 and after five seconds are displayed in normal format. This is illustrated in the figures below. The figure below illustrates a new alert in the <span class="guimenuitem"><strong>messages</strong></span> log file. The log file is listed in bold text.
+ </div><div class="figure" title="Figure 25.5. Log File Alert" id="fig-redhat-logviewer-monitoring1"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-monitoring1.png" width="444" alt="Log File Alert" /><div class="longdesc"><div class="para">
+ Log File Alert
+ </div></div></div></div><h6>Figure 25.5. Log File Alert</h6></div><br class="figure-break" /><div class="para">
+ Clicking on the <span class="guimenuitem"><strong>messages</strong></span> log file displays the logs in the file with the new lines in bold as illustrated below.
+ </div><div class="figure" title="Figure 25.6. Log file contents" id="fig-redhat-logviewer-monitoring2"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-monitoring2.png" width="444" alt="Log file contents" /><div class="longdesc"><div class="para">
+ Log file contents
+ </div></div></div></div><h6>Figure 25.6. Log file contents</h6></div><br class="figure-break" /><div class="para">
+ The new lines are displayed in bold for five seconds after which they are displayed in normal font.
+ </div><div class="figure" title="Figure 25.7. Log file contents after five seconds" id="fig-redhat-logviewer-monitoring3"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-monitoring3.png" width="444" alt="Log file contents after five seconds" /><div class="longdesc"><div class="para">
+ Log file contents after five seconds
+ </div></div></div></div><h6>Figure 25.7. Log file contents after five seconds</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-adding.html"><strong>Prev</strong>25.3. 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="pt-system-monitoring.html"><strong>Next</strong>Part IV. System Monitoring</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-logfiles-viewing.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-logfiles-viewing.html
new file mode 100644
index 0000000..bd4e33e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-logfiles-viewing.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>25.2. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Log_Files.html" title="Chapter 25. Log Files" /><link rel="prev" href="ch-Log_Files.html" title="Chapter 25. Log Files" /><link rel="next" href="s1-logfiles-adding.html" title="25.3. Adding a Log File" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-adding.html"><strong>Next</strong></a></li></ul><div class="section" title="25.2. Viewing Log Files" id="s1-logfiles-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-viewing">25.2. Viewing Log Files</h2></div></div></div><a id="id982587" 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="id982613" class="indexterm"></a><div class="para">
+ To view system log files in an interactive, real-time application, use the <span class="application"><strong>System Log Viewer</strong></span>. To start the application, go to <span class="guimenu"><strong>Applications</strong></span> (the main menu on the panel) > <span class="guimenuitem"><strong>System</strong></span> > <span class="guimenuitem"><strong>System Logs</strong></span>, or type the command <code class="command">gnome-system-log</code> at a shell prompt.
+ </div><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 25.1. System Log Viewer">Figure 25.1, “ <span class="application">System Log Viewer</span> ”</a>.
+ </div><a id="id598769" class="indexterm"></a><a id="id598787" class="indexterm"></a><div class="figure" title="Figure 25.1. System Log Viewer" id="fig-redhat-logviewer"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer.png" width="444" alt="System Log Viewer" /><div class="longdesc"><div class="para">
+ System Log Viewer
+ </div></div></div></div><h6>Figure 25.1. <span class="application">System Log Viewer</span> </h6></div><br class="figure-break" /><a id="id837458" class="indexterm"></a><div class="para">
+ To filter the contents of the selected log file, click on <span class="guimenuitem"><strong>View</strong></span> from the menu and select <span class="guimenuitem"><strong>Filter</strong></span> as illustrated below.
+ </div><div class="figure" title="Figure 25.2. System Log Viewer - View Menu" id="fig-redhat-logviewer-prefs"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-prefs.png" width="444" alt="System Log Viewer - View Menu" /><div class="longdesc"><div class="para">
+ System Log Viewer - View Menu
+ </div></div></div></div><h6>Figure 25.2. <span class="application">System Log Viewer - View Menu</span> </h6></div><br class="figure-break" /><a id="id837526" class="indexterm"></a><div class="para">
+ Selecting the <span class="guilabel"><strong>Filter</strong></span> menu item will display the <span class="guilabel"><strong>Filter</strong></span> text field where you can type the keywords you wish to use for your filter. To clear your filter click on the <span class="guibutton"><strong>Clear</strong></span> button.The figure below illustrates a sample filter.
+ </div><div class="figure" title="Figure 25.3. System Log Viewer - Filter" id="fig-redhat-logviewer-sample"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-sample.png" width="444" alt="System Log Viewer - Filter" /><div class="longdesc"><div class="para">
+ System Log Viewer - Filter
+ </div></div></div></div><h6>Figure 25.3. <span class="application">System Log Viewer - Filter</span> </h6></div><br class="figure-break" /><a id="id952178" class="indexterm"></a></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Log_Files.html"><strong>Prev</strong>Chapter 25. 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>25.3. Adding a Log File</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-modules-ethernet.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-modules-ethernet.html
new file mode 100644
index 0000000..3d58c63
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-modules-ethernet.html
@@ -0,0 +1,386 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>30.5. Ethernet 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-General_Parameters_and_Modules.html" title="Chapter 30. General Parameters and Modules" /><link rel="prev" href="s1-modules-scsi.html" title="30.4. Storage parameters" /><link rel="next" href="s2-modules-bonding.html" title="30.5.2. The Channel Bonding Module" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upg
rade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-modules-scsi.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-modules-bonding.html"><strong>Next</strong></a></li></ul><div class="section" title="30.5. Ethernet Parameters" id="s1-modules-ethernet"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-modules-ethernet">30.5. Ethernet Parameters</h2></div></div></div><a id="id659590" class="indexterm"></a><a id="id659602" class="indexterm"></a><a id="id659614" class="indexterm"></a><a id="id659626" class="indexterm"></a><div class="para">
+ Most modern Ethernet-based network interface cards (NICs), do not require module parameters to alter settings. Instead, they can be configured using <code class="command">ethtool</code> or <code class="command">mii-tool</code>. Only after these tools fail to work should module parameters be adjusted. Module paramaters can be viewed using the <code class="command">modinfo</code> command.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ For information about using these tools, consult the man pages for <code class="command">ethtool</code>, <code class="command">mii-tool</code>, and <code class="command">modinfo</code>.
+ </div></div><div class="table" title="Table 30.2. Ethernet Module Parameters" id="tb-modules-ethernet"><div class="table-contents"><table summary="Ethernet Module Parameters" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th>
+ Hardware
+ </th><th>
+ Module
+ </th><th>
+ Parameters
+ </th></tr></thead><tbody><tr><td>
+ 3Com EtherLink PCI III/XL Vortex (3c590, 3c592, 3c595, 3c597) Boomerang (3c900, 3c905, 3c595)
+ </td><td>
+ <code class="filename">3c59x.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — 3c59x debug level (0-6)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>options</code></em> — 3c59x: Bits 0-3: media type, bit 4: bus mastering, bit 9: full duplex
+ </div>
+ <div class="para">
+ <em class="parameter"><code>global_options</code></em> — 3c59x: same as options, but applies to all NICs if options is unset
+ </div>
+ <div class="para">
+ <em class="parameter"><code>full_duplex</code></em> — 3c59x full duplex setting(s) (1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>global_full_duplex</code></em> — 3c59x: same as full_duplex, but applies to all NICs if full_duplex is unset
+ </div>
+ <div class="para">
+ <em class="parameter"><code>hw_checksums</code></em> — 3c59x Hardware checksum checking by adapter(s) (0-1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>flow_ctrl</code></em> — 3c59x 802.3x flow control usage (PAUSE only) (0-1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>enable_wol</code></em> — 3c59x: Turn on Wake-on-LAN for adapter(s) (0-1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>global_enable_wol</code></em> — 3c59x: same as enable_wol, but applies to all NICs if enable_wol is unset
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — 3c59x copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>max_interrupt_work</code></em> — 3c59x maximum events handled per interrupt
+ </div>
+ <div class="para">
+ <em class="parameter"><code>compaq_ioaddr</code></em> — 3c59x PCI I/O base address (Compaq BIOS problem workaround)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>compaq_irq</code></em> — 3c59x PCI IRQ number (Compaq BIOS problem workaround)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>compaq_device_id</code></em> — 3c59x PCI device ID (Compaq BIOS problem workaround)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>watchdog</code></em> — 3c59x transmit timeout in milliseconds
+ </div>
+ <div class="para">
+ <em class="parameter"><code>global_use_mmio</code></em> — 3c59x: same as use_mmio, but applies to all NICs if options is unset
+ </div>
+ <div class="para">
+ <em class="parameter"><code>use_mmio</code></em> — 3c59x: use memory-mapped PCI I/O resource (0-1)
+ </div>
+
+ </td></tr><tr><td>
+ RTL8139, SMC EZ Card Fast Ethernet, RealTek cards using RTL8129, or RTL8139 Fast Ethernet chipsets
+ </td><td>
+ <code class="filename">8139too.ko</code>
+ </td><td>
+ </td></tr><tr><td>
+ Broadcom 4400 10/100 PCI ethernet driver
+ </td><td>
+ <code class="filename">b44.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>b44_debug</code></em> — B44 bitmapped debugging message enable value
+ </div>
+
+ </td></tr><tr><td>
+ Broadcom NetXtreme II BCM5706/5708 Driver
+ </td><td>
+ <code class="filename">bnx2.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>disable_msi</code></em> — Disable Message Signaled Interrupt (MSI)
+ </div>
+
+ </td></tr><tr><td>
+ Intel Ether Express/100 driver
+ </td><td>
+ <code class="filename">e100.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — Debug level (0=none,...,16=all)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>eeprom_bad_csum_allow</code></em> — Allow bad eeprom checksums
+ </div>
+
+ </td></tr><tr><td>
+ Intel EtherExpress/1000 Gigabit
+ </td><td>
+ <code class="filename">e1000.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>TxDescriptors</code></em> — Number of transmit descriptors
+ </div>
+ <div class="para">
+ <em class="parameter"><code>RxDescriptors</code></em> — Number of receive descriptors
+ </div>
+ <div class="para">
+ <em class="parameter"><code>Speed</code></em> — Speed setting
+ </div>
+ <div class="para">
+ <em class="parameter"><code>Duplex</code></em> — Duplex setting
+ </div>
+ <div class="para">
+ <em class="parameter"><code>AutoNeg</code></em> — Advertised auto-negotiation setting
+ </div>
+ <div class="para">
+ <em class="parameter"><code>FlowControl</code></em> — Flow Control setting
+ </div>
+ <div class="para">
+ <em class="parameter"><code>XsumRX</code></em> — Disable or enable Receive Checksum offload
+ </div>
+ <div class="para">
+ <em class="parameter"><code>TxIntDelay</code></em> — Transmit Interrupt Delay
+ </div>
+ <div class="para">
+ <em class="parameter"><code>TxAbsIntDelay</code></em> — Transmit Absolute Interrupt Delay
+ </div>
+ <div class="para">
+ <em class="parameter"><code>RxIntDelay</code></em> — Receive Interrupt Delay
+ </div>
+ <div class="para">
+ <em class="parameter"><code>RxAbsIntDelay</code></em> — Receive Absolute Interrupt Delay
+ </div>
+ <div class="para">
+ <em class="parameter"><code>InterruptThrottleRate</code></em> — Interrupt Throttling Rate
+ </div>
+ <div class="para">
+ <em class="parameter"><code>SmartPowerDownEnable</code></em> — Enable PHY smart power down
+ </div>
+ <div class="para">
+ <em class="parameter"><code>KumeranLockLoss</code></em> — Enable Kumeran lock loss workaround
+ </div>
+
+ </td></tr><tr><td>
+ Myricom 10G driver (10GbE)
+ </td><td>
+ <code class="filename">myri10ge.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_fw_name</code></em> — Firmware image name
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_ecrc_enable</code></em> — Enable Extended CRC on PCI-E
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_max_intr_slots</code></em> — Interrupt queue slots
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_small_bytes</code></em> — Threshold of small packets
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_msi</code></em> — Enable Message Signalled Interrupts
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_intr_coal_delay</code></em> — Interrupt coalescing delay
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_flow_control</code></em> — Pause parameter
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_deassert_wait</code></em> — Wait when deasserting legacy interrupts
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_force_firmware</code></em> — Force firmware to assume aligned completions
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_skb_cross_4k</code></em> — Can a small skb cross a 4KB boundary?
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_initial_mtu</code></em> — Initial MTU
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_napi_weight</code></em> — Set NAPI weight
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_watchdog_timeout</code></em> — Set watchdog timeout
+ </div>
+ <div class="para">
+ <em class="parameter"><code>myri10ge_max_irq_loops</code></em> — Set stuck legacy IRQ detection threshold
+ </div>
+
+ </td></tr><tr><td>
+ NatSemi DP83815 Fast Ethernet
+ </td><td>
+ <code class="filename">natsemi.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>mtu</code></em> — DP8381x MTU (all boards)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — DP8381x default debug level
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — DP8381x copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>options</code></em> — DP8381x: Bits 0-3: media type, bit 17: full duplex
+ </div>
+ <div class="para">
+ <em class="parameter"><code>full_duplex</code></em> — DP8381x full duplex setting(s) (1)
+ </div>
+
+ </td></tr><tr><td>
+ AMD PCnet32 and AMD PCnetPCI
+ </td><td>
+ <code class="filename">pcnet32.ko</code>
+ </td><td>
+ </td></tr><tr><td>
+ PCnet32 and PCnetPCI
+ </td><td>
+ <code class="filename">pcnet32.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — pcnet32 debug level
+ </div>
+ <div class="para">
+ <em class="parameter"><code>max_interrupt_work</code></em> — pcnet32 maximum events handled per interrupt
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — pcnet32 copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>tx_start_pt</code></em> — pcnet32 transmit start point (0-3)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>pcnet32vlb</code></em> — pcnet32 Vesa local bus (VLB) support (0/1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>options</code></em> — pcnet32 initial option setting(s) (0-15)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>full_duplex</code></em> — pcnet32 full duplex setting(s) (1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>homepna</code></em> — pcnet32 mode for 79C978 cards (1 for HomePNA, 0 for Ethernet, default Ethernet
+ </div>
+
+ </td></tr><tr><td>
+ RealTek RTL-8169 Gigabit Ethernet driver
+ </td><td>
+ <code class="filename">r8169.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>media</code></em> — force phy operation. Deprecated by ethtool (8).
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — Copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>use_dac</code></em> — Enable PCI DAC. Unsafe on 32 bit PCI slot.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — Debug verbosity level (0=none, ..., 16=all)
+ </div>
+
+ </td></tr><tr><td>
+ Neterion Xframe 10GbE Server Adapter
+ </td><td>
+ <code class="filename">s2io.ko</code>
+ </td><td>
+ </td></tr><tr><td>
+ SIS 900/701G PCI Fast Ethernet
+ </td><td>
+ <code class="filename">sis900.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>multicast_filter_limit</code></em> — SiS 900/7016 maximum number of filtered multicast addresses
+ </div>
+ <div class="para">
+ <em class="parameter"><code>max_interrupt_work</code></em> — SiS 900/7016 maximum events handled per interrupt
+ </div>
+ <div class="para">
+ <em class="parameter"><code>sis900_debug</code></em> — SiS 900/7016 bitmapped debugging message level
+ </div>
+
+ </td></tr><tr><td>
+ Adaptec Starfire Ethernet driver
+ </td><td>
+ <code class="filename">starfire.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>max_interrupt_work</code></em> — Maximum events handled per interrupt
+ </div>
+ <div class="para">
+ <em class="parameter"><code>mtu</code></em> — MTU (all boards)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — Debug level (0-6)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — Copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>intr_latency</code></em> — Maximum interrupt latency, in microseconds
+ </div>
+ <div class="para">
+ <em class="parameter"><code>small_frames</code></em> — Maximum size of receive frames that bypass interrupt latency (0,64,128,256,512)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>options</code></em> — Deprecated: Bits 0-3: media type, bit 17: full duplex
+ </div>
+ <div class="para">
+ <em class="parameter"><code>full_duplex</code></em> — Deprecated: Forced full-duplex setting (0/1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>enable_hw_cksum</code></em> — Enable/disable hardware cksum support (0/1)
+ </div>
+
+ </td></tr><tr><td>
+ Broadcom Tigon3
+ </td><td>
+ <code class="filename">tg3.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>tg3_debug</code></em> — Tigon3 bitmapped debugging message enable value
+ </div>
+
+ </td></tr><tr><td>
+ ThunderLAN PCI
+ </td><td>
+ <code class="filename">tlan.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>aui</code></em> — ThunderLAN use AUI port(s) (0-1)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>duplex</code></em> — ThunderLAN duplex setting(s) (0-default, 1-half, 2-full)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>speed</code></em> — ThunderLAN port speen setting(s) (0,10,100)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — ThunderLAN debug mask
+ </div>
+ <div class="para">
+ <em class="parameter"><code>bbuf</code></em> — ThunderLAN use big buffer (0-1)
+ </div>
+
+ </td></tr><tr><td>
+ Digital 21x4x Tulip PCI Ethernet cards SMC EtherPower 10 PCI(8432T/8432BT) SMC EtherPower 10/100 PCI(9332DST) DEC EtherWorks 100/10 PCI(DE500-XA) DEC EtherWorks 10 PCI(DE450) DEC QSILVER's, Znyx 312 etherarray Allied Telesis LA100PCI-T Danpex EN-9400, Cogent EM110
+ </td><td>
+ <code class="filename">tulip.ko</code>
+ </td><td>
+ <em class="parameter"><code>io</code></em> <em class="replaceable"><code>io_port</code></em>
+ </td></tr><tr><td>
+ VIA Rhine PCI Fast Ethernet cards with either the VIA VT86c100A Rhine-II PCI or 3043 Rhine-I D-Link DFE-930-TX PCI 10/100
+ </td><td>
+ <code class="filename">via-rhine.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>max_interrupt_work</code></em> — VIA Rhine maximum events handled per interrupt
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — VIA Rhine debug level (0-7)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>rx_copybreak</code></em> — VIA Rhine copy breakpoint for copy-only-tiny-frames
+ </div>
+ <div class="para">
+ <em class="parameter"><code>avoid_D3</code></em> — Avoid power state D3 (work-around for broken BIOSes)
+ </div>
+
+ </td></tr></tbody></table></div><h6>Table 30.2. Ethernet Module Parameters</h6></div><br class="table-break" /><div class="section" title="30.5.1. Using Multiple Ethernet Cards" id="s2-modules-multiple-eth"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-modules-multiple-eth">30.5.1. Using Multiple Ethernet Cards</h3></div></div></div><a id="id573223" class="indexterm"></a><a id="id573238" 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="s1-modules-scsi.html"><strong>Prev</strong>30.4. Storage 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="s2-modules-bonding.html"><strong>Next</strong>30.5.2. The Channel Bonding Module</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-modules-parameters-specifying.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-modules-parameters-specifying.html
new file mode 100644
index 0000000..5921644
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-modules-parameters-specifying.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>30.3. Specifying 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-General_Parameters_and_Modules.html" title="Chapter 30. General Parameters and Modules" /><link rel="prev" href="s1-kernel-modules-persistant.html" title="30.2. Persistent Module Loading" /><link rel="next" href="s1-modules-scsi.html" title="30.4. Storage parameters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe
, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-persistant.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-modules-scsi.html"><strong>Next</strong></a></li></ul><div class="section" title="30.3. Specifying Module Parameters" id="s1-modules-parameters-specifying"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-modules-parameters-specifying">30.3. Specifying Module Parameters</h2></div></div></div><a id="id612535" class="indexterm"></a><a id="id612551" class="indexterm"></a><div class="para">
+ In some situations, it may be necessary to supply parameters to a module
+ <a id="id612565" class="indexterm"></a>
+ as it is loaded for it to function properly.
+ </div><div class="para">
+ For instance, to enable full duplex at 100Mbps connection speed for an Intel Ether Express/100 card, load the <code class="filename">e100</code> driver with the <code class="option">e100_speed_duplex=4</code> option.
+ </div><div class="important"><h2>Important: kernel module parameters separated by commas</h2><div class="para">
+ When a module parameter has values separated by commas, do <span class="emphasis"><em>not</em></span> use spaces after the commas to separate the values.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-modules-persistant.html"><strong>Prev</strong>30.2. 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="s1-modules-scsi.html"><strong>Next</strong>30.4. Storage parameters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-modules-scsi.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-modules-scsi.html
new file mode 100644
index 0000000..803fa08
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-modules-scsi.html
@@ -0,0 +1,268 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>30.4. Storage 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-General_Parameters_and_Modules.html" title="Chapter 30. General Parameters and Modules" /><link rel="prev" href="s1-modules-parameters-specifying.html" title="30.3. Specifying Module Parameters" /><link rel="next" href="s1-modules-ethernet.html" title="30.5. Ethernet Parameters" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifra
me, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-modules-parameters-specifying.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-modules-ethernet.html"><strong>Next</strong></a></li></ul><div class="section" title="30.4. Storage parameters" id="s1-modules-scsi"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-modules-scsi">30.4. Storage parameters</h2></div></div></div><a id="id913158" class="indexterm"></a><a id="id913170" class="indexterm"></a><div class="table" title="Table 30.1. Storage Module Parameters" id="tb-modules-scsiparame
ters"><div class="table-contents"><table summary="Storage Module Parameters" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th>
+ Hardware
+ </th><th>
+ Module
+ </th><th>
+ Parameters
+ </th></tr></thead><tbody><tr><td>
+ 3ware Storage Controller and 9000 series
+ </td><td>
+ <code class="filename">3w-xxxx.ko, 3w-9xxx.ko</code>
+ </td><td>
+ </td></tr><tr><td>
+ Adaptec Advanced Raid Products, Dell PERC2, 2/Si, 3/Si, 3/Di, HP NetRAID-4M, IBM ServeRAID, and ICP SCSI driver
+ </td><td>
+ <code class="filename">aacraid.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>nondasd</code></em> — Control scanning of hba for nondasd devices. 0=off, 1=on
+ </div>
+ <div class="para">
+ <em class="parameter"><code>dacmode</code></em> — Control whether dma addressing is using 64 bit DAC. 0=off, 1=on
+ </div>
+ <div class="para">
+ <em class="parameter"><code>commit</code></em> — Control whether a COMMIT_CONFIG is issued to the adapter for foreign arrays. This is typically needed in systems that do not have a BIOS. 0=off, 1=on
+ </div>
+ <div class="para">
+ <em class="parameter"><code>startup_timeout</code></em> — The duration of time in seconds to wait for adapter to have it's kernel up and running. This is typically adjusted for large systems that do not have a BIOS
+ </div>
+ <div class="para">
+ <em class="parameter"><code>aif_timeout</code></em> — The duration of time in seconds to wait for applications to pick up AIFs before deregistering them. This is typically adjusted for heavily burdened systems.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>numacb</code></em> — Request a limit to the number of adapter control blocks (FIB) allocated. Valid values are 512 and down. Default is to use suggestion from Firmware.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>acbsize</code></em> — Request a specific adapter control block (FIB) size. Valid values are 512, 2048, 4096 and 8192. Default is to use suggestion from Firmware.
+ </div>
+
+ </td></tr><tr><td>
+ Adaptec 28xx, R9xx, 39xx AHA-284x, AHA-29xx, AHA-394x, AHA-398x, AHA-274x, AHA-274xT, AHA-2842, AHA-2910B, AHA-2920C, AHA-2930/U/U2, AHA-2940/W/U/UW/AU/, U2W/U2/U2B/, U2BOEM, AHA-2944D/WD/UD/UWD, AHA-2950U2/W/B, AHA-3940/U/W/UW/, AUW/U2W/U2B, AHA-3950U2D, AHA-3985/U/W/UW, AIC-777x, AIC-785x, AIC-786x, AIC-787x, AIC-788x , AIC-789x, AIC-3860
+ </td><td>
+ <code class="filename">aic7xxx.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>verbose</code></em> — Enable verbose/diagnostic logging
+ </div>
+ <div class="para">
+ <em class="parameter"><code>allow_memio</code></em> — Allow device registers to be memory mapped
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — Bitmask of debug values to enable
+ </div>
+ <div class="para">
+ <em class="parameter"><code>no_probe</code></em> — Toggle EISA/VLB controller probing
+ </div>
+ <div class="para">
+ <em class="parameter"><code>probe_eisa_vl</code></em> — Toggle EISA/VLB controller probing
+ </div>
+ <div class="para">
+ <em class="parameter"><code>no_reset</code></em> — Supress initial bus resets
+ </div>
+ <div class="para">
+ <em class="parameter"><code>extended</code></em> — Enable extended geometry on all controllers
+ </div>
+ <div class="para">
+ <em class="parameter"><code>periodic_otag</code></em> — Send an ordered tagged transaction periodically to prevent tag starvation. This may be required by some older disk drives or RAID arrays.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>tag_info:<tag_str></code></em> — Set per-target tag depth
+ </div>
+ <div class="para">
+ <em class="parameter"><code>global_tag_depth:<int></code></em> — Global tag depth for every target on every bus
+ </div>
+ <div class="para">
+ <em class="parameter"><code>seltime:<int></code></em> — Selection Timeout (0/256ms,1/128ms,2/64ms,3/32ms)
+ </div>
+
+ </td></tr><tr><td>
+ IBM ServeRAID
+ </td><td>
+ <code class="filename">ips.ko</code>
+ </td><td>
+ </td></tr><tr><td>
+ LSI Logic MegaRAID Mailbox Driver
+ </td><td>
+ <code class="filename">megaraid_mbox.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>unconf_disks</code></em> — Set to expose unconfigured disks to kernel (default=0)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>busy_wait</code></em> — Max wait for mailbox in microseconds if busy (default=10)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>max_sectors</code></em> — Maximum number of sectors per IO command (default=128)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>cmd_per_lun</code></em> — Maximum number of commands per logical unit (default=64)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>fast_load</code></em> — Faster loading of the driver, skips physical devices! (default=0)
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug_level</code></em> — Debug level for driver (default=0)
+ </div>
+
+ </td></tr><tr><td>
+ Emulex LightPulse Fibre Channel SCSI driver
+ </td><td>
+ <code class="filename">lpfc.ko</code>
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>lpfc_poll</code></em> — FCP ring polling mode control: 0 - none, 1 - poll with interrupts enabled 3 - poll and disable FCP ring interrupts
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_log_verbose</code></em> — Verbose logging bit-mask
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_lun_queue_depth</code></em> — Max number of FCP commands we can queue to a specific LUN
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_hba_queue_depth</code></em> — Max number of FCP commands we can queue to a lpfc HBA
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_scan_down</code></em> — Start scanning for devices from highest ALPA to lowest
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_nodev_tmo</code></em> — Seconds driver will hold I/O waiting for a device to come back
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_topology</code></em> — Select Fibre Channel topology
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_link_speed</code></em> — Select link speed
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_fcp_class</code></em> — Select Fibre Channel class of service for FCP sequences
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_use_adisc</code></em> — Use ADISC on rediscovery to authenticate FCP devices
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_ack0</code></em> — Enable ACK0 support
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_cr_delay</code></em> — A count of milliseconds after which an interrupt response is generated
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_cr_count</code></em> — A count of I/O completions after which an interrupt response is generated
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_multi_ring_support</code></em> — Determines number of primary SLI rings to spread IOCB entries across
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_fdmi_on</code></em> — Enable FDMI support
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_discovery_threads</code></em> — Maximum number of ELS commands during discovery
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_max_luns</code></em> — Maximum allowed LUN
+ </div>
+ <div class="para">
+ <em class="parameter"><code>lpfc_poll_tmo</code></em> — Milliseconds driver will wait between polling FCP ring
+ </div>
+
+ </td></tr><tr><td>
+ HP Smart Array
+ </td><td>
+ cciss.ko
+ </td><td>
+ </td></tr><tr><td>
+ LSI Logic MPT Fusion
+ </td><td>
+ mptbase.ko mptctl.ko mptfc.ko mptlan.ko mptsas.ko mptscsih.ko mptspi.ko
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>mpt_msi_enable</code></em> — MSI Support Enable
+ </div>
+ <div class="para">
+ <em class="parameter"><code>mptfc_dev_loss_tmo</code></em> — Initial time the driver programs the transport to wait for an rport to return following a device loss event.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>mpt_pt_clear</code></em> — Clear persistency table
+ </div>
+ <div class="para">
+ <em class="parameter"><code>mpt_saf_te</code></em> — Force enabling SEP Processor
+ </div>
+
+ </td></tr><tr><td>
+ QLogic Fibre Channel Driver
+ </td><td>
+ qla2xxx.ko
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>ql2xlogintimeout</code></em> — Login timeout value in seconds.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>qlport_down_retry</code></em> — Maximum number of command retries to a port that returns a PORT-DOWN status
+ </div>
+ <div class="para">
+ <em class="parameter"><code>ql2xplogiabsentdevice</code></em> — Option to enable PLOGI to devices that are not present after a Fabric scan.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>ql2xloginretrycount</code></em> — Specify an alternate value for the NVRAM login retry count.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>ql2xallocfwdump</code></em> — Option to enable allocation of memory for a firmware dump during HBA initialization. Default is 1 - allocate memory.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>extended_error_logging</code></em> — Option to enable extended error logging.
+ </div>
+ <div class="para">
+ <em class="parameter"><code>ql2xfdmienable</code></em> — Enables FDMI registratons.
+ </div>
+
+ </td></tr><tr><td>
+ NCR, Symbios and LSI 8xx and 1010
+ </td><td>
+ sym53c8xx
+
+ </td><td>
+ <div class="para">
+ <em class="parameter"><code>cmd_per_lun</code></em> — The maximum number of tags to use by default
+ </div>
+ <div class="para">
+ <em class="parameter"><code>tag_ctrl</code></em> — More detailed control over tags per LUN
+ </div>
+ <div class="para">
+ <em class="parameter"><code>burst</code></em> — Maximum burst. 0 to disable, 255 to read from registers
+ </div>
+ <div class="para">
+ <em class="parameter"><code>led</code></em> — Set to 1 to enable LED support
+ </div>
+ <div class="para">
+ <em class="parameter"><code>diff</code></em> — 0 for no differential mode, 1 for BIOS, 2 for always, 3 for not GPIO3
+ </div>
+ <div class="para">
+ <em class="parameter"><code>irqm</code></em> — 0 for open drain, 1 to leave alone, 2 for totem pole
+ </div>
+ <div class="para">
+ <em class="parameter"><code>buschk</code></em> — 0 to not check, 1 for detach on error, 2 for warn on error
+ </div>
+ <div class="para">
+ <em class="parameter"><code>hostid</code></em> — The SCSI ID to use for the host adapters
+ </div>
+ <div class="para">
+ <em class="parameter"><code>verb</code></em> — 0 for minimal verbosity, 1 for normal, 2 for excessive
+ </div>
+ <div class="para">
+ <em class="parameter"><code>debug</code></em> — Set bits to enable debugging
+ </div>
+ <div class="para">
+ <em class="parameter"><code>settle</code></em> — Settle delay in seconds. Default 3
+ </div>
+ <div class="para">
+ <em class="parameter"><code>nvram</code></em> — Option currently not used
+ </div>
+ <div class="para">
+ <em class="parameter"><code>excl</code></em> — List ioport addresses here to prevent controllers from being attached
+ </div>
+ <div class="para">
+ <em class="parameter"><code>safe</code></em> — Set other settings to a "safe mode"
+ </div>
+
+ </td></tr></tbody></table></div><h6>Table 30.1. Storage Module Parameters</h6></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-modules-parameters-specifying.html"><strong>Prev</strong>30.3. Specifying 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="s1-modules-ethernet.html"><strong>Next</strong>30.5. Ethernet Parameters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-control.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-control.html
new file mode 100644
index 0000000..b760426
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-control.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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</strong></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="id887141" class="indexterm"></a><a id="id887163" class="indexterm"></a><a id="id806796" class="indexterm"></a><a id="id806817" c
lass="indexterm"></a><a id="id806831" 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"><h2>Caution</h2><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 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><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><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><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><span class="term"> <code class="filename">ifup-plip</code> </span></dt><dd><div class="para">
+ Brings up a PLIP interface.
+ </div></dd><dt><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><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><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><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><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><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"><h2>Warning</h2><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 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_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-functions.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-functions.html
new file mode 100644
index 0000000..6ce078b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-functions.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgr
ade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id792317" 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_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-interfaces.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-interfaces.html
new file mode 100644
index 0000000..1acfe79
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-interfaces.html
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to v
iew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id991230" class="indexterm"></a><a id="id991244" 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="id665868" class="indexterm"></a><a id="id665886" 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><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><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><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><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><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><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><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"><h2>Note</h2><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></dd><dt><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><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><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><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><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><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><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><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><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><span class="term"> <code class="command">SLAVE=<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 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><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><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_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-resources.html
new file mode 100644
index 0000000..2f0d99d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-resources.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade
your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id724515" 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><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><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_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-static-routes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-static-routes.html
new file mode 100644
index 0000000..0d3aae3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-networkscripts-static-routes.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgra
de your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id933974">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"><h2>Duplicate Default Gateways</h2><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 class="formalpara"><h5 class="formalpara" id="id936336">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_Draft_Documentation/0.1/html/Deployment_Guide/s1-openssh-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-openssh-additional-resources.html
new file mode 100644
index 0000000..3918da6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-openssh-additional-resources.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>8.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 8. OpenSSH" /><link rel="prev" href="s2-ssh-beyondshell-tcpip.html" title="8.4.2. Port Forwarding" /><link rel="next" href="s2-openssh-useful-websites.html" title="8.5.2. Useful Websites" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.<
/iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="s2-openssh-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" title="8.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">8.5. Additional Resources</h2></div></div></div><a id="id807091" class="indexterm"></a><a id="id807103" 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="8.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">8.5.1. Installed Documentation</h3></div></div></div><div class="variablelist"><dl><dt><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><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><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><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><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><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><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>8.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>8.5.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-additional-resources.html
new file mode 100644
index 0000000..09c8760
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-additional-resources.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>27.9. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 27. OProfile" /><link rel="prev" href="s1-oprofile-gui.html" title="27.8. Graphical Interface" /><link rel="next" href="s2-oprofile-useful-websites.html" title="27.9.2. Useful Websites" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.<
/iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-gui.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" title="27.9. Additional Resources" id="s1-oprofile-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-additional-resources">27.9. Additional Resources</h2></div></div></div><a id="id1008442" class="indexterm"></a><div class="para">
+ This chapter only highlights OProfile and how to configure and use it. To learn more, refer to the following resources.
+ </div><div class="section" title="27.9.1. Installed Docs" id="s1-oprofile-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-oprofile-installed-docs">27.9.1. Installed Docs</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/oprofile-<em class="replaceable"><code><version></code></em>/oprofile.html</code> — <em class="citetitle">OProfile Manual</em>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">oprofile</code> man page — Discusses <code class="command">opcontrol</code>, <code class="command">opreport</code>, <code class="command">opannotate</code>, and <code class="command">ophelp</code>
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-gui.html"><strong>Prev</strong>27.8. Graphical 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="s2-oprofile-useful-websites.html"><strong>Next</strong>27.9.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-analyzing-data.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-analyzing-data.html
new file mode 100644
index 0000000..816ec02
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-analyzing-data.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>27.5. Analyzing the Data</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 27. OProfile" /><link rel="prev" href="s1-oprofile-saving-data.html" title="27.4. Saving Data" /><link rel="next" href="s2-oprofile-reading-opreport-single.html" title="27.5.2. Using opreport on a Single Executable" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browse
r or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-saving-data.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-reading-opreport-single.html"><strong>Next</strong></a></li></ul><div class="section" title="27.5. Analyzing the Data" id="s1-oprofile-analyzing-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-analyzing-data">27.5. Analyzing the Data</h2></div></div></div><a id="id770359" class="indexterm"></a><div class="para">
+ Periodically, the OProfile daemon, <code class="command">oprofiled</code>, collects the samples and writes them to the <code class="filename">/var/lib/oprofile/samples/</code> directory. Before reading the data, make sure all data has been written to this directory by executing the following command as root:
+ </div><pre class="screen">
+<code class="command">opcontrol --dump</code>
+</pre><div class="para">
+ Each sample file name is based on the name of the executable. For example, the samples for the default event on a Pentium III processor for <code class="command">/bin/bash</code> becomes:
+ </div><pre class="screen">\{root\}/bin/bash/\{dep\}/\{root\}/bin/bash/CPU_CLK_UNHALTED.100000</pre><div class="para">
+ The following tools are available to profile the sample data once it has been collected:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">opreport</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">opannotate</code>
+ </div></li></ul></div><div class="para">
+ Use these tools, along with the binaries profiled, to generate reports that can be further analyzed.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ The executable being profiled must be used with these tools to analyze the data. If it must change after the data is collected, backup the executable used to create the samples as well as the sample files. Please note that the sample file and the binary have to agree. Making a backup isn't going to work if they do not match. <code class="command">oparchive</code> can be used to address this problem.
+ </div></div><div class="para">
+ Samples for each executable are written to a single sample file. Samples from each dynamically linked library are also written to a single sample file. While OProfile is running, if the executable being monitored changes and a sample file for the executable exists, the existing sample file is automatically deleted. Thus, if the existing sample file is needed, it must be backed up, along with the executable used to create it before replacing the executable with a new version. The oprofile analysis tools use the executable file that created the samples during analysis. If the executable changes the analysis tools will be unable to analyze the associated samples. Refer to <a class="xref" href="s1-oprofile-saving-data.html" title="27.4. Saving Data">Section 27.4, “Saving Data”</a> for details on how to backup the sample file.
+ </div><div class="section" title="27.5.1. Using opreport" id="s2-oprofile-reading-opreport"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-reading-opreport">27.5.1. Using <code class="command">opreport</code> </h3></div></div></div><a id="id877171" class="indexterm"></a><a id="id877189" class="indexterm"></a><div class="para">
+ The <code class="command">opreport</code> tool provides an overview of all the executables being profiled.
+ </div><div class="para">
+ The following is part of a sample output:
+ </div><pre class="screen">
+Profiling through timer interrupt
+TIMER:0|
+samples| %|
+------------------
+25926 97.5212 no-vmlinux
+359 1.3504 pi
+65 0.2445 Xorg
+62 0.2332 libvte.so.4.4.0
+56 0.2106 libc-2.3.4.so
+34 0.1279 libglib-2.0.so.0.400.7
+19 0.0715 libXft.so.2.1.2
+17 0.0639 bash
+8 0.0301 ld-2.3.4.so
+8 0.0301 libgdk-x11-2.0.so.0.400.13
+6 0.0226 libgobject-2.0.so.0.400.7
+5 0.0188 oprofiled
+4 0.0150 libpthread-2.3.4.so
+4 0.0150 libgtk-x11-2.0.so.0.400.13
+3 0.0113 libXrender.so.1.2.2
+3 0.0113 du
+1 0.0038 libcrypto.so.0.9.7a
+1 0.0038 libpam.so.0.77
+1 0.0038 libtermcap.so.2.0.8
+1 0.0038 libX11.so.6.2
+1 0.0038 libgthread-2.0.so.0.400.7
+1 0.0038 libwnck-1.so.4.9.0
+</pre><div class="para">
+ Each executable is listed on its own line. The first column is the number of samples recorded for the executable. The second column is the percentage of samples relative to the total number of samples. The third column is the name of the executable.
+ </div><div class="para">
+ Refer to the <code class="command">opreport</code> man page for a list of available command line options, such as the <code class="option">-r</code> option used to sort the output from the executable with the smallest number of samples to the one with the largest number of samples.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-saving-data.html"><strong>Prev</strong>27.4. Saving Data</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-reading-opreport-single.html"><strong>Next</strong>27.5.2. Using opreport on a Single Executable</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-configuring.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-configuring.html
new file mode 100644
index 0000000..3193b93
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-configuring.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>27.2. Configuring OProfile</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 27. OProfile" /><link rel="prev" href="ch-OProfile.html" title="Chapter 27. OProfile" /><link rel="next" href="s2-oprofile-events.html" title="27.2.2. Setting Events to Monitor" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe
></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-OProfile.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-events.html"><strong>Next</strong></a></li></ul><div class="section" title="27.2. Configuring OProfile" id="s1-oprofile-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-configuring">27.2. Configuring OProfile</h2></div></div></div><a id="id768394" class="indexterm"></a><a id="id768408" class="indexterm"></a><a id="id768425" class="indexterm"></a><div class="para">
+ Before OProfile can be run, it must be configured. At a minimum, selecting to monitor the kernel (or selecting not to monitor the kernel) is required. The following sections describe how to use the <code class="command">opcontrol</code> utility to configure OProfile. As the <code class="command">opcontrol</code> commands are executed, the setup options are saved to the <code class="filename">/root/.oprofile/daemonrc</code> file.
+ </div><div class="section" title="27.2.1. Specifying the Kernel" id="s2-oprofile-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-kernel">27.2.1. Specifying the Kernel</h3></div></div></div><a id="id768469" class="indexterm"></a><div class="para">
+ First, configure whether OProfile should monitor the kernel. This is the only configuration option that is required before starting OProfile. All others are optional.
+ </div><div class="para">
+ To monitor the kernel, execute the following command as root:
+ </div><a id="id747365" class="indexterm"></a><pre class="screen">
+<code class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux</code>
+</pre><div class="note"><h2>Note</h2><div class="para">
+ The <code class="command">debuginfo</code> package must be installed (which contains the uncompressed kernel) in order to monitor the kernel.
+ </div></div><div class="para">
+ To configure OProfile not to monitor the kernel, execute the following command as root:
+ </div><a id="id747421" class="indexterm"></a><pre class="screen">
+<code class="command">opcontrol --setup --no-vmlinux</code>
+</pre><div class="para">
+ This command also loads the <code class="computeroutput">oprofile</code> kernel module, if it is not already loaded, and creates the <code class="filename">/dev/oprofile/</code> directory, if it does not already exist. Refer to <a class="xref" href="s1-oprofile-dev-oprofile.html" title="27.6. Understanding /dev/oprofile/">Section 27.6, “Understanding <code class="filename">/dev/oprofile/</code> ”</a> for details about this directory.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ Even if OProfile is configured not to profile the kernel, the SMP kernel still must be running so that the <code class="command">oprofile</code> module can be loaded from it.
+ </div></div><div class="para">
+ Setting whether samples should be collected within the kernel only changes what data is collected, not how or where the collected data is stored. To generate different sample files for the kernel and application libraries, refer to <a class="xref" href="s2-oprofile-starting-separate.html" title="27.2.3. Separating Kernel and User-space Profiles">Section 27.2.3, “Separating Kernel and User-space Profiles”</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-OProfile.html"><strong>Prev</strong>Chapter 27. OProfile</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-events.html"><strong>Next</strong>27.2.2. Setting Events to Monitor</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-dev-oprofile.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-dev-oprofile.html
new file mode 100644
index 0000000..13209d4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-dev-oprofile.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>27.6. Understanding /dev/oprofile/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 27. OProfile" /><link rel="prev" href="s2-oprofile-reading-opannotate.html" title="27.5.4. Using opannotate" /><link rel="next" href="s1-oprofile-example-usage.html" title="27.7. Example Usage" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable
iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-reading-opannotate.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-example-usage.html"><strong>Next</strong></a></li></ul><div class="section" title="27.6. Understanding /dev/oprofile/" id="s1-oprofile-dev-oprofile"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-dev-oprofile">27.6. Understanding <code class="filename">/dev/oprofile/</code> </h2></div></div></div><a id="id648762" class="indexterm"></a><a id="id648780" class="indexterm"></a><div class="para">
+ The <code class="filename">/dev/oprofile/</code> directory contains the file system for OProfile. Use the <code class="command">cat</code> command to display the values of the virtual files in this file system. For example, the following command displays the type of processor OProfile detected:
+ </div><pre class="screen">
+<code class="command">cat /dev/oprofile/cpu_type</code>
+</pre><div class="para">
+ A directory exists in <code class="filename">/dev/oprofile/</code> for each counter. For example, if there are 2 counters, the directories <code class="filename">/dev/oprofile/0/</code> and <code class="filename">dev/oprofile/1/</code> exist.
+ </div><div class="para">
+ Each directory for a counter contains the following files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">count</code> — The interval between samples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">enabled</code> — If 0, the counter is off and no samples are collected for it; if 1, the counter is on and samples are being collected for it.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">event</code> — The event to monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">kernel</code> — If 0, samples are not collected for this counter event when the processor is in kernel-space; if 1, samples are collected even if the processor is in kernel-space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">unit_mask</code> — Defines which unit masks are enabled for the counter.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">user</code> — If 0, samples are not collected for the counter event when the processor is in user-space; if 1, samples are collected even if the processor is in user-space.
+ </div></li></ul></div><div class="para">
+ The values of these files can be retrieved with the <code class="command">cat</code> command. For example:
+ </div><pre class="screen">
+<code class="command">cat /dev/oprofile/0/count</code>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-reading-opannotate.html"><strong>Prev</strong>27.5.4. Using opannotate </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-example-usage.html"><strong>Next</strong>27.7. Example Usage</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-example-usage.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-example-usage.html
new file mode 100644
index 0000000..f04f079
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-example-usage.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>27.7. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 27. OProfile" /><link rel="prev" href="s1-oprofile-dev-oprofile.html" title="27.6. Understanding /dev/oprofile/" /><link rel="next" href="s1-oprofile-gui.html" title="27.8. Graphical Interface" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.
</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-dev-oprofile.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-gui.html"><strong>Next</strong></a></li></ul><div class="section" title="27.7. Example Usage" id="s1-oprofile-example-usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-example-usage">27.7. Example Usage</h2></div></div></div><div class="para">
+ While OProfile can be used by developers to analyze application performance, it can also be used by system administrators to perform system analysis. For example:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Determine which applications and services are used the most on a system</em></span> — <code class="command">opreport</code> can be used to determine how much processor time an application or service uses. If the system is used for multiple services but is under performing, the services consuming the most processor time can be moved to dedicated systems.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Determine processor usage</em></span> — The <code class="computeroutput">CPU_CLK_UNHALTED</code> event can be monitored to determine the processor load over a given period of time. This data can then be used to determine if additional processors or a faster processor might improve system performance.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-dev-oprofile.html"><strong>Prev</strong>27.6. Understanding /dev/oprofile/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-gui.html"><strong>Next</strong>27.8. Graphical Interface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-gui.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-gui.html
new file mode 100644
index 0000000..a70fd94
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-gui.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>27.8. Graphical 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 27. OProfile" /><link rel="prev" href="s1-oprofile-example-usage.html" title="27.7. Example Usage" /><link rel="next" href="s1-oprofile-additional-resources.html" title="27.9. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifram
e display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-example-usage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="27.8. Graphical Interface" id="s1-oprofile-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-gui">27.8. Graphical Interface</h2></div></div></div><a id="id572607" class="indexterm"></a><div class="para">
+ Some OProfile preferences can be set with a graphical interface. To start it, execute the <code class="command">oprof_start</code> command as root at a shell prompt. To use the graphical interface, you will need to have the <code class="filename">oprofile-gui</code> package installed.
+ </div><div class="para">
+ After changing any of the options, save them by clicking the <span class="guibutton"><strong>Save and quit</strong></span> button. The preferences are written to <code class="filename">/root/.oprofile/daemonrc</code>, and the application exits. Exiting the application does not stop OProfile from sampling.
+ </div><div class="para">
+ On the <span class="guilabel"><strong>Setup</strong></span> tab, to set events for the processor counters as discussed in <a class="xref" href="s2-oprofile-events.html" title="27.2.2. Setting Events to Monitor">Section 27.2.2, “Setting Events to Monitor”</a>, select the counter from the pulldown menu and select the event from the list. A brief description of the event appears in the text box below the list. Only events available for the specific counter and the specific architecture are displayed. The interface also displays whether the profiler is running and some brief statistics about it.
+ </div><div class="figure" title="Figure 27.1. OProfile Setup" id="fig-oprofile-setup"><div class="figure-contents"><div class="mediaobject"><img src="images/oprof-start-setup.png" alt="OProfile Setup" /><div class="longdesc"><div class="para">
+ <code class="command">oprof_start</code> interface
+ </div></div></div></div><h6>Figure 27.1. OProfile Setup</h6></div><br class="figure-break" /><div class="para">
+ On the right side of the tab, select the <span class="guilabel"><strong>Profile kernel</strong></span> option to count events in kernel mode for the currently selected event, as discussed in <a class="xref" href="s2-oprofile-starting-separate.html" title="27.2.3. Separating Kernel and User-space Profiles">Section 27.2.3, “Separating Kernel and User-space Profiles”</a>. If this option is unselected, no samples are collected for the kernel.
+ </div><div class="para">
+ Select the <span class="guilabel"><strong>Profile user binaries</strong></span> option to count events in user mode for the currently selected event, as discussed in <a class="xref" href="s2-oprofile-starting-separate.html" title="27.2.3. Separating Kernel and User-space Profiles">Section 27.2.3, “Separating Kernel and User-space Profiles”</a>. If this option is unselected, no samples are collected for user applications.
+ </div><div class="para">
+ Use the <span class="guilabel"><strong>Count</strong></span> text field to set the sampling rate for the currently selected event as discussed in <a class="xref" href="s2-oprofile-events.html#s3-oprofile-events-sampling" title="27.2.2.1. Sampling Rate">Section 27.2.2.1, “Sampling Rate”</a>.
+ </div><div class="para">
+ If any unit masks are available for the currently selected event, as discussed in <a class="xref" href="s2-oprofile-events.html#s3-oprofile-events-unit-masks" title="27.2.2.2. Unit Masks">Section 27.2.2.2, “Unit Masks”</a>, they are displayed in the <span class="guilabel"><strong>Unit Masks</strong></span> area on the right side of the <span class="guilabel"><strong>Setup</strong></span> tab. Select the checkbox beside the unit mask to enable it for the event.
+ </div><div class="para">
+ On the <span class="guilabel"><strong>Configuration</strong></span> tab, to profile the kernel, enter the name and location of the <code class="filename">vmlinux</code> file for the kernel to monitor in the <span class="guilabel"><strong>Kernel image file</strong></span> text field. To configure OProfile not to monitor the kernel, select <span class="guilabel"><strong>No kernel image</strong></span>.
+ </div><div class="figure" title="Figure 27.2. OProfile Configuration" id="fig-oprofile-configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/oprof-start-config.png" width="444" alt="OProfile Configuration" /><div class="longdesc"><div class="para">
+ OProfile Configuration
+ </div></div></div></div><h6>Figure 27.2. OProfile Configuration</h6></div><br class="figure-break" /><div class="para">
+ If the <span class="guilabel"><strong>Verbose</strong></span> option is selected, the <code class="command">oprofiled</code> daemon log includes more information.
+ </div><div class="para">
+ If <span class="guilabel"><strong>Per-application kernel samples files</strong></span> is selected, OProfile generates per-application profiles for the kernel and kernel modules as discussed in <a class="xref" href="s2-oprofile-starting-separate.html" title="27.2.3. Separating Kernel and User-space Profiles">Section 27.2.3, “Separating Kernel and User-space Profiles”</a>. This is equivalent to the <code class="command">opcontrol --separate=kernel</code> command. If <span class="guilabel"><strong>Per-application shared libs samples files</strong></span> is selected, OProfile generates per-application profiles for libraries. This is equivalent to the <code class="command">opcontrol --separate=library</code> command.
+ </div><div class="para">
+ To force data to be written to samples files as discussed in <a class="xref" href="s1-oprofile-analyzing-data.html" title="27.5. Analyzing the Data">Section 27.5, “Analyzing the Data”</a>, click the <span class="guibutton"><strong>Flush profiler data</strong></span> button. This is equivalent to the <code class="command">opcontrol --dump</code> command.
+ </div><div class="para">
+ To start OProfile from the graphical interface, click <span class="guibutton"><strong>Start profiler</strong></span>. To stop the profiler, click <span class="guibutton"><strong>Stop profiler</strong></span>. Exiting the application does not stop OProfile from sampling.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-example-usage.html"><strong>Prev</strong>27.7. 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="s1-oprofile-additional-resources.html"><strong>Next</strong>27.9. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-saving-data.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-saving-data.html
new file mode 100644
index 0000000..89c87b8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-saving-data.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>27.4. Saving Data</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 27. OProfile" /><link rel="prev" href="s1-oprofile-starting.html" title="27.3. Starting and Stopping OProfile" /><link rel="next" href="s1-oprofile-analyzing-data.html" title="27.5. Analyzing the Data" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe di
splay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-starting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-analyzing-data.html"><strong>Next</strong></a></li></ul><div class="section" title="27.4. Saving Data" id="s1-oprofile-saving-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-saving-data">27.4. Saving Data</h2></div></div></div><a id="id770296" class="indexterm"></a><div class="para">
+ Sometimes it is useful to save samples at a specific time. For example, when profiling an executable, it may be useful to gather different samples based on different input data sets. If the number of events to be monitored exceeds the number of counters available for the processor, multiple runs of OProfile can be used to collect data, saving the sample data to different files each time.
+ </div><div class="para">
+ To save the current set of sample files, execute the following command, replacing <em class="replaceable"><code><name></code></em> with a unique descriptive name for the current session.
+ </div><pre class="screen">
+<code class="command">opcontrol --save=<em class="replaceable"><code><name></code></em> </code>
+</pre><div class="para">
+ The directory <code class="filename">/var/lib/oprofile/samples/<em class="replaceable"><code>name</code></em>/</code> is created and the current sample files are copied to it.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-starting.html"><strong>Prev</strong>27.3. Starting and Stopping OProfile</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-analyzing-data.html"><strong>Next</strong>27.5. Analyzing the Data</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-starting.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-starting.html
new file mode 100644
index 0000000..3030b4e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-oprofile-starting.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>27.3. Starting and Stopping OProfile</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 27. OProfile" /><link rel="prev" href="s2-oprofile-starting-separate.html" title="27.2.3. Separating Kernel and User-space Profiles" /><link rel="next" href="s1-oprofile-saving-data.html" title="27.4. Saving Data" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade y
our browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-starting-separate.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-saving-data.html"><strong>Next</strong></a></li></ul><div class="section" title="27.3. Starting and Stopping OProfile" id="s1-oprofile-starting"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-oprofile-starting">27.3. Starting and Stopping OProfile</h2></div></div></div><a id="id572452" class="indexterm"></a><div class="para">
+ To start monitoring the system with OProfile, execute the following command as root:
+ </div><a id="id572471" class="indexterm"></a><pre class="screen">
+<code class="command">opcontrol --start</code>
+</pre><div class="para">
+ Output similar to the following is displayed:
+ </div><pre class="screen">Using log file /var/lib/oprofile/oprofiled.log Daemon started. Profiler running.</pre><div class="para">
+ The settings in <code class="filename">/root/.oprofile/daemonrc</code> are used.
+ </div><a id="id770199" class="indexterm"></a><a id="id770217" class="indexterm"></a><a id="id770236" class="indexterm"></a><div class="para">
+ The OProfile daemon, <code class="command">oprofiled</code>, is started; it periodically writes the sample data to the <code class="filename">/var/lib/oprofile/samples/</code> directory. The log file for the daemon is located at <code class="filename">/var/lib/oprofile/oprofiled.log</code>.
+ </div><div class="para">
+ To stop the profiler, execute the following command as root:
+ </div><pre class="screen">
+<code class="command">opcontrol --shutdown</code>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-starting-separate.html"><strong>Prev</strong>27.2.3. Separating Kernel and User-space Profiles</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-saving-data.html"><strong>Next</strong>27.4. Saving Data</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-additional-resources.html
new file mode 100644
index 0000000..06a542d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-additional-resources.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>23.9. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Printer_Configuration.html" title="Chapter 23. Printer Configuration" /><link rel="prev" href="s1-printing-managing.html" title="23.8. Managing Print Jobs" /><link rel="next" href="s2-printing-useful-websites.html" title="23.9.2. Useful Websites" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your bro
wser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-printing-managing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-printing-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" title="23.9. Additional Resources" id="s1-printing-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-additional-resources">23.9. Additional Resources</h2></div></div></div><div class="para">
+ To learn more about printing on Fedora, refer to the following resources.
+ </div><div class="section" title="23.9.1. Installed Documentation" id="s2-printing-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-printing-installed-docs">23.9.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">map lpr</code> — The manual page for the <code class="command">lpr</code> command that allows you to print files from the command line.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man lprm</code> — The manual page for the command line utility to remove print jobs from the print queue.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man mpage</code> — The manual page for the command line utility to print multiple pages on one sheet of paper.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man cupsd</code> — The manual page for the CUPS printer daemon.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man cupsd.conf</code> — The manual page for the CUPS printer daemon configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man classes.conf</code> — The manual page for the class configuration file for CUPS.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-managing.html"><strong>Prev</strong>23.8. Managing Print 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-printing-useful-websites.html"><strong>Next</strong>23.9.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-edit.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-edit.html
new file mode 100644
index 0000000..9c9aea8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-edit.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.7. Modifying Existing Printers</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Printer_Configuration.html" title="Chapter 23. Printer Configuration" /><link rel="prev" href="s1-printing-test-page.html" title="23.6. Printing a Test Page" /><link rel="next" href="ch23s07s02.html" title="23.7.2. The Policies Tab" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or
enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-printing-test-page.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch23s07s02.html"><strong>Next</strong></a></li></ul><div class="section" title="23.7. Modifying Existing Printers" id="s1-printing-edit"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-edit">23.7. Modifying Existing Printers</h2></div></div></div><a id="id969362" class="indexterm"></a><div class="para">
+ To delete an existing printer, select the printer and click the <span class="guibutton"><strong>Delete</strong></span> button on the toolbar. The printer is removed from the printer list once you confirm deletion of the printer configuration.
+ </div><a id="id969385" class="indexterm"></a><div class="para">
+ To set the default printer, select the printer from the printer list and click the <span class="guibutton"><strong>Make Default Printer</strong></span> button in the <span class="guilabel"><strong>Settings</strong></span> tab.
+ </div><div class="section" title="23.7.1. The Settings Tab"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id969412">23.7.1. The <span class="guilabel"><strong>Settings</strong></span> Tab</h3></div></div></div><div class="para">
+ To change printer driver configuration, click the corresponding name in the <span class="guilabel"><strong>Printer</strong></span> list and click the <span class="guilabel"><strong>Settings</strong></span> tab.
+ </div><div class="para">
+ You can modify printer settings such as make and model, make a printer the default, print a test page, change the device location (URI), and more.
+ </div><div class="figure" title="Figure 23.8. Settings Tab" id="fig-printconf-config1"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config1.png" width="444" alt="Settings Tab" /><div class="longdesc"><div class="para">
+ Settings Tab
+ </div></div></div></div><h6>Figure 23.8. Settings Tab</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-test-page.html"><strong>Prev</strong>23.6. Printing a Test Page</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch23s07s02.html"><strong>Next</strong>23.7.2. The Policies Tab</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-ipp-printer.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-ipp-printer.html
new file mode 100644
index 0000000..cd5d462
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-ipp-printer.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>23.2. Adding an IPP Printer</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Printer_Configuration.html" title="Chapter 23. Printer Configuration" /><link rel="prev" href="ch-Printer_Configuration.html" title="Chapter 23. Printer Configuration" /><link rel="next" href="s1-printing-smb-printer.html" title="23.3. Adding a Samba (SMB) Printer" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to vie
w it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Printer_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-smb-printer.html"><strong>Next</strong></a></li></ul><div class="section" title="23.2. Adding an IPP Printer" id="s1-printing-ipp-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-ipp-printer">23.2. Adding an IPP Printer</h2></div></div></div><a id="id965156" class="indexterm"></a><a id="id965170" class="indexterm"></a><a id="id965183" class="indexterm"></a><a id="id965201" class="indexterm"></a><div c
lass="para">
+ An IPP printer is a printer attached to a different system on the same TCP/IP network. The system this printer is attached to may either be running CUPS or simply configured to use IPP.
+ </div><div class="para">
+ If a firewall is enabled on the printer server, then the firewall should be configured to allow send / receive connections on the incoming UDP port 631. If a firewall is enabled on the client (the system sending the print request) then the firewall should be configured to allow accept and create connections through port 631.
+ </div><div class="para">
+ You can add a networked IPP printer by clicking the <span class="guibutton"><strong>New Printer</strong></span> button in the main <span class="application"><strong> Printer Configuration Tool</strong></span> window to display the window in <a class="xref" href="ch-Printer_Configuration.html#fig-printconf-add" title="Figure 23.2. Adding a Printer">Figure 23.2, “ <span class="application">Adding a Printer</span> ”</a>. Enter the <span class="guilabel"><strong>Printer Name</strong></span> (printer names cannot contain spaces and may contain letters, numbers, dashes (-), and underscores (_)), <span class="guilabel"><strong>Description</strong></span>, and <span class="guilabel"><strong>Location</strong></span> to distinguish this printer from others that you may configure on your system. Click <span class="guibutton"><strong>Forward</strong></span> to proceed.
+ </div><div class="para">
+ In the window shown in <a class="xref" href="s1-printing-ipp-printer.html#fig-printconf-ipp" title="Figure 23.4. Adding an IPP Printer">Figure 23.4, “Adding an IPP Printer”</a>, enter the hostname of the IPP printer in the <span class="guilabel"><strong>Hostname</strong></span> field as well as a unique name for the printer in the <span class="guilabel"><strong>Printername</strong></span> field.
+ </div><div class="figure" title="Figure 23.4. Adding an IPP Printer" id="fig-printconf-ipp"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-ipp.png" width="444" alt="Adding an IPP Printer" /><div class="longdesc"><div class="para">
+ Networked IPP Printer
+ </div></div></div></div><h6>Figure 23.4. Adding an IPP Printer</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div><div class="para">
+ Next, select the printer type. Refer to <a class="xref" href="s1-printing-select-model.html" title="23.5. Selecting the Printer Model and Finishing">Section 23.5, “Selecting the Printer Model and Finishing”</a> for details.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Printer_Configuration.html"><strong>Prev</strong>Chapter 23. Printer 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-printing-smb-printer.html"><strong>Next</strong>23.3. Adding a Samba (SMB) Printer</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-jetdirect-printer.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-jetdirect-printer.html
new file mode 100644
index 0000000..5576a88
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-jetdirect-printer.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. Adding a JetDirect Printer</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Printer_Configuration.html" title="Chapter 23. Printer Configuration" /><link rel="prev" href="s1-printing-smb-printer.html" title="23.3. Adding a Samba (SMB) Printer" /><link rel="next" href="s1-printing-select-model.html" title="23.5. Selecting the Printer Model and Finishing" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-printing-smb-printer.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-select-model.html"><strong>Next</strong></a></li></ul><div class="section" title="23.4. Adding a JetDirect Printer" id="s1-printing-jetdirect-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-jetdirect-printer">23.4. Adding a JetDirect Printer</h2></div></div></div><a id="id902804" class="indexterm"></a><a id="id902819" class="indexterm"></a><div class="para">
+ To add a JetDirect or AppSocket connected printer share, click the <span class="guibutton"><strong>New Printer</strong></span> button in the main <span class="application"><strong> Printer Configuration Tool</strong></span> window to display the window in <a class="xref" href="ch-Printer_Configuration.html#fig-printconf-add" title="Figure 23.2. Adding a Printer">Figure 23.2, “ <span class="application">Adding a Printer</span> ”</a>. Enter a unique name for the printer in the <span class="guilabel"><strong>Printer Name</strong></span> field. The printer name can contain letters, numbers, dashes (-), and underscores (_); it <span class="emphasis"><em>must not</em></span> contain any spaces.
+ </div><div class="para">
+ You can also use the <span class="guilabel"><strong>Description</strong></span> and <span class="guilabel"><strong>Location</strong></span> fields to further distinguish this printer from others that may be configured on your system. Both of these fields are optional, and may contain spaces.
+ </div><div class="figure" title="Figure 23.6. Adding a JetDirect Printer" id="fig-printconf-jetdirect"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-jetdirect.png" width="444" alt="Adding a JetDirect Printer" /><div class="longdesc"><div class="para">
+ Adding a JetDirect Printer
+ </div></div></div></div><h6>Figure 23.6. Adding a JetDirect Printer</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>Forward</strong></span> to continue.
+ </div><div class="para">
+ Text fields for the following options appear:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hostname</strong></span> — The hostname or IP address of the JetDirect printer.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Port Number</strong></span> — The port on the JetDirect printer that is listening for print jobs. The default port is 9100.
+ </div></li></ul></div><div class="para">
+ Next, select the printer type. Refer to <a class="xref" href="s1-printing-select-model.html" title="23.5. Selecting the Printer Model and Finishing">Section 23.5, “Selecting the Printer Model and Finishing”</a> for details.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-smb-printer.html"><strong>Prev</strong>23.3. Adding a Samba (SMB) Printer</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-printing-select-model.html"><strong>Next</strong>23.5. Selecting the Printer Model and Finishing</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-managing.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-managing.html
new file mode 100644
index 0000000..8dac27e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-managing.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.8. Managing Print 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Printer_Configuration.html" title="Chapter 23. Printer Configuration" /><link rel="prev" href="ch23s07s04.html" title="23.7.4. The Printer and Job OptionsTab" /><link rel="next" href="s1-printing-additional-resources.html" title="23.9. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrad
e your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch23s07s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="23.8. Managing Print Jobs" id="s1-printing-managing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-managing">23.8. Managing Print Jobs</h2></div></div></div><a id="id865621" class="indexterm"></a><div class="para">
+ When you send a print job to the printer daemon, such as printing a text file from <span class="application"><strong>Emacs</strong></span> or printing an image from <span class="application"><strong>The GIMP</strong></span>, the print job is added to the print spool queue. The print spool queue is a list of print jobs that have been sent to the printer and information about each print request, such as the status of the request, the the job number, and more.
+ </div><div class="para">
+ During the printing process, the Printer Status icon appears in the <span class="application"><strong>Notification Area</strong></span> on the panel. To check the status of a print job, double click the Printer Status, which displays a window similar to <a class="xref" href="s1-printing-managing.html#fig-gnome-print-manager-list" title="Figure 23.12. GNOME Print Status">Figure 23.12, “GNOME Print Status”</a>.
+ </div><div class="figure" title="Figure 23.12. GNOME Print Status" id="fig-gnome-print-manager-list"><div class="figure-contents"><div class="mediaobject"><img src="images/gnome-print-queue.png" width="444" alt="GNOME Print Status" /><div class="longdesc"><div class="para">
+ GNOME Print Status
+ </div></div></div></div><h6>Figure 23.12. GNOME Print Status</h6></div><br class="figure-break" /><div class="para">
+ To cancel a specific print job listed in the <span class="application"><strong>GNOME Print Status</strong></span>, select it from the list and select <span class="guimenu"><strong>Edit</strong></span> > <span class="guimenuitem"><strong>Cancel Documents</strong></span> from the pulldown menu.
+ </div><a id="id595697" class="indexterm"></a><div class="para">
+ To view the list of print jobs in the print spool from a shell prompt, type the command <code class="command">lpq</code>. The last few lines look similar to the following:
+ </div><div class="example" title="Example 23.1. Example of lpq output" id="lpq-example"><div class="example-contents"><pre class="screen">
+Rank Owner/ID Class Job Files Size Time
+active user at localhost+902 A 902 sample.txt 2050 01:20:46
+</pre></div><h6>Example 23.1. Example of <code class="command">lpq</code> output</h6></div><br class="example-break" /><a id="id595739" class="indexterm"></a><div class="para">
+ If you want to cancel a print job, find the job number of the request with the command <code class="command">lpq</code> and then use the command <code class="command">lprm <em class="replaceable"><code>job number</code></em> </code>. For example, <code class="command">lprm 902</code> would cancel the print job in <a class="xref" href="s1-printing-managing.html#lpq-example" title="Example 23.1. Example of lpq output">Example 23.1, “Example of <code class="command">lpq</code> output”</a>. You must have proper permissions to cancel a print job. You can not cancel print jobs that were started by other users unless you are logged in as root on the machine to which the printer is attached.
+ </div><a id="id740585" class="indexterm"></a><a id="id740599" class="indexterm"></a><div class="para">
+ You can also print a file directly from a shell prompt. For example, the command <code class="command">lpr sample.txt</code> prints the text file <code class="filename">sample.txt</code>. The print filter determines what type of file it is and converts it into a format the printer can understand.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch23s07s04.html"><strong>Prev</strong>23.7.4. The Printer and Job OptionsTab</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-printing-additional-resources.html"><strong>Next</strong>23.9. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-select-model.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-select-model.html
new file mode 100644
index 0000000..090b30a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-select-model.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>23.5. Selecting the Printer Model and Finishing</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Printer_Configuration.html" title="Chapter 23. Printer Configuration" /><link rel="prev" href="s1-printing-jetdirect-printer.html" title="23.4. Adding a JetDirect Printer" /><link rel="next" href="s1-printing-test-page.html" title="23.6. Printing a Test Page" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an i
frame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-printing-jetdirect-printer.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-test-page.html"><strong>Next</strong></a></li></ul><div class="section" title="23.5. Selecting the Printer Model and Finishing" id="s1-printing-select-model"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-select-model">23.5. Selecting the Printer Model and Finishing</h2></div></div></div><div class="para">
+ Once you have properly selected a printer queue type, you can choose either option:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Select a Printer from database - If you select this option, choose the make of your printer from the list of <span class="guilabel"><strong>Makes</strong></span>. If your printer make is not listed, choose <span class="guilabel"><strong>Generic</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ Provide PPD file - A PostScript Printer Description (PPD) file may also be provided with your printer. This file is normally provided by the manufacturer. If you are provided with a PPD file, you can choose this option and use the browser bar below the option description to select the PPD file.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref" href="s1-printing-select-model.html#fig-printconf-select-model" title="Figure 23.7. Selecting a Printer Model">Figure 23.7, “Selecting a Printer Model”</a>.
+ </div><div class="figure" title="Figure 23.7. Selecting a Printer Model" id="fig-printconf-select-model"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-select-model.png" width="444" alt="Selecting a Printer Model" /><div class="longdesc"><div class="para">
+ Selecting a Printer Model
+ </div></div></div></div><h6>Figure 23.7. Selecting a Printer Model</h6></div><br class="figure-break" /><div class="para">
+ After choosing an option, click <span class="guibutton"><strong>Forward</strong></span> to continue. <a class="xref" href="s1-printing-select-model.html#fig-printconf-select-model" title="Figure 23.7. Selecting a Printer Model">Figure 23.7, “Selecting a Printer Model”</a> appears. You now have to choose the corresponding model and driver for the printer.
+ </div><div class="para">
+ The recommended printed driver is automatically selected based on the printer model you chose. The print driver processes the data that you want to print into a format the printer can understand. Since a local printer is attached directly to your computer, you need a printer driver to process the data that is sent to the printer.
+ </div><div class="para">
+ If you have a PPD file for the device (usually provided by the manufacturer), you can select it by choosing <span class="guilabel"><strong>Provide PPD file</strong></span>. You can then browse the filesystem for the PPD file by clicking <span class="guibutton"><strong>Browse</strong></span>.
+ </div><div class="section" title="23.5.1. Confirming Printer Configuration" id="s2-printing-confirm"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-printing-confirm">23.5.1. Confirming Printer Configuration</h3></div></div></div><div class="para">
+ The last step is to confirm your printer configuration. Click <span class="guibutton"><strong>Apply</strong></span> to add the print queue if the settings are correct. Click <span class="guibutton"><strong>Back</strong></span> to modify the printer configuration.
+ </div><div class="para">
+ After applying the changes, print a test page to ensure the configuration is correct. Refer to <a class="xref" href="s1-printing-test-page.html" title="23.6. Printing a Test Page">Section 23.6, “Printing a Test Page”</a> for details.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-jetdirect-printer.html"><strong>Prev</strong>23.4. Adding a JetDirect Printer</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-printing-test-page.html"><strong>Next</strong>23.6. Printing a Test Page</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-smb-printer.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-smb-printer.html
new file mode 100644
index 0000000..f3c0505
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-smb-printer.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>23.3. Adding a Samba (SMB) Printer</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Printer_Configuration.html" title="Chapter 23. Printer Configuration" /><link rel="prev" href="s1-printing-ipp-printer.html" title="23.2. Adding an IPP Printer" /><link rel="next" href="s1-printing-jetdirect-printer.html" title="23.4. Adding a JetDirect Printer" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to
view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-printing-ipp-printer.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-jetdirect-printer.html"><strong>Next</strong></a></li></ul><div class="section" title="23.3. Adding a Samba (SMB) Printer" id="s1-printing-smb-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-smb-printer">23.3. Adding a Samba (SMB) Printer</h2></div></div></div><a id="id825278" class="indexterm"></a><a id="id825292" class="indexterm"></a><div class="para">
+ You can add a Samba (SMB) based printer share by clicking the <span class="guibutton"><strong>New Printer</strong></span> button in the main <span class="application"><strong> Printer Configuration Tool</strong></span> window to display the window in <a class="xref" href="ch-Printer_Configuration.html#fig-printconf-add" title="Figure 23.2. Adding a Printer">Figure 23.2, “ <span class="application">Adding a Printer</span> ”</a>. Enter a unique name for the printer in the <span class="guilabel"><strong>Printer Name</strong></span> field. The printer name can contain letters, numbers, dashes (-), and underscores (_); it <span class="emphasis"><em>must not</em></span> contain any spaces.
+ </div><div class="para">
+ You can also use the <span class="guilabel"><strong>Description</strong></span> and <span class="guilabel"><strong>Location</strong></span> fields to further distinguish this printer from others that may be configured on your system. Both of these fields are optional, and may contain spaces.
+ </div><div class="figure" title="Figure 23.5. Adding a SMB Printer" id="fig-printconf-smb"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-smb.png" width="444" alt="Adding a SMB Printer" /><div class="longdesc"><div class="para">
+ SMB Printer
+ </div></div></div></div><h6>Figure 23.5. Adding a SMB Printer</h6></div><br class="figure-break" /><div class="para">
+ As shown in <a class="xref" href="s1-printing-smb-printer.html#fig-printconf-smb" title="Figure 23.5. Adding a SMB Printer">Figure 23.5, “Adding a SMB Printer”</a>, available SMB shares are automatically detected and listed in the <span class="guilabel"><strong>Share</strong></span> column. Click the arrow (
+ <span class="inlinemediaobject"><img src="images/arrow.png" /></span>
+ ) beside a Workgroup to expand it. From the expanded list, select a printer.
+ </div><div class="para">
+ If the printer you are looking for does not appear in the list, enter the SMB address in the <span class="guilabel"><strong>smb://</strong></span> field. Use the format <em class="replaceable"><code>computer name/printer share</code></em>. In <a class="xref" href="s1-printing-smb-printer.html#fig-printconf-smb" title="Figure 23.5. Adding a SMB Printer">Figure 23.5, “Adding a SMB Printer”</a>, the <em class="replaceable"><code>computer name</code></em> is <code class="command">dellbox</code>, while the <em class="replaceable"><code>printer share</code></em> is <code class="command">r2</code>.
+ </div><div class="para">
+ In the <span class="guilabel"><strong>Username</strong></span> field, enter the username to access the printer. This user must exist on the SMB system, and the user must have permission to access the printer. The default user name is typically <strong class="userinput"><code>guest</code></strong> for Windows servers, or <strong class="userinput"><code>nobody</code></strong> for Samba servers.
+ </div><div class="para">
+ Enter the <span class="guilabel"><strong>Password</strong></span> (if required) for the user specified in the <span class="guilabel"><strong>Username</strong></span> field.
+ </div><div class="para">
+ You can then test the connection by clicking <span class="guibutton"><strong>Verify</strong></span>. Upon successful verification, a dialog box appears confirming printer share accessibility.
+ </div><div class="para">
+ Next, select the printer type. Refer to <a class="xref" href="s1-printing-select-model.html" title="23.5. Selecting the Printer Model and Finishing">Section 23.5, “Selecting the Printer Model and Finishing”</a> for details.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ Samba printer usernames and passwords are stored in the printer server as unencrypted files readable by root and lpd. Thus, other users that have root access to the printer server can view the username and password you use to access the Samba printer.
+ </div><div class="para">
+ As such, when you choose a username and password to access a Samba printer, it is advisable that you choose a password that is different from what you use to access your local Fedora system.
+ </div><div class="para">
+ If there are files shared on the Samba print server, it is recommended that they also use a password different from what is used by the print queue.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-ipp-printer.html"><strong>Prev</strong>23.2. Adding an IPP Printer</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-printing-jetdirect-printer.html"><strong>Next</strong>23.4. Adding a JetDirect Printer</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-test-page.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-test-page.html
new file mode 100644
index 0000000..a3b8b42
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-printing-test-page.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Printing a Test Page</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Printer_Configuration.html" title="Chapter 23. Printer Configuration" /><link rel="prev" href="s1-printing-select-model.html" title="23.5. Selecting the Printer Model and Finishing" /><link rel="next" href="s1-printing-edit.html" title="23.7. Modifying Existing Printers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to
view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-printing-select-model.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-edit.html"><strong>Next</strong></a></li></ul><div class="section" title="23.6. Printing a Test Page" id="s1-printing-test-page"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-printing-test-page">23.6. Printing a Test Page</h2></div></div></div><a id="id888936" class="indexterm"></a><div class="para">
+ After you have configured your printer, you should print a test page to make sure the printer is functioning properly. To print a test page, select the printer that you want to try out from the printer list, then click <span class="guibutton"><strong>Print Test Page</strong></span> from the printer's <span class="guilabel"><strong>Settings</strong></span> tab.
+ </div><div class="para">
+ If you change the print driver or modify the driver options, you should print a test page to test the different configuration.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-select-model.html"><strong>Prev</strong>23.5. Selecting the Printer Model and Finishing</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-printing-edit.html"><strong>Next</strong>23.7. Modifying Existing Printers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-additional-resources.html
new file mode 100644
index 0000000..f3fc403
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-additional-resources.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-proc.html" title="Chapter 17. The proc File System" /><link rel="prev" href="s1-proc-sysctl.html" title="17.4. Using the sysctl Command" /><link rel="next" href="ch-The_sysconfig_Directory.html" title="Chapter 18. The sysconfig Directory" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable if
rame display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="ch-The_sysconfig_Directory.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.5. References</h2></div></div></div><a id="id963683" 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="id963719" 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>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>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>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>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="id718114" 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>17.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="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_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-directories.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-directories.html
new file mode 100644
index 0000000..8050d9f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-directories.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-proc.html" title="Chapter 17. The proc File System" /><link rel="prev" href="s2-proc-version.html" title="17.2.30. /proc/version" /><link rel="next" href="s2-proc-dir-bus.html" title="17.3.2. /proc/bus/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</ifra
me></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.3. Directories within <code class="filename">/proc/</code> </h2></div></div></div><a id="id864892" 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="17.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">17.3.1. Process Directories</h3></div></div></div><a id="id864931" 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="17.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">17.3.1.1. <code class="filename">/proc/self/</code> </h4></div></div></div><a id="id647970" 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>17.2.30. /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>17.3.2. /proc/bus/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-sysctl.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-sysctl.html
new file mode 100644
index 0000000..84478f6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-sysctl.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-proc.html" title="Chapter 17. The proc File System" /><link rel="prev" href="s2-proc-pid.html" title="17.3.11. /proc/PID/" /><link rel="next" href="s1-proc-additional-resources.html" title="17.5. References" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</if
rame></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.4. Using the <code class="command">sysctl</code> Command</h2></div></div></div><a id="id822992" class="indexterm"></a><a id="id823006" class="indexterm"></a><a id="id823021" class="indexterm"></a><a id="id833439" class="indexterm"></a><a id="id833469" class="indexterm"></a><a id="id8334
88" 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>17.3.11. /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>17.5. References</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-topfiles.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-topfiles.html
new file mode 100644
index 0000000..ad80a54
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-proc-topfiles.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-proc.html" title="Chapter 17. The proc File System" /><link rel="prev" href="ch-proc.html" title="Chapter 17. The proc File System" /><link rel="next" href="s2-proc-cmdline.html" title="17.2.2. /proc/cmdline" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enabl
e iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2. Top-level Files within the <code class="filename">proc</code> File System</h2></div></div></div><a id="id974904" 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"><h2>Note</h2><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 class="section" title="17.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">17.2.1. <code class="filename">/proc/buddyinfo</code> </h3></div></div></div><a id="id974975" 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 17. 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>17.2.2. /proc/cmdline </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-rpm-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-rpm-additional-resources.html
new file mode 100644
index 0000000..00a1547
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-rpm-additional-resources.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe dis
play.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id651384" 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_Draft_Documentation/0.1/html/Deployment_Guide/s1-rpm-impressing.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-rpm-impressing.html
new file mode 100644
index 0000000..fa53835
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-rpm-impressing.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-rpm-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="id1003124" class="indexterm"></a><a id="id1003136" 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="id1003168" class="indexterm"></a><a id="id639467" 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="id639500" class="indexterm"></a><a id="id736834" 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.fc13.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="id612292" class="indexterm"></a><a id="id612304" class="indexterm"></a><a id="id612315" 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="id851042" class="indexterm"></a><a id="id752171" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qip crontabs-1.10-31.fc13.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="id752218" class="indexterm"></a><a id="id857982" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qlp crontabs-1.10-31.fc13.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_Draft_Documentation/0.1/html/Deployment_Guide/s1-rpm-using.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-rpm-using.html
new file mode 100644
index 0000000..18b1b6e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-rpm-using.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a cl
ass="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>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="id948190" 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="id651376" class="indexterm"></a><a id="id827500" 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="id893728" class="indexterm"></a>
+ <a id="id792221" 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="id651095" class="indexterm"></a>
+ <a id="id600954" 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"><h2>Important</h2><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></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_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-account-info-dbs.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-account-info-dbs.html
new file mode 100644
index 0000000..3fe5a81
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-account-info-dbs.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>9.8. Samba Account Information Databases</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="s2-samba-share-level.html" title="9.7.2. Share-Level Security" /><link rel="next" href="s1-samba-network-browsing.html" title="9.9. Samba Network Browsing" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable
iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-share-level.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-network-browsing.html"><strong>Next</strong></a></li></ul><div class="section" title="9.8. Samba Account Information Databases" id="s1-samba-account-info-dbs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-account-info-dbs">9.8. Samba Account Information Databases</h2></div></div></div><a id="id798261" class="indexterm"></a><div class="para">
+ The latest release of Samba offers many new features including new password database backends not previously available. Samba version 3.0.0 fully supports all databases used in previous versions of Samba. However, although supported, many backends may not be suitable for production use.
+ </div><div class="para">
+ The following is a list different backends you can use with Samba. Other backends not listed here may also be available.
+ </div><a id="id798290" class="indexterm"></a><a id="id798304" class="indexterm"></a><a id="id798322" class="indexterm"></a><a id="id798345" class="indexterm"></a><a id="id798367" class="indexterm"></a><a id="id798381" class="indexterm"></a><a id="id754982" class="indexterm"></a><a id="id755004" class="indexterm"></a><a id="id755027" class="indexterm"></a><div class="variablelist"><dl><dt><span class="term">Plain Text</span></dt><dd><div class="para">
+ Plain text backends are nothing more than the <code class="command">/etc/passwd</code> type backends. With a plain text backend, all usernames and passwords are sent unencrypted between the client and the Samba server. This method is very unsecure and is not recommended for use by any means. It is possible that different Windows clients connecting to the Samba server with plain text passwords cannot support such an authentication method.
+ </div></dd><dt><span class="term"> <code class="command">smbpasswd</code> </span></dt><dd><div class="para">
+ A popular backend used in previous Samba packages, the <code class="command">smbpasswd</code> backend utilizes a plain ASCII text layout that includes the MS Windows LanMan and NT account, and encrypted password information. The <code class="command">smbpasswd</code> backend lacks the storage of the Windows NT/2000/2003 SAM extended controls. The <code class="command">smbpasswd</code> backend is not recommended because it does not scale well or hold any Windows information, such as RIDs for NT-based groups. The <code class="command">tdbsam</code> backend solves these issues for use in a smaller database (250 users), but is still not an enterprise-class solution.
+ </div></dd><dt><span class="term"> <code class="command">ldapsam_compat</code> </span></dt><dd><div class="para">
+ The <code class="command">ldapsam_compat</code> backend allows continued OpenLDAP support for use with upgraded versions of Samba. This option normally used when migrating to Samba 3.0.
+ </div></dd><dt><span class="term"> <code class="command">tdbsam</code> </span></dt><dd><div class="para">
+ The <code class="command">tdbsam</code> backend provides an ideal database backend for local servers, servers that do not need built-in database replication, and servers that do not require the scalability or complexity of LDAP. The <code class="command">tdbsam</code> backend includes all of the <code class="command">smbpasswd</code> database information as well as the previously-excluded SAM information. The inclusion of the extended SAM data allows Samba to implement the same account and system access controls as seen with Windows NT/2000/2003-based systems.
+ </div><div class="para">
+ The <code class="command">tdbsam</code> backend is recommended for 250 users at most. Larger organizations should require Active Directory or LDAP integration due to scalability and possible network infrastructure concerns.
+ </div></dd><dt><span class="term"> <code class="command">ldapsam</code> </span></dt><dd><div class="para">
+ The <code class="command">ldapsam</code> backend provides an optimal distributed account installation method for Samba. LDAP is optimal because of its ability to replicate its database to any number of servers using the OpenLDAP <code class="command">slurpd</code> daemon. LDAP databases are light-weight and scalable, and as such are preferred by large enterprises.
+ </div><div class="para">
+ If you are upgrading from a previous version of Samba to 3.0, note that the <code class="filename">/usr/share/doc/samba-<em class="replaceable"><code><version></code></em>/LDAP/samba.schema</code> has changed. This file contains the <em class="firstterm">attribute syntax definitions</em> and <em class="firstterm">objectclass definitions</em> that the <code class="command">ldapsam</code> backend will need in order to function properly.
+ </div><div class="para">
+ As such, if you are using the <code class="command">ldapsam</code> backend for your Samba server, you will need to configure <code class="command">slapd</code> to include this schema file. Refer to <a class="xref" href="s1-ldap-files-schemas.html" title="14.5. The /etc/openldap/schema/ Directory">Section 14.5, “The <code class="filename">/etc/openldap/schema/</code> Directory”</a> for directions on how to do this.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ You will need to have the <code class="filename">openldap-server</code> package installed if you want to use the <code class="command">ldapsam</code> backend.
+ </div></div></dd><dt><span class="term"> <code class="command">mysqlsam</code> </span></dt><dd><div class="para">
+ The <code class="command">mysqlsam</code> backend uses a MySQL-based database backend. This is useful for sites that already implement MySQL. At present, <code class="command">mysqlsam</code> is now packed in a module separate from Samba, and as such is not officially supported by Samba.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-samba-share-level.html"><strong>Prev</strong>9.7.2. Share-Level Security</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-network-browsing.html"><strong>Next</strong>9.9. Samba Network Browsing</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-configuring.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-configuring.html
new file mode 100644
index 0000000..f01c029
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-configuring.html
@@ -0,0 +1,83 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Configuring a Samba 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="s1-samba-mounting.html" title="9.3.2. Mounting the Share" /><link rel="next" href="s2-samba-configuring-cmdline.html" title="9.4.2. Command Line Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifram
e display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-mounting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-samba-configuring-cmdline.html"><strong>Next</strong></a></li></ul><div class="section" title="9.4. Configuring a Samba Server" id="s1-samba-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-configuring">9.4. Configuring a Samba Server</h2></div></div></div><a id="id841598" class="indexterm"></a><a id="id841612" class="indexterm"></a><div class="para">
+ The default configuration file (<code class="filename">/etc/samba/smb.conf</code>) allows users to view their home directories as a Samba share. It also shares all printers configured for the system as Samba shared printers. In other words, you can attach a printer to the system and print to it from the Windows machines on your network.
+ </div><div class="section" title="9.4.1. Graphical Configuration" id="s2-samba-configuring-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-configuring-gui">9.4.1. Graphical Configuration</h3></div></div></div><a id="id841647" class="indexterm"></a><div class="para">
+ To configure Samba using a graphical interface, use the <span class="application"><strong>Samba Server Configuration Tool</strong></span>. For command line configuration, skip to <a class="xref" href="s2-samba-configuring-cmdline.html" title="9.4.2. Command Line Configuration">Section 9.4.2, “Command Line Configuration”</a>.
+ </div><div class="para">
+ The <span class="application"><strong>Samba Server Configuration Tool</strong></span> is a graphical interface for managing Samba shares, users, and basic server settings. It modifies the configuration files in the <code class="filename">/etc/samba/</code> directory. Any changes to these files not made using the application are preserved.
+ </div><div class="para">
+ To use this application, you must be running the X Window System, have root privileges, and have the <code class="filename">system-config-samba</code> RPM package installed. To start the <span class="application"><strong>Samba Server Configuration Tool</strong></span> from the desktop, go to the <span class="guimenu"><strong>System</strong></span> (on the Panel) > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>Server Settings</strong></span> > <span class="guimenuitem"><strong>Samba</strong></span> or type the command <code class="command">system-config-samba</code> at a shell prompt (for example, in an XTerm or a GNOME terminal).
+ </div><div class="figure" title="Figure 9.3. Samba Server Configuration Tool" id="fig-s-c-samba"><div class="figure-contents"><div class="mediaobject"><img src="images/s-c-samba.png" width="444" alt="Samba Server Configuration Tool" /><div class="longdesc"><div class="para">
+ <span class="application"><strong>Samba Server Configuration Tool</strong></span>
+ </div></div></div></div><h6>Figure 9.3. <span class="application">Samba Server Configuration Tool</span> </h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><div class="para">
+ The <span class="application"><strong>Samba Server Configuration Tool</strong></span> does not display shared printers or the default stanza that allows users to view their own home directories on the Samba server.
+ </div></div><div class="section" title="9.4.1.1. Configuring Server Settings" id="s3-samba-gui-server-settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-gui-server-settings">9.4.1.1. Configuring Server Settings</h4></div></div></div><a id="id725816" class="indexterm"></a><div class="para">
+ The first step in configuring a Samba server is to configure the basic settings for the server and a few security options. After starting the application, select <span class="guimenu"><strong>Preferences</strong></span> > <span class="guimenuitem"><strong>Server Settings</strong></span> from the pulldown menu. The <span class="guilabel"><strong>Basic</strong></span> tab is displayed as shown in <a class="xref" href="s1-samba-configuring.html#fig-samba-basic" title="Figure 9.4. Configuring Basic Server Settings">Figure 9.4, “Configuring Basic Server Settings”</a>.
+ </div><div class="figure" title="Figure 9.4. Configuring Basic Server Settings" id="fig-samba-basic"><div class="figure-contents"><div class="mediaobject"><img src="images/s-c-samba-basic.png" alt="Configuring Basic Server Settings" /><div class="longdesc"><div class="para">
+ Configuring Basic Server Settings
+ </div></div></div></div><h6>Figure 9.4. Configuring Basic Server Settings</h6></div><br class="figure-break" /><div class="para">
+ On the <span class="guilabel"><strong>Basic</strong></span> tab, specify which workgroup the computer should be in as well as a brief description of the computer. They correspond to the <code class="command">workgroup</code> and <code class="command">server string</code> options in <code class="filename">smb.conf</code>.
+ </div><div class="figure" title="Figure 9.5. Configuring Security Server Settings" id="fig-samba-security"><div class="figure-contents"><div class="mediaobject"><img src="images/s-c-samba-security.png" alt="Configuring Security Server Settings" /><div class="longdesc"><div class="para">
+ Configuring Security Server Settings
+ </div></div></div></div><h6>Figure 9.5. Configuring Security Server Settings</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Security</strong></span> tab contains the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Authentication Mode</strong></span> — This corresponds to the <code class="command">security</code> option. Select one of the following types of authentication.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>ADS</strong></span> — The Samba server acts as a domain member in an Active Directory Domain (ADS) realm. For this option, Kerberos must be installed and configured on the server, and Samba must become a member of the ADS realm using the <code class="command">net</code> utility, which is part of the <code class="filename">samba-common</code> package. Refer to the <code class="command">net</code> man page for details. This option does not configure Samba to be an ADS Controller. Specify the realm of the Kerberos server in the <span class="guilabel"><strong>Kerberos Realm</strong></span> field.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ The <span class="guilabel"><strong>Kerberos Realm</strong></span> field must be supplied in all uppercase letters, such as <code class="command">EXAMPLE.COM</code>.
+ </div><div class="para">
+ Using a Samba server as a domain member in an ADS realm assumes proper configuration of Kerberos, including the <code class="filename">/etc/krb5.conf</code> file.
+ </div></div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Domain</strong></span> — The Samba server relies on a Windows NT Primary or Backup Domain Controller to verify the user. The server passes the username and password to the Controller and waits for it to return. Specify the NetBIOS name of the Primary or Backup Domain Controller in the <span class="guilabel"><strong>Authentication Server</strong></span> field.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Encrypted Passwords</strong></span> option must be set to <span class="guilabel"><strong>Yes</strong></span> if this is selected.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Server</strong></span> — The Samba server tries to verify the username and password combination by passing them to another Samba server. If it can not, the server tries to verify using the user authentication mode. Specify the NetBIOS name of the other Samba server in the <span class="guilabel"><strong>Authentication Server</strong></span> field.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Share</strong></span> — Samba users do not have to enter a username and password combination on a per Samba server basis. They are not prompted for a username and password until they try to connect to a specific shared directory from a Samba server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>User</strong></span> — (Default) Samba users must provide a valid username and password on a per Samba server basis. Select this option if you want the <span class="guilabel"><strong>Windows Username</strong></span> option to work. Refer to <a class="xref" href="s1-samba-configuring.html#s3-samba-gui-users" title="9.4.1.2. Managing Samba Users">Section 9.4.1.2, “Managing Samba Users”</a> for details.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Encrypt Passwords</strong></span> — This option must be enabled if the clients are connecting from a system with Windows 98, Windows NT 4.0 with Service Pack 3, or other more recent versions of Microsoft Windows. The passwords are transfered between the server and the client in an encrypted format instead of as a plain-text word that can be intercepted. This corresponds to the <code class="command">encrypted passwords</code> option. Refer to <a class="xref" href="s2-samba-encrypted-passwords.html" title="9.4.3. Encrypted Passwords">Section 9.4.3, “Encrypted Passwords”</a> for more information about encrypted Samba passwords.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Guest Account</strong></span> — When users or guest users log into a Samba server, they must be mapped to a valid user on the server. Select one of the existing usernames on the system to be the guest Samba account. When guests log in to the Samba server, they have the same privileges as this user. This corresponds to the <code class="command">guest account</code> option.
+ </div></li></ul></div><div class="para">
+ After clicking <span class="guibutton"><strong>OK</strong></span>, the changes are written to the configuration file and the daemon is restarted; thus, the changes take effect immediately.
+ </div></div><div class="section" title="9.4.1.2. Managing Samba Users" id="s3-samba-gui-users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-gui-users">9.4.1.2. Managing Samba Users</h4></div></div></div><a id="id941149" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Samba Server Configuration Tool</strong></span> requires that an existing user account be active on the system acting as the Samba server before a Samba user can be added. The Samba user is associated with the existing user account.
+ </div><div class="figure" title="Figure 9.6. Managing Samba Users" id="fig-samba-users"><div class="figure-contents"><div class="mediaobject"><img src="images/s-c-samba-users.png" alt="Managing Samba Users" /><div class="longdesc"><div class="para">
+ Managing Samba Users
+ </div></div></div></div><h6>Figure 9.6. Managing Samba Users</h6></div><br class="figure-break" /><div class="para">
+ To add a Samba user, select <span class="guimenu"><strong>Preferences</strong></span> > <span class="guimenuitem"><strong>Samba Users</strong></span> from the pulldown menu, and click the <span class="guibutton"><strong>Add User</strong></span> button. In the <span class="guilabel"><strong>Create New Samba User</strong></span> window select a <span class="guilabel"><strong>Unix Username</strong></span> from the list of existing users on the local system.
+ </div><div class="para">
+ If the user has a different username on a Windows machine and needs to log into the Samba server from the Windows machine, specify that Windows username in the <span class="guilabel"><strong>Windows Username</strong></span> field. The <span class="guilabel"><strong>Authentication Mode</strong></span> on the <span class="guilabel"><strong>Security</strong></span> tab of the <span class="guilabel"><strong>Server Settings</strong></span> preferences must be set to <span class="guilabel"><strong>User</strong></span> for this option to work.
+ </div><div class="para">
+ Also, configure a <span class="guilabel"><strong>Samba Password</strong></span> for the Samba User and confirm it by typing it again. Even if you opt to use encrypted passwords for Samba, it is recommended that the Samba passwords for all users are different from their system passwords.
+ </div><div class="para">
+ To edit an existing user, select the user from the list, and click <span class="guibutton"><strong>Edit User</strong></span>. To delete an existing Samba user, select the user, and click the <span class="guibutton"><strong>Delete User</strong></span> button. Deleting a Samba user does not delete the associated system user account.
+ </div><div class="para">
+ The users are modified immediately after clicking the <span class="guibutton"><strong>OK</strong></span> button.
+ </div></div><div class="section" title="9.4.1.3. Adding a Share" id="s3-samba-gui-add-share"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-gui-add-share">9.4.1.3. Adding a Share</h4></div></div></div><a id="id982712" class="indexterm"></a><div class="para">
+ To create a Samba share, click the <span class="guibutton"><strong>Add</strong></span> button from the main Samba configuration window.
+ </div><div class="figure" title="Figure 9.7. Adding a Share" id="fig-samba-add-share"><div class="figure-contents"><div class="mediaobject"><img src="images/s-c-samba-create-share.png" alt="Adding a Share" /><div class="longdesc"><div class="para">
+ Adding a Samba Share
+ </div></div></div></div><h6>Figure 9.7. Adding a Share</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>Basic</strong></span> tab configures the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Directory</strong></span> — The directory to share via Samba. The directory must exist before it can be entered here.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Share name</strong></span> — The actual name of the share that is seen from remote machines. By default, it is the same value as <span class="guilabel"><strong>Directory</strong></span>, but can be configured.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Descriptions</strong></span> — A brief description of the share.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Writable</strong></span> — Enables users to read and write to the shared directory
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Visible</strong></span> — Grants read-only rights to users for the shared directory.
+ </div></li></ul></div><div class="para">
+ On the <span class="guilabel"><strong>Access</strong></span> tab, select whether to allow only specified users to access the share or whether to allow all Samba users to access the share. If you select to allow access to specific users, select the users from the list of available Samba users.
+ </div><div class="para">
+ The share is added immediately after clicking <span class="guibutton"><strong>OK</strong></span>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-mounting.html"><strong>Prev</strong>9.3.2. Mounting the Share</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-configuring-cmdline.html"><strong>Next</strong>9.4.2. Command Line Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-connect-share.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-connect-share.html
new file mode 100644
index 0000000..2cea1c8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-connect-share.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>9.3. Connecting to a Samba Share</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="s1-samba-daemons.html" title="9.2. Samba Daemons and Related Services" /><link rel="next" href="s1-samba-mounting.html" title="9.3.2. Mounting the Share" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe dis
play.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-daemons.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-mounting.html"><strong>Next</strong></a></li></ul><div class="section" title="9.3. Connecting to a Samba Share" id="s1-samba-connect-share"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-connect-share">9.3. Connecting to a Samba Share</h2></div></div></div><a id="id658797" class="indexterm"></a><div class="para">
+ You can use <span class="application"><strong>Nautilus</strong></span> to view available Samba shares on your network. Select <span class="guimenu"><strong>Places</strong></span> (on the Panel) > <span class="guimenuitem"><strong>Network Servers</strong></span> to view a list of Samba workgroups on your network. You can also type <strong class="userinput"><code>smb:</code></strong> in the <span class="guilabel"><strong>File</strong></span> > <span class="guilabel"><strong>Open Location</strong></span> bar of Nautilus to view the workgroups.
+ </div><div class="para">
+ As shown in <a class="xref" href="s1-samba-connect-share.html#fig-samba-nautilus-workgroups" title="Figure 9.1. SMB Workgroups in Nautilus">Figure 9.1, “SMB Workgroups in Nautilus”</a>, an icon appears for each available SMB workgroup on the network.
+ </div><div class="figure" title="Figure 9.1. SMB Workgroups in Nautilus" id="fig-samba-nautilus-workgroups"><div class="figure-contents"><div class="mediaobject"><img src="images/samba-nautilus.png" width="444" alt="SMB Workgroups in Nautilus" /><div class="longdesc"><div class="para">
+ SMB Workgroups in Nautilus
+ </div></div></div></div><h6>Figure 9.1. SMB Workgroups in Nautilus</h6></div><br class="figure-break" /><div class="para">
+ Double-click one of the workgroup icons to view a list of computers within the workgroup.
+ </div><div class="figure" title="Figure 9.2. SMB Machines in Nautilus" id="fig-samba-nautilus-machines"><div class="figure-contents"><div class="mediaobject"><img src="images/samba-nautilus-machines.png" width="444" alt="SMB Machines in Nautilus" /><div class="longdesc"><div class="para">
+ SMB Machines in Nautilus
+ </div></div></div></div><h6>Figure 9.2. SMB Machines in Nautilus</h6></div><br class="figure-break" /><div class="para">
+ As you can see from <a class="xref" href="s1-samba-connect-share.html#fig-samba-nautilus-machines" title="Figure 9.2. SMB Machines in Nautilus">Figure 9.2, “SMB Machines in Nautilus”</a>, there is an icon for each machine within the workgroup. Double-click on an icon to view the Samba shares on the machine. If a username and password combination is required, you are prompted for them.
+ </div><div class="para">
+ Alternately, you can also specify the Samba server and sharename in the <span class="guilabel"><strong>Location:</strong></span> bar for <span class="application"><strong>Nautilus</strong></span> using the following syntax (replace <em class="replaceable"><code><servername></code></em> and <em class="replaceable"><code><sharename></code></em> with the appropriate values):
+ </div><pre class="screen">
+<code class="command">smb://<em class="replaceable"><code><servername></code></em>/<em class="replaceable"><code><sharename></code></em> </code>
+</pre><div class="section" title="9.3.1. Command Line" id="s2-samba-connect-share-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-connect-share-cmdline">9.3.1. Command Line</h3></div></div></div><a id="id929647" class="indexterm"></a><a id="id1010464" class="indexterm"></a><a id="id1010482" class="indexterm"></a><div class="para">
+ To query the network for Samba servers, use the <code class="command">findsmb</code> command. For each server found, it displays its IP address, NetBIOS name, workgroup name, operating system, and SMB server version.
+ </div><a id="id1010504" class="indexterm"></a><a id="id1010522" class="indexterm"></a><div class="para">
+ To connect to a Samba share from a shell prompt, type the following command:
+ </div><pre class="screen">
+<code class="command">smbclient //<em class="replaceable"><code><hostname></code></em>/<em class="replaceable"><code><sharename></code></em> -U <em class="replaceable"><code><username></code></em> </code>
+</pre><div class="para">
+ Replace <em class="replaceable"><code><hostname></code></em> with the hostname or IP address of the Samba server you want to connect to, <em class="replaceable"><code><sharename></code></em> with the name of the shared directory you want to browse, and <em class="replaceable"><code><username></code></em> with the Samba username for the system. Enter the correct password or press <span class="keycap"><strong>Enter</strong></span> if no password is required for the user.
+ </div><div class="para">
+ If you see the <code class="prompt">smb:\></code> prompt, you have successfully logged in. Once you are logged in, type <strong class="userinput"><code>help</code></strong> for a list of commands. If you wish to browse the contents of your home directory, replace <em class="replaceable"><code>sharename</code></em> with your username. If the <code class="command">-U</code> switch is not used, the username of the current user is passed to the Samba server.
+ </div><div class="para">
+ To exit <code class="command">smbclient</code>, type <strong class="userinput"><code>exit</code></strong> at the <code class="prompt">smb:\></code> prompt.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-daemons.html"><strong>Prev</strong>9.2. Samba Daemons and Related 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="s1-samba-mounting.html"><strong>Next</strong>9.3.2. Mounting the Share</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-cups.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-cups.html
new file mode 100644
index 0000000..36354b2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-cups.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>9.10. Samba with CUPS Printing Support</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="s2-samba-wins.html" title="9.9.2. WINS (Windows Internetworking Name Server)" /><link rel="next" href="s1-samba-programs.html" title="9.11. Samba Distribution Programs" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-wins.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-programs.html"><strong>Next</strong></a></li></ul><div class="section" title="9.10. Samba with CUPS Printing Support" id="s1-samba-cups"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-cups">9.10. Samba with CUPS Printing Support</h2></div></div></div><a id="id930131" class="indexterm"></a><div class="para">
+ Samba allows client machines to share printers connected to the Samba server. In addition, Samba also allows client machines to send documents built in Linux to Windows printer shares. Although there are other printing systems that function with Fedora, CUPS (Common UNIX Print System) is the recommended printing system due to its close integration with Samba.
+ </div><div class="section" title="9.10.1. Simple smb.conf Settings" id="s2-samba-cups-smb.conf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-cups-smb.conf">9.10.1. Simple <code class="filename">smb.conf</code> Settings</h3></div></div></div><a id="id930172" class="indexterm"></a><div class="para">
+ The following example shows a very basic <code class="filename">smb.conf</code> configuration for CUPS support:
+ </div><pre class="screen">
+[global]
+load printers = Yes
+printing = cups
+printcap name = cups
+[printers]
+comment = All Printers
+path = /var/spool/samba
+printer = IBMInfoP
+browseable = No
+public = Yes
+guest ok = Yes
+writable = No
+printable = Yes
+printer admin = @ntadmins
+[print$]
+comment = Printer Drivers Share
+path = /var/lib/samba/drivers
+write list = ed, john
+printer admin = ed, john
+</pre><div class="para">
+ Other printing configurations are also possible. To add additional security and privacy for printing confidential documents, users can have their own print spooler not located in a public path. If a job fails, other users would not have access to the file.
+ </div><div class="para">
+ The <code class="command">print$</code> share contains printer drivers for clients to access if not available locally. The <code class="command">print$</code> share is optional and may not be required depending on the organization.
+ </div><div class="para">
+ Setting <code class="command">browseable</code> to <code class="command">Yes</code> enables the printer to be viewed in the Windows Network Neighborhood, provided the Samba server is set up correctly in the domain/workgroup.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-samba-wins.html"><strong>Prev</strong>9.9.2. WINS (Windows Internetworking Name 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-samba-programs.html"><strong>Next</strong>9.11. Samba Distribution Programs</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-daemons.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-daemons.html
new file mode 100644
index 0000000..c9250e2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-daemons.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>9.2. Samba Daemons and Related 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="next" href="s1-samba-connect-share.html" title="9.3. Connecting to a Samba Share" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</ifra
me></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Samba.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-connect-share.html"><strong>Next</strong></a></li></ul><div class="section" title="9.2. Samba Daemons and Related Services" id="s1-samba-daemons"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-daemons">9.2. Samba Daemons and Related Services</h2></div></div></div><a id="id714193" class="indexterm"></a><div class="para">
+ The following is a brief introduction to the individual Samba daemons and services.
+ </div><div class="section" title="9.2.1. Samba Daemons" id="s2-samba-services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-services">9.2.1. Samba Daemons</h3></div></div></div><a id="id726964" class="indexterm"></a><div class="para">
+ Samba is comprised of three daemons (<code class="command">smbd</code>, <code class="command">nmbd</code>, and <code class="command">winbindd</code>). Two services (<code class="command">smb</code> and <code class="command">windbind</code>) control how the daemons are started, stopped, and other service-related features. Each daemon is listed in detail, as well as which specific service has control over it.
+ </div><div class="formalpara" id="s3-samba-daemon-smbd"><h5 class="formalpara"> <code class="command">smbd</code> </h5><a id="id727019" class="indexterm"></a>
+ The <code class="command">smbd</code> server daemon provides file sharing and printing services to Windows clients. In addition, it is responsible for user authentication, resource locking, and data sharing through the SMB protocol. The default ports on which the server listens for SMB traffic are TCP ports 139 and 445.
+ </div><div class="para">
+ The <code class="command">smbd</code> daemon is controlled by the <code class="command">smb</code> service.
+ </div><div class="formalpara" id="s3-samba-daemon-nmbd"><h5 class="formalpara"> <code class="command">nmbd</code> </h5><a id="id872349" class="indexterm"></a>
+ The <code class="command">nmbd</code> server daemon understands and replies to NetBIOS name service requests such as those produced by SMB/CIFS in Windows-based systems. These systems include Windows 95/98/ME, Windows NT, Windows 2000, Windows XP, and LanManager clients. It also participates in the browsing protocols that make up the Windows <span class="guilabel"><strong>Network Neighborhood</strong></span> view. The default port that the server listens to for NMB traffic is UDP port 137.
+ </div><div class="para">
+ The <code class="command">nmbd</code> daemon is controlled by the <code class="command">smb</code> service.
+ </div><div class="formalpara" id="s3-samba-daemon-winbindd"><h5 class="formalpara"> <code class="command">winbindd</code> </h5><a id="id872405" class="indexterm"></a>
+ The <code class="command">winbind</code> service resolves user and group information on a server running Windows NT 2000 or Windows Server 2003. This makes Windows user / group information understandable by UNIX platforms. This is achieved by using Microsoft RPC calls, Pluggable Authentication Modules (PAM), and the Name Service Switch (NSS). This allows Windows NT domain users to appear and operate as UNIX users on a UNIX machine. Though bundled with the Samba distribution, the <code class="command">winbind</code> service is controlled separately from the <code class="command">smb</code> service.
+ </div><div class="para">
+ The <code class="command">winbindd</code> daemon is controlled by the <code class="command">winbind</code> service and does not require the <code class="command">smb</code> service to be started in order to operate. Winbindd is also used when Samba is an Active Directory member, and may also be used on a Samba domain controller (to implement nested groups and/or interdomain trust). Because <code class="command">winbind</code> is a client-side service used to connect to Windows NT-based servers, further discussion of <code class="command">winbind</code> is beyond the scope of this manual.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ You may refer to <a class="xref" href="s1-samba-programs.html" title="9.11. Samba Distribution Programs">Section 9.11, “Samba Distribution Programs”</a> for a list of utilities included in the Samba distribution.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Samba.html"><strong>Prev</strong>Chapter 9. Samba</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-connect-share.html"><strong>Next</strong>9.3. Connecting to a Samba Share</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-mounting.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-mounting.html
new file mode 100644
index 0000000..e272a55
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-mounting.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Mounting the Share</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-samba-connect-share.html" title="9.3. Connecting to a Samba Share" /><link rel="prev" href="s1-samba-connect-share.html" title="9.3. Connecting to a Samba Share" /><link rel="next" href="s1-samba-configuring.html" title="9.4. Configuring a Samba Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade you
r browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-connect-share.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-configuring.html"><strong>Next</strong></a></li></ul><div class="section" title="9.3.2. Mounting the Share" id="s1-samba-mounting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-samba-mounting">9.3.2. Mounting the Share</h3></div></div></div><a id="id1007343" class="indexterm"></a><div class="para">
+ Sometimes it is useful to mount a Samba share to a directory so that the files in the directory can be treated as if they are part of the local file system.
+ </div><div class="para">
+ To mount a Samba share to a directory, create create a directory to mount it to (if it does not already exist), and execute the following command as root:
+ </div><pre class="screen">
+<code class="command">mount -t cifs -o <em class="replaceable"><code><username></code></em>,<em class="replaceable"><code><password></code></em> //<em class="replaceable"><code><servername></code></em>/<em class="replaceable"><code><sharename></code></em> <em class="replaceable"><code>/mnt/point/</code></em> </code>
+</pre><div class="para">
+ This command mounts <em class="replaceable"><code><sharename></code></em> from <em class="replaceable"><code><servername></code></em> in the local directory <em class="replaceable"><code>/mnt/point/</code></em>. For more information about mounting a samba share, refer to <code class="command">man mount.cifs</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-connect-share.html"><strong>Prev</strong>9.3. Connecting to a Samba Share</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-configuring.html"><strong>Next</strong>9.4. Configuring a Samba Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-network-browsing.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-network-browsing.html
new file mode 100644
index 0000000..77a4d6b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-network-browsing.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.9. Samba Network Browsing</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="s1-samba-account-info-dbs.html" title="9.8. Samba Account Information Databases" /><link rel="next" href="s2-samba-wins.html" title="9.9.2. WINS (Windows Internetworking Name Server)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your bro
wser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-account-info-dbs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-samba-wins.html"><strong>Next</strong></a></li></ul><div class="section" title="9.9. Samba Network Browsing" id="s1-samba-network-browsing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-network-browsing">9.9. Samba Network Browsing</h2></div></div></div><a id="id1027376" class="indexterm"></a><a id="id1027390" class="indexterm"></a><div class="para">
+ <em class="firstterm">Network browsing</em> enables Windows and Samba servers to appear in the Windows <span class="guilabel"><strong>Network Neighborhood</strong></span>. Inside the <span class="guilabel"><strong>Network Neighborhood</strong></span>, icons are represented as servers and if opened, the server's shares and printers that are available are displayed.
+ </div><div class="para">
+ Network browsing capabilities require NetBIOS over TCP/IP. NetBIOS-based networking uses broadcast (UDP) messaging to accomplish browse list management. Without NetBIOS and WINS as the primary method for TCP/IP hostname resolution, other methods such as static files (<code class="filename">/etc/hosts</code>) or DNS, must be used.
+ </div><div class="para">
+ A domain master browser collates the browse lists from local master browsers on all subnets so that browsing can occur between workgroups and subnets. Also, the domain master browser should preferably be the local master browser for its own subnet.
+ </div><div class="section" title="9.9.1. Domain Browsing" id="s2-samba-domain-browsing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-domain-browsing">9.9.1. Domain Browsing</h3></div></div></div><a id="id881759" class="indexterm"></a><div class="para">
+ By default, a Windows server PDC for a domain is also the domain master browser for that domain. A Samba server must <span class="emphasis"><em>not</em></span> be set up as a domain master server in this type of situation
+ </div><div class="para">
+ For subnets that do not include the Windows server PDC, a Samba server can be implemented as a local master browser. Configuring the <code class="filename">smb.conf</code> for a local master browser (or no browsing at all) in a domain controller environment is the same as workgroup configuration.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-account-info-dbs.html"><strong>Prev</strong>9.8. Samba Account Information Databases</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-wins.html"><strong>Next</strong>9.9.2. WINS (Windows Internetworking Name Server)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-programs.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-programs.html
new file mode 100644
index 0000000..a534e7b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-programs.html
@@ -0,0 +1,200 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.11. Samba Distribution Programs</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="s1-samba-cups.html" title="9.10. Samba with CUPS Printing Support" /><link rel="next" href="s1-samba-resources.html" title="9.12. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe disp
lay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-cups.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="9.11. Samba Distribution Programs" id="s1-samba-programs"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-programs">9.11. Samba Distribution Programs</h2></div></div></div><a id="id950123" class="indexterm"></a><div class="formalpara" id="s2-samba-programs-findsmb"><h5 class="formalpara"> <code class="filename">findsmb</code> </h5><a id="id950151" class="indexterm"></a><a id="id950173" class="i
ndexterm"></a>
+ <code class="command">findsmb <em class="replaceable"><code><subnet_broadcast_address></code></em> </code>
+ </div><div class="para">
+ The <code class="command">findsmb</code> program is a Perl script which reports information about SMB-aware systems on a specific subnet. If no subnet is specified the local subnet is used. Items displayed include IP address, NetBIOS name, workgroup or domain name, operating system, and version.
+ </div><div class="para">
+ The following example shows the output of executing <code class="command">findsmb</code> as any valid user on a system:
+ </div><pre class="screen">
+<strong class="userinput"><code>findsmb</code></strong>
+IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
+------------------------------------------------------------------
+10.1.59.25 VERVE [MYGROUP] [Unix] [Samba 3.0.0-15]
+10.1.59.26 STATION22 [MYGROUP] [Unix] [Samba 3.0.2-7.FC1]
+10.1.56.45 TREK +[WORKGROUP] [Windows 5.0] [Windows 2000 LAN Manager]
+10.1.57.94 PIXEL [MYGROUP] [Unix] [Samba 3.0.0-15]
+10.1.57.137 MOBILE001 [WORKGROUP] [Windows 5.0] [Windows 2000 LAN Manager]
+10.1.57.141 JAWS +[KWIKIMART] [Unix] [Samba 2.2.7a-security-rollup-fix]
+10.1.56.159 FRED +[MYGROUP] [Unix] [Samba 3.0.0-14.3E]
+10.1.59.192 LEGION *[MYGROUP] [Unix] [Samba 2.2.7-security-rollup-fix]
+10.1.56.205 NANCYN +[MYGROUP] [Unix] [Samba 2.2.7a-security-rollup-fix]
+</pre><div class="formalpara" id="s2-samba-programs-net"><h5 class="formalpara"> <code class="filename">net</code> </h5><a id="id643655" class="indexterm"></a><a id="id643678" class="indexterm"></a>
+ <code class="command">net <em class="replaceable"><code><protocol> <function> <misc_options> <target_options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">net</code> utility is similar to the <code class="command">net</code> utility used for Windows and MS-DOS. The first argument is used to specify the protocol to use when executing a command. The <code class="command"><em class="replaceable"><code><protocol></code></em> </code> option can be <code class="command">ads</code>, <code class="command">rap</code>, or <code class="command">rpc</code> for specifying the type of server connection. Active Directory uses <code class="command">ads</code>, Win9x/NT3 uses <code class="command">rap</code>, and Windows NT4/2000/2003 uses <code class="command">rpc</code>. If the protocol is omitted, <code class="command">net</code> automatically tries to determine it.
+ </div><div class="para">
+ The following example displays a list the available shares for a host named <code class="command">wakko</code>:
+ </div><pre class="screen">
+<strong class="userinput"><code>net -l share -S wakko</code></strong>
+Password:
+Enumerating shared resources (exports) on remote server:
+Share name Type Description
+---------- ---- -----------
+data Disk Wakko data share
+tmp Disk Wakko tmp share
+IPC$ IPC IPC Service (Samba Server)
+ADMIN$ IPC IPC Service (Samba Server)
+</pre><div class="para">
+ The following example displays a list of Samba users for a host named <code class="command">wakko</code>:
+ </div><pre class="screen">
+<strong class="userinput"><code>net -l user -S wakko</code></strong>
+root password:
+User name Comment
+-----------------------------
+andriusb Documentation
+joe Marketing
+lisa Sales
+</pre><div class="formalpara" id="s2-samba-programs-nmblookup"><h5 class="formalpara"> <code class="filename">nmblookup</code> </h5><a id="id875192" class="indexterm"></a><a id="id875215" class="indexterm"></a>
+ <code class="command">nmblookup <em class="replaceable"><code><options> <netbios_name></code></em> </code>
+ </div><div class="para">
+ The <code class="command">nmblookup</code> program resolves NetBIOS names into IP addresses. The program broadcasts its query on the local subnet until the target machine replies.
+ </div><div class="para">
+ Here is an example:
+ </div><pre class="screen">
+<strong class="userinput"><code>nmblookup trek</code></strong>
+querying trek on 10.1.59.255
+10.1.56.45 trek<00>
+</pre><div class="formalpara" id="s2-samba-programs-pdbedit"><h5 class="formalpara"> <code class="filename">pdbedit</code> </h5><a id="id766774" class="indexterm"></a><a id="id766796" class="indexterm"></a>
+ <code class="command">pdbedit <em class="replaceable"><code><options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">pdbedit</code> program manages accounts located in the SAM database. All backends are supported including <code class="filename">smbpasswd</code>, LDAP, NIS+, and the <code class="filename">tdb</code> database library.
+ </div><div class="para">
+ The following are examples of adding, deleting, and listing users:
+ </div><pre class="screen">
+<strong class="userinput"><code>pdbedit -a kristin</code></strong>
+new password:
+retype new password:
+Unix username: kristin
+NT username:
+Account Flags: [U ]
+User SID: S-1-5-21-1210235352-3804200048-1474496110-2012
+Primary Group SID: S-1-5-21-1210235352-3804200048-1474496110-2077
+Full Name: Home Directory: \\wakko\kristin
+HomeDir Drive:
+Logon Script:
+Profile Path: \\wakko\kristin\profile
+Domain: WAKKO
+Account desc:
+Workstations: Munged
+dial:
+Logon time: 0
+Logoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Kickoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Password last set: Thu, 29 Jan 2004 08:29:28
+GMT Password can change: Thu, 29 Jan 2004 08:29:28 GMT
+Password must change: Mon, 18 Jan 2038 22:14:07 GMT
+<strong class="userinput"><code>pdbedit -v -L kristin</code></strong>
+Unix username: kristin
+NT username:
+Account Flags: [U ]
+User SID: S-1-5-21-1210235352-3804200048-1474496110-2012
+Primary Group SID: S-1-5-21-1210235352-3804200048-1474496110-2077
+Full Name:
+Home Directory: \\wakko\kristin
+HomeDir Drive:
+Logon Script:
+Profile Path: \\wakko\kristin\profile
+Domain: WAKKO
+Account desc:
+Workstations: Munged
+dial:
+Logon time: 0
+Logoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Kickoff time: Mon, 18 Jan 2038 22:14:07 GMT
+Password last set: Thu, 29 Jan 2004 08:29:28 GMT
+Password can change: Thu, 29 Jan 2004 08:29:28 GMT
+Password must change: Mon, 18 Jan 2038 22:14:07 GMT
+<strong class="userinput"><code>pdbedit -L</code></strong>
+andriusb:505:
+joe:503:
+lisa:504:
+kristin:506:
+<strong class="userinput"><code>pdbedit -x joe</code></strong>
+<strong class="userinput"><code>pdbedit -L</code></strong>
+andriusb:505: lisa:504: kristin:506:
+</pre><div class="formalpara" id="s2-samba-programs-rpcclient"><h5 class="formalpara"> <code class="filename">rpcclient</code> </h5><a id="id928713" class="indexterm"></a><a id="id928736" class="indexterm"></a>
+ <code class="command">rpcclient <em class="replaceable"><code><server> <options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">rpcclient</code> program issues administrative commands using Microsoft RPCs, which provide access to the Windows administration graphical user interfaces (GUIs) for systems management. This is most often used by advanced users that understand the full complexity of Microsoft RPCs.
+ </div><div class="formalpara" id="s2-samba-programs-smbcacls"><h5 class="formalpara"> <code class="filename">smbcacls</code> </h5><a id="id928789" class="indexterm"></a><a id="id928812" class="indexterm"></a>
+ <code class="command">smbcacls <em class="replaceable"><code><//server/share> <filename> <options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbcacls</code> program modifies Windows ACLs on files and directories shared by the Samba server.
+ </div><div class="formalpara" id="s2-samba-programs-smbclient"><h5 class="formalpara"> <code class="filename">smbclient</code> </h5><a id="id736909" class="indexterm"></a><a id="id736932" class="indexterm"></a>
+ <code class="command">smbclient <em class="replaceable"><code><//server/share> <password> <options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbclient</code> program is a versatile UNIX client which provides functionality similar to <code class="command">ftp</code>.
+ </div><div class="formalpara" id="s2-samba-programs-smbcontrol"><h5 class="formalpara"> <code class="filename">smbcontrol</code> </h5><a id="id736987" class="indexterm"></a><a id="id737009" class="indexterm"></a>
+ <code class="command">smbcontrol -i <em class="replaceable"><code><options></code></em> </code>
+ </div><div class="para">
+ <code class="command">smbcontrol <em class="replaceable"><code><options> <destination> <messagetype> <parameters></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbcontrol</code> program sends control messages to running <code class="command">smbd</code> or <code class="command">nmbd</code> daemons. Executing <code class="command">smbcontrol -i</code> runs commands interactively until a blank line or a 'q' is entered.
+ </div><div class="formalpara" id="s2-samba-programs-smbpasswd"><h5 class="formalpara"> <code class="filename">smbpasswd</code> </h5><a id="id884595" class="indexterm"></a><a id="id884618" class="indexterm"></a>
+ <code class="command">smbpasswd <em class="replaceable"><code><options> <username> <password></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbpasswd</code> program manages encrypted passwords. This program can be run by a superuser to change any user's password as well as by an ordinary user to change their own Samba password.
+ </div><div class="formalpara" id="s2-samba-programs-smbspool"><h5 class="formalpara"> <code class="filename">smbspool</code> </h5><a id="id749594" class="indexterm"></a><a id="id749617" class="indexterm"></a>
+ <code class="command">smbspool <em class="replaceable"><code><job> <user> <title> <copies> <options> <filename></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbspool</code> program is a CUPS-compatible printing interface to Samba. Although designed for use with CUPS printers, <code class="command">smbspool</code> can work with non-CUPS printers as well.
+ </div><div class="formalpara" id="s2-samba-programs-smbstatus"><h5 class="formalpara"> <code class="filename">smbstatus</code> </h5><a id="id749672" class="indexterm"></a><a id="id749695" class="indexterm"></a>
+ <code class="command">smbstatus <em class="replaceable"><code><options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbstatus</code> program displays the status of current connections to a Samba server.
+ </div><div class="formalpara" id="s2-samba-programs-smbtar"><h5 class="formalpara"> <code class="filename">smbtar</code> </h5><a id="id982419" class="indexterm"></a><a id="id982441" class="indexterm"></a>
+ <code class="command">smbtar <em class="replaceable"><code><options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">smbtar</code> program performs backup and restores of Windows-based share files and directories to a local tape archive. Though similar to the <code class="command">tar</code> command, the two are not compatible.
+ </div><div class="formalpara" id="s2-samba-programs-testparm"><h5 class="formalpara"> <code class="filename">testparm</code> </h5><a id="id982497" class="indexterm"></a><a id="id898554" class="indexterm"></a>
+ <code class="command">testparm <em class="replaceable"><code><options> <filename> <hostname IP_address></code></em> </code>
+ </div><div class="para">
+ The <code class="command">testparm</code> program checks the syntax of the <code class="filename">smb.conf</code> file. If your <code class="filename">smb.conf</code> file is in the default location (<code class="filename">/etc/samba/smb.conf</code>) you do not need to specify the location. Specifying the hostname and IP address to the <code class="command">testparm</code> program verifies that the <code class="filename">hosts.allow</code> and <code class="filename">host.deny</code> files are configured correctly. The <code class="command">testparm</code> program also displays a summary of your <code class="filename">smb.conf</code> file and the server's role (stand-alone, domain, etc.) after testing. This is convenient when debugging as it excludes comments and concisely presents information for experienced administrators to read.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">
+<strong class="userinput"><code>testparm</code></strong>
+Load smb config files from /etc/samba/smb.conf
+Processing section "[homes]"
+Processing section "[printers]"
+Processing section "[tmp]"
+Processing section "[html]"
+Loaded services file OK.
+Server role: ROLE_STANDALONE
+Press enter to see a dump of your service definitions
+<strong class="userinput"><code><enter></code></strong>
+# Global parameters
+[global]
+ workgroup = MYGROUP
+ server string = Samba Server
+ security = SHARE
+ log file = /var/log/samba/%m.log
+ max log size = 50
+ socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
+ dns proxy = No
+[homes]
+ comment = Home Directories
+ read only = No
+ browseable = No
+[printers]
+ comment = All Printers
+ path = /var/spool/samba
+ printable = Yes
+ browseable = No
+[tmp]
+ comment = Wakko tmp
+ path = /tmp
+ guest only = Yes
+[html]
+ comment = Wakko www
+ path = /var/www/html
+ force user = andriusb
+ force group = users
+ read only = No
+ guest only = Yes
+</pre><div class="formalpara" id="s2-samba-programs-wbinfo"><h5 class="formalpara"> <code class="filename">wbinfo</code> </h5><a id="id898670" class="indexterm"></a><a id="id841736" class="indexterm"></a>
+ <code class="command">wbinfo <em class="replaceable"><code><options></code></em> </code>
+ </div><div class="para">
+ The <code class="command">wbinfo</code> program displays information from the <code class="command">winbindd</code> daemon. The <code class="command">winbindd</code> daemon must be running for <code class="command">wbinfo</code> to work.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-cups.html"><strong>Prev</strong>9.10. Samba with CUPS Printing Support</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-resources.html"><strong>Next</strong>9.12. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-resources.html
new file mode 100644
index 0000000..bd00170
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-resources.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.12. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="s1-samba-programs.html" title="9.11. Samba Distribution Programs" /><link rel="next" href="s2-samba-resources-published.html" title="9.12.2. Related Books" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display
.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-programs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-samba-resources-published.html"><strong>Next</strong></a></li></ul><div class="section" title="9.12. Additional Resources" id="s1-samba-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-resources">9.12. Additional Resources</h2></div></div></div><a id="id841797" class="indexterm"></a><div class="para">
+ The following sections give you the means to explore Samba in greater detail.
+ </div><div class="section" title="9.12.1. Installed Documentation" id="s2-samba-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-resources-installed">9.12.1. Installed Documentation</h3></div></div></div><a id="id841824" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/samba-<<em class="replaceable"><code>version-number</code></em>>/</code> — All additional files included with the Samba distribution. This includes all helper scripts, sample configuration files, and documentation.
+ </div><div class="para">
+ This directory also contains online versions of <em class="citetitle">The Official Samba-3 HOWTO-Collection</em> and <em class="citetitle">Samba-3 by Example</em>, both of which are cited below.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-programs.html"><strong>Prev</strong>9.11. Samba Distribution Programs</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-resources-published.html"><strong>Next</strong>9.12.2. Related Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-security-modes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-security-modes.html
new file mode 100644
index 0000000..058573a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-security-modes.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>9.7. Samba Security Modes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="s2-samba-domain-controller.html" title="9.6.3. Domain Controller" /><link rel="next" href="s2-samba-share-level.html" title="9.7.2. Share-Level Security" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</
iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-domain-controller.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-samba-share-level.html"><strong>Next</strong></a></li></ul><div class="section" title="9.7. Samba Security Modes" id="s1-samba-security-modes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-security-modes">9.7. Samba Security Modes</h2></div></div></div><a id="id714418" class="indexterm"></a><div class="para">
+ There are only two types of security modes for Samba, <span class="emphasis"><em>share-level</em></span> and <span class="emphasis"><em>user-level</em></span>, which are collectively known as <span class="emphasis"><em><em class="firstterm">security levels</em> </em></span>. Share-level security can only be implemented in one way, while user-level security can be implemented in one of four different ways. The different ways of implementing a security level are called <span class="emphasis"><em><em class="firstterm">security modes</em> </em></span>.
+ </div><div class="section" title="9.7.1. User-Level Security" id="s2-samba-user-level"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-user-level">9.7.1. User-Level Security</h3></div></div></div><a id="id714469" class="indexterm"></a><div class="para">
+ User-level security is the default setting for Samba. Even if the <code class="command">security = user</code> directive is not listed in the <code class="command">smb.conf</code> file, it is used by Samba. If the server accepts the client's username/password, the client can then mount multiple shares without specifying a password for each instance. Samba can also accept session-based username/password requests. The client maintains multiple authentication contexts by using a unique UID for each logon.
+ </div><div class="para">
+ In <code class="command">smb.conf</code>, the <code class="command">security = user</code> directive that sets user-level security is:
+ </div><pre class="screen">
+[GLOBAL]
+...
+security = user
+...
+</pre><div class="para">
+ The following sections describe other implementations of user-level security.
+ </div><div class="section" title="9.7.1.1. Domain Security Mode (User-Level Security)" id="s2-samba-domain-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-samba-domain-security-mode">9.7.1.1. Domain Security Mode (User-Level Security)</h4></div></div></div><a id="id872207" class="indexterm"></a><div class="para">
+ In domain security mode, the Samba server has a machine account (domain security trust account) and causes all authentication requests to be passed through to the domain controllers. The Samba server is made into a domain member server by using the following directives in <code class="command">smb.conf</code>:
+ </div><pre class="screen">
+[GLOBAL]
+...
+security = domain
+workgroup = MARKETING
+...
+</pre></div><div class="section" title="9.7.1.2. Active Directory Security Mode (User-Level Security)" id="s2-samba-ads-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-samba-ads-security-mode">9.7.1.2. Active Directory Security Mode (User-Level Security)</h4></div></div></div><a id="id872250" class="indexterm"></a><div class="para">
+ If you have an Active Directory environment, it is possible to join the domain as a native Active Directory member. Even if a security policy restricts the use of NT-compatible authentication protocols, the Samba server can join an ADS using Kerberos. Samba in Active Directory member mode can accept Kerberos tickets.
+ </div><div class="para">
+ In <code class="command">smb.conf</code>, the following directives make Samba an Active Directory member server:
+ </div><pre class="screen">
+[GLOBAL]
+...
+security = ADS
+realm = EXAMPLE.COM
+password server = kerberos.example.com
+...
+</pre></div><div class="section" title="9.7.1.3. Server Security Mode (User-Level Security)" id="s2-samba-server-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-samba-server-security-mode">9.7.1.3. Server Security Mode (User-Level Security)</h4></div></div></div><a id="id906671" class="indexterm"></a><div class="para">
+ Server security mode was previously used when Samba was not capable of acting as a domain member server.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ It is highly recommended to <span class="emphasis"><em>not</em></span> use this mode since there are numerous security drawbacks.
+ </div></div><div class="para">
+ In <code class="filename">smb.conf</code>, the following directives enable Samba to operate in server security mode:
+ </div><pre class="screen">
+[GLOBAL]
+...
+encrypt passwords = Yes
+security = server
+password server = "NetBIOS_of_Domain_Controller"
+...
+</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-samba-domain-controller.html"><strong>Prev</strong>9.6.3. Domain Controller</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-share-level.html"><strong>Next</strong>9.7.2. Share-Level Security</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-servers.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-servers.html
new file mode 100644
index 0000000..96359e8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-servers.html
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.6. Samba Server Types and the smb.conf 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="s1-samba-startstop.html" title="9.5. Starting and Stopping Samba" /><link rel="next" href="s2-samba-domain-member.html" title="9.6.2. Domain Member Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or en
able iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-startstop.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-samba-domain-member.html"><strong>Next</strong></a></li></ul><div class="section" title="9.6. Samba Server Types and the smb.conf File" id="s1-samba-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-servers">9.6. Samba Server Types and the <code class="command">smb.conf</code> File</h2></div></div></div><a id="id957097" class="indexterm"></a><a id="id959930" class="indexterm"></a><div class="para">
+ Samba configuration is straightforward. All modifications to Samba are done in the <code class="filename">/etc/samba/smb.conf</code> configuration file. Although the default <code class="filename">smb.conf</code> file is well documented, it does not address complex topics such as LDAP, Active Directory, and the numerous domain controller implementations.
+ </div><div class="para">
+ The following sections describe the different ways a Samba server can be configured. Keep in mind your needs and the changes required to the <code class="filename">smb.conf</code> file for a successful configuration.
+ </div><div class="section" title="9.6.1. Stand-alone Server" id="s2-samba-standalone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-standalone">9.6.1. Stand-alone Server</h3></div></div></div><a id="id959975" class="indexterm"></a><div class="para">
+ A stand-alone server can be a workgroup server or a member of a workgroup environment. A stand-alone server is not a domain controller and does not participate in a domain in any way. The following examples include several anonymous share-level security configurations and one user-level security configuration. For more information on share-level and user-level security modes, refer to <a class="xref" href="s1-samba-security-modes.html" title="9.7. Samba Security Modes">Section 9.7, “Samba Security Modes”</a>.
+ </div><div class="section" title="9.6.1.1. Anonymous Read-Only" id="s3-samba-standalone-anonreadonly"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-standalone-anonreadonly">9.6.1.1. Anonymous Read-Only</h4></div></div></div><a id="id960015" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement anonymous read-only file sharing. The <code class="command">security = share</code> parameter makes a share anonymous. Note, security levels for a single Samba server cannot be mixed. The <code class="command">security</code> directive is a global Samba parameter located in the <code class="command">[global]</code> configuration section of the <code class="command">smb.conf</code> file.
+ </div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+[data]
+comment = Documentation Samba Server
+path = /export
+read only = Yes
+guest only = Yes
+</pre></div><div class="section" title="9.6.1.2. Anonymous Read/Write" id="s3-samba-standalone-anonreadwrite"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-standalone-anonreadwrite">9.6.1.2. Anonymous Read/Write</h4></div></div></div><a id="id869575" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement anonymous read/write file sharing. To enable anonymous read/write file sharing, set the <code class="command">read only</code> directive to <code class="command">no</code>. The <code class="command">force user</code> and <code class="command">force group</code> directives are also added to enforce the ownership of any newly placed files specified in the share.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ Although having an anonymous read/write server is possible, it is not recommended. Any files placed in the share space, regardless of user, are assigned the user/group combination as specified by a generic user (<code class="command">force user</code>) and group (<code class="command">force group</code>) in the <code class="filename">smb.conf</code> file.
+ </div></div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+[data]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+read only = No
+guest ok = Yes
+</pre></div><div class="section" title="9.6.1.3. Anonymous Print Server" id="s3-samba-standalone-anonprint"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-standalone-anonprint">9.6.1.3. Anonymous Print Server</h4></div></div></div><a id="id869661" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement an anonymous print server. Setting <code class="command">browseable</code> to <code class="command">no</code> as shown does not list the printer in Windows <span class="guilabel"><strong>Network Neighborhood</strong></span>. Although hidden from browsing, configuring the printer explicitly is possible. By connecting to <code class="command">DOCS_SRV</code> using NetBIOS, the client can have access to the printer if the client is also part of the <code class="command">DOCS</code> workgroup. It is also assumed that the client has the correct local printer driver installed, as the <code class="command">use client driver</code> directive is set to <code class="command">Yes</code>. In this case, the Samba server has no responsibility for sharing printer drivers to the client.
+ </div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = share
+printcap name = cups
+disable spools= Yes
+show add printer wizard = No
+printing = cups
+[printers]
+comment = All Printers
+path = /var/spool/samba
+guest ok = Yes
+printable = Yes
+use client driver = Yes
+browseable = Yes
+</pre></div><div class="section" title="9.6.1.4. Secure Read/Write File and Print Server" id="s3-samba-standalone-readwriteall"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-standalone-readwriteall">9.6.1.4. Secure Read/Write File and Print Server</h4></div></div></div><a id="id662677" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement a secure read/write print server. Setting the <code class="command">security</code> directive to <code class="command">user</code> forces Samba to authenticate client connections. Notice the <code class="command">[homes]</code> share does not have a <code class="command">force user</code> or <code class="command">force group</code> directive as the <code class="command">[public]</code> share does. The <code class="command">[homes]</code> share uses the authenticated user details for any files created as opposed to the <code class="command">force user</code> and <code class="command">force group</code> in <code class="command">[public]</code>.
+ </div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = user
+printcap name = cups
+disable spools = Yes
+show add printer wizard = No
+printing = cups
+[homes]
+comment = Home Directories
+valid users = %S
+read only = No
+browseable = No
+[public]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+guest ok = Yes
+[printers]
+comment = All Printers
+path = /var/spool/samba
+printer admin = john, ed, @admins
+create mask = 0600
+guest ok = Yes
+printable = Yes
+use client driver = Yes
+browseable = Yes
+</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-startstop.html"><strong>Prev</strong>9.5. Starting and Stopping Samba</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-domain-member.html"><strong>Next</strong>9.6.2. Domain Member Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-startstop.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-startstop.html
new file mode 100644
index 0000000..7069541
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-samba-startstop.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>9.5. Starting and Stopping Samba</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Samba.html" title="Chapter 9. Samba" /><link rel="prev" href="s2-samba-encrypted-passwords.html" title="9.4.3. Encrypted Passwords" /><link rel="next" href="s1-samba-servers.html" title="9.6. Samba Server Types and the smb.conf File" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or
enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-encrypted-passwords.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-servers.html"><strong>Next</strong></a></li></ul><div class="section" title="9.5. Starting and Stopping Samba" id="s1-samba-startstop"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-samba-startstop">9.5. Starting and Stopping Samba</h2></div></div></div><a id="id605668" class="indexterm"></a><a id="id605686" class="indexterm"></a><a id="id953877" class="indexterm"></a><a id="id953895" class="indexterm"></a><a id="id953914" class="indexterm"></
a><div class="para">
+ To start a Samba server, type the following command in a shell prompt while logged in as root:
+ </div><pre class="screen">
+<code class="command">/sbin/service smb start</code>
+</pre><div class="important"><h2>Important</h2><div class="para">
+ To set up a domain member server, you must first join the domain or Active Directory using the <code class="command">net join</code> command <span class="emphasis"><em>before</em></span> starting the <code class="command">smb</code> service.
+ </div></div><div class="para">
+ To stop the server, type the following command in a shell prompt while logged in as root:
+ </div><pre class="screen">
+<code class="command">/sbin/service smb stop</code>
+</pre><div class="para">
+ The <code class="option">restart</code> option is a quick way of stopping and then starting Samba. This is the most reliable way to make configuration changes take effect after editing the configuration file for Samba. Note that the restart option starts the daemon even if it was not running originally.
+ </div><div class="para">
+ To restart the server, type the following command in a shell prompt while logged in as root:
+ </div><pre class="screen">
+<code class="command"> /sbin/service smb restart </code>
+</pre><div class="para">
+ The <code class="option">condrestart</code> (<em class="firstterm">conditional restart</em>) option only starts <code class="command">smb</code> on the condition that it is currently running. This option is useful for scripts, because it does not start the daemon if it is not running.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ When the <code class="command">smb.conf</code> file is changed, Samba automatically reloads it after a few minutes. Issuing a manual <code class="command">restart</code> or <code class="command">reload</code> is just as effective.
+ </div></div><div class="para">
+ To conditionally restart the server, type the following command as root:
+ </div><pre class="screen">
+<code class="command"> /sbin/service smb condrestart </code>
+</pre><div class="para">
+ A manual reload of the <code class="command">smb.conf</code> file can be useful in case of a failed automatic reload by the <code class="command">smb</code> service. To ensure that the Samba server configuration file is reloaded without restarting the service, type the following command as root:
+ </div><pre class="screen">
+<code class="command"> /sbin/service smb reload </code>
+</pre><div class="para">
+ By default, the <code class="command">smb</code> service does <span class="emphasis"><em>not</em></span> start automatically at boot time. To configure Samba to start at boot time, use an initscript utility, such as <code class="command">/sbin/chkconfig</code>, <code class="command">/usr/sbin/ntsysv</code>, or the <span class="application"><strong>Services Configuration Tool</strong></span> program. Refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a> for more information regarding these tools.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-samba-encrypted-passwords.html"><strong>Prev</strong>9.4.3. Encrypted 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="s1-samba-servers.html"><strong>Next</strong>9.6. Samba Server Types and the smb.conf File</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-secureserver-oldcert.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-secureserver-oldcert.html
new file mode 100644
index 0000000..6118f3f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-secureserver-oldcert.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>11.8.3. Using Pre-Existing Keys and Certificates</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-httpd-secure-server.html" title="11.8. Apache HTTP Secure Server Configuration" /><link rel="prev" href="s2-secureserver-overview-certs.html" title="11.8.2. An Overview of Certificates and Security" /><link rel="next" href="s2-secureserver-certs.html" title="11.8.4. Types of Certificates" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../.
./../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-secureserver-overview-certs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-secureserver-certs.html"><strong>Next</strong></a></li></ul><div class="section" title="11.8.3. Using Pre-Existing Keys and Certificates" id="s1-secureserver-oldcert"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-secureserver-oldcert">11.8.3. Using Pre-Existing Keys and Certificates</h3></div></div></div><a id="id665209" class="indexterm"></a><div class="para">
+ If you already have an existing key and certificate (for example, if you are installing the secure server to replace another company's secure server product), you can probably use your existing key and certificate with the secure server. The following two situations provide instances where you are not able to use your existing key and certificate:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>If you are changing your IP address or domain name</em></span> — Certificates are issued for a particular IP address and domain name pair. You must get a new certificate if you are changing your IP address or domain name.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id790325" class="indexterm"></a>
+ <span class="emphasis"><em>If you have a certificate from VeriSign and you are changing your server software</em></span> — VeriSign is a widely used CA. If you already have a VeriSign certificate for another purpose, you may have been considering using your existing VeriSign certificate with your new secure server. However, you are not be allowed to because VeriSign issues certificates for one specific server software and IP address/domain name combination.
+ </div><div class="para">
+ If you change either of those parameters (for example, if you previously used a different secure server product), the VeriSign certificate you obtained to use with the previous configuration will not work with the new configuration. You must obtain a new certificate.
+ </div></li></ul></div><div class="para">
+ If you have an existing key and certificate that you can use, you do not have to generate a new key and obtain a new certificate. However, you may need to move and rename the files which contain your key and certificate.
+ </div><div class="para">
+ Move your existing key file to:
+ </div><pre class="screen">
+<code class="filename">/etc/pki/tls/private/server.key</code>
+</pre><div class="para">
+ Move your existing certificate file to:
+ </div><pre class="screen">
+<code class="filename">/etc/pki/tls/certs/server.crt</code>
+</pre><div class="para">
+ <a id="id790388" class="indexterm"></a>
+ <a id="id790402" class="indexterm"></a>
+ If you are upgrading from the Red Hat Secure Web Server, your old key (<code class="filename">httpsd.key</code>) and certificate (<code class="filename">httpsd.crt</code>) are located in <code class="filename">/etc/httpd/conf/</code>. Move and rename your key and certificate so that the secure server can use them. Use the following two commands to move and rename your key and certificate files:
+ </div><pre class="screen">
+<code class="command">mv /etc/httpd/conf/httpsd.key /etc/pki/tls/private/server.key mv /etc/httpd/conf/httpsd.crt /etc/pki/tls/certs/server.crt</code>
+</pre><div class="para">
+ Then, start your secure server with the command:
+ </div><pre class="screen">
+<code class="command">/sbin/service httpd start</code>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-secureserver-overview-certs.html"><strong>Prev</strong>11.8.2. An Overview of Certificates and Security</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-secureserver-certs.html"><strong>Next</strong>11.8.4. Types of Certificates</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-services-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-services-additional-resources.html
new file mode 100644
index 0000000..4f5b192
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-services-additional-resources.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Controlling_Access_to_Services.html" title="Chapter 6. Controlling Access to Services" /><link rel="prev" href="s1-services-running.html" title="6.3. Running the Services" /><link rel="next" href="s2-services-additional-resources-books.html" title="6.4.2. Related Books" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to v
iew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="6.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">6.4. Additional Resources</h2></div></div></div><div class="section" title="6.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">6.4.1. Installed Documentation</h3></div></div></div><div class="variablelist"><dl><dt><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><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><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><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>6.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>6.4.2. Related Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-services-configuring.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-services-configuring.html
new file mode 100644
index 0000000..acc40a2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-services-configuring.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>6.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Controlling_Access_to_Services.html" title="Chapter 6. Controlling Access to Services" /><link rel="prev" href="ch-Controlling_Access_to_Services.html" title="Chapter 6. Controlling Access to Services" /><link rel="next" href="s2-services-ntsysv.html" title="6.2.2. Using the ntsysv Utility" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.htm
l">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_Services.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="6.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">6.2. Configuring the Services</h2></div></div></div><div class="section" title="6.2.1. Using the Service Configuration Utility" id="s2-services-serviceconf"><div class="titlepag
e"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-serviceconf">6.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="id824540" class="indexterm"></a><a id="id824558" 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 6.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 6.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 6.2. Possible Service States">Table 6.2, “Possible Service States”</a> for a complete list of used icons and an explanation of their meaning.
+ </div><div class="table" title="Table 6.2. Possible Service States" id="tab-services-serviceconf-states"><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><h6>Table 6.2. Possible Service States</h6></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 6.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 6.2. Authentication Query</h6></div><br class="figure-break" /><div class="section" title="6.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">6.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="6.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">6.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="6.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">6.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="6.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">6.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="6.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">6.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="6.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">6.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 6. 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>6.2.2. Using the ntsysv Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-services-running.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-services-running.html
new file mode 100644
index 0000000..0f773de
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-services-running.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>6.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Controlling_Access_to_Services.html" title="Chapter 6. Controlling Access to Services" /><link rel="prev" href="s2-services-chkconfig.html" title="6.2.3. Using the chkconfig Utility" /><link rel="next" href="s1-services-additional-resources.html" title="6.4. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an if
rame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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>Prev</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="6.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">6.3. Running the Services</h2></div></div></div><div class="section" title="6.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">6.3.1. Using the <span class="application"><strong>service</strong></span> Utility</h3></div></div></div><a id="id995475" class="indexterm"></a><a id="id995493" 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"><h2>Tip</h2><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="6.2.1. Using the Service Configuration Utility">Section 6.2.1, “Using the <span class="application"><strong>Service Configuration</strong></span> Utility”</a> for more information.
+ </div></div><div class="section" title="6.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">6.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="6.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">6.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="6.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">6.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="6.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">6.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 6.4. Checking the status of httpd" id="ex-services-running-checking-single"><div class="example-contents"><pre class="screen">~]# <code class="command">service httpd status</code>
+httpd (pid 7474) is running...</pre></div><h6>Example 6.4. Checking the status of <span class="application">httpd</span></h6></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 6.5. Checking the status of all services" id="ex-services-running-checking-all"><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><h6>Example 6.5. Checking the status of all services</h6></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>6.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>6.4. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ssh-beyondshell.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ssh-beyondshell.html
new file mode 100644
index 0000000..cfb583b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ssh-beyondshell.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>8.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 8. OpenSSH" /><link rel="prev" href="s2-ssh-clients-sftp.html" title="8.3.3. Using the sftp Utility" /><link rel="next" href="s2-ssh-beyondshell-tcpip.html" title="8.4.2. Port Forwarding" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe displ
ay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="8.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">8.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="8.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">8.4.1. X11 Forwarding</h3></div></div></div><a id="id927027" 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>8.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>8.4.2. Port Forwarding</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ssh-clients.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ssh-clients.html
new file mode 100644
index 0000000..cc48272
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ssh-clients.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>8.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 8. OpenSSH" /><link rel="prev" href="s2-ssh-configuration-keypairs.html" title="8.2.4. Using a Key-Based Authentication" /><link rel="next" href="s2-ssh-clients-scp.html" title="8.3.2. Using the scp Utility" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable i
frame display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="8.3. OpenSSH Clients" id="s1-ssh-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ssh-clients">8.3. OpenSSH Clients</h2></div></div></div><a id="id727912" class="indexterm"></a><div class="note"><h2>Note: Make Sure You Have Relevant Packages Installed</h2><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 class="section" title="8.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">8.3.1. Using the <code class="command">ssh</code> Utility</h3></div></div></div><a id="id945911" class="indexterm"></a><a id="id945927" 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"><h2>Important</h2><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 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>8.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>8.3.2. Using the scp Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ssh-configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ssh-configuration.html
new file mode 100644
index 0000000..b5c2e2d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-ssh-configuration.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>8.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 8. OpenSSH" /><link rel="prev" href="ch-OpenSSH.html" title="Chapter 8. OpenSSH" /><link rel="next" href="s2-ssh-configuration-sshd.html" title="8.2.2. Starting an OpenSSH Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</if
rame></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-sshd.html"><strong>Next</strong></a></li></ul><div class="section" title="8.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">8.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="8.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">8.2.1. Configuration Files</h3></div></div></div><a id="id757463" 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="id757495" 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 8.1. System-wide configuration files">Table 8.1, “System-wide configuration files”</a> for a description of its content.
+ </div><div class="table" title="Table 8.1. System-wide configuration files" id="table-ssh-configuration-configs-system"><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><h6>Table 8.1. System-wide configuration files</h6></div><br class="table-break" /><a id="id919245" 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 8.2. User-specific configuration files">Table 8.2, “User-specific configuration files”</a> for a description of its content.
+ </div><div class="table" title="Table 8.2. User-specific configuration files" id="table-ssh-configuration-configs-user"><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><h6>Table 8.2. User-specific configuration files</h6></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 8. 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>8.2.2. Starting an OpenSSH Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysconfig-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysconfig-additional-resources.html
new file mode 100644
index 0000000..5287588
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysconfig-additional-resources.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="chap-Date_and_Time_Configuration.html" title="Chapter 19. Date and Time Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../.
./toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="chap-Date_and_Time_Configuration.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="id811751" 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="id965479" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code><version-number></code></em>/sysconfig.txt</code> — This file contains a more authoritative listing of the files found in the <code class="filename">/etc/sysconfig/</code> directory and the configuration options available for them. The <em class="replaceable"><code><version-number></code></em> in the path to this file corresponds to the version of the <code class="command">initscripts</code> package installed.
+ </div></li></ul></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="chap-Date_and_Time_Configuration.html"><strong>Next</strong>Chapter 19. Date and Time Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysconfig-etcsysconf-dir.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysconfig-etcsysconf-dir.html
new file mode 100644
index 0000000..2a27604
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysconfig-etcsysconf-dir.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../to
c.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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>Prev</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="id912639" class="indexterm
"></a><div class="para">
+ The following directories are normally found in <code class="filename">/etc/sysconfig/</code>.
+ </div><a id="id912665" class="indexterm"></a><div class="variablelist"><dl><dt><span class="term"> <code class="filename">apm-scripts/</code> </span></dt><dd><div class="para">
+ This directory contains the APM suspend/resume script. Do not edit the files directly. If customization is necessary, create a file called <code class="filename">/etc/sysconfig/apm-scripts/apmcontinue</code> which is called at the end of the script. It is also possible to control the script by editing <code class="filename">/etc/sysconfig/apmd</code>.
+ </div></dd><dt><span class="term"> <code class="filename">cbq/</code> </span></dt><dd><div class="para">
+ <a id="id646621" 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><span class="term"> <code class="filename">networking/</code> </span></dt><dd><div class="para">
+ <a id="id646668" 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><span class="term"> <code class="filename">network-scripts/</code> </span></dt><dd><div class="para">
+ <a id="id938275" 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="filename">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">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><span class="term"> <code class="filename">rhn/</code> </span></dt><dd><div class="para">
+ <a id="id811704" 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_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-additional-resources.html
new file mode 100644
index 0000000..945f60c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-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>26.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Gathering_System_Information.html" title="Chapter 26. Gathering System Information" /><link rel="prev" href="s1-sysinfo-hardware.html" title="26.4. Hardware" /><link rel="next" href="ch-OProfile.html" title="Chapter 27. OProfile" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable i
frame display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-OProfile.html"><strong>Next</strong></a></li></ul><div class="section" title="26.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">26.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="26.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">26.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 — Type <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 — type <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 — Type <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 — Type <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 — Type <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="id919573" 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>26.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-OProfile.html"><strong>Next</strong>Chapter 27. OProfile</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-filesystems.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-filesystems.html
new file mode 100644
index 0000000..d01009a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-filesystems.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>26.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Gathering_System_Information.html" title="Chapter 26. Gathering System Information" /><link rel="prev" href="s1-sysinfo-memory-usage.html" title="26.2. Memory Usage" /><link rel="next" href="s1-sysinfo-hardware.html" title="26.4. Hardware" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable
iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="26.3. File Systems" id="s1-sysinfo-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-filesystems">26.3. File Systems</h2></div></div></div><a id="id671607" class="indexterm"></a><a id="id1014218" class="indexterm"></a><a id="id1014228" class="indexterm"></a><div class="para">
+ The <code class="command">df</code> command reports the system's disk space usage. If you type 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/VolGroup00-LogVol00 11675568 6272120 4810348 57% / /dev/sda1 100691 9281 86211 10% /boot none 322856 0 322856 0% /dev/shm</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/VolGroup00-LogVol00 12G 6.0G 4.6G 57% / /dev/sda1 99M 9.1M 85M 10% /boot none 316M 0 316M 0% /dev/shm</pre><a id="id1014277" class="indexterm"></a><a id="id1014298" 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="id1014319" 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 type <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>System</strong></span> > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>System Monitor</strong></span> or type <code class="command">gnome-system-monitor</code> at a shell prompt (such as an XTerm). 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 26.3. GNOME System Monitor - File Systems" id="fig-sysinfo-filesystems"><div class="figure-contents"><div class="mediaobject"><img src="images/gnome-system-monitor-filesystems.png" width="444" alt="GNOME System Monitor - File Systems" /><div class="longdesc"><div class="para">
+ File systems tab of the gnome-system-monitor
+ </div></div></div></div><h6>Figure 26.3. <span class="application">GNOME System Monitor - File Systems</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>26.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>26.4. Hardware</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-hardware.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-hardware.html
new file mode 100644
index 0000000..7e5e24a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-hardware.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>26.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Gathering_System_Information.html" title="Chapter 26. Gathering System Information" /><link rel="prev" href="s1-sysinfo-filesystems.html" title="26.3. File Systems" /><link rel="next" href="s1-sysinfo-additional-resources.html" title="26.5. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your
browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="26.4. Hardware" id="s1-sysinfo-hardware"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-hardware">26.4. Hardware</h2></div></div></div><a id="id957315" class="indexterm"></a><a id="id957329" class="indexterm"></a><a id="id957342" class="indexterm"></a><a id="id957356" 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 26.4. Hardware Browser">Figure 26.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 26.4. Hardware Browser" id="sysinfo-hwbrowser-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/hwbrowser.png" width="444" alt="Hardware Browser" /><div class="longdesc"><div class="para">
+ hwbrowser
+ </div></div></div></div><h6>Figure 26.4. <span class="application">Hardware Browser</span> </h6></div><br class="figure-break" /><a id="id957440" class="indexterm"></a><a id="id957454" 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 26.5. Device Manager" id="sysinfo-devicemngr-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/devicemngr.png" width="444" alt="Device Manager" /><div class="longdesc"><div class="para">
+ Device Manager
+ </div></div></div></div><h6>Figure 26.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:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06) 00:00.1 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06) 00:01.0 VGA compatible controller: S3 Inc. Savage 4 (rev 04) 00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08) 00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 50) 00:0f.1 IDE interface: ServerWorks OSB4 IDE Controller 00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 04) 01:03.0 SCSI storage controller: Adaptec AIC-7892P U160/m (rev 02) 01:05.0 RAID bus controller: IBM ServeRAID Controller</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>26.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>26.5. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-memory-usage.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-memory-usage.html
new file mode 100644
index 0000000..8695c81
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-sysinfo-memory-usage.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>26.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Gathering_System_Information.html" title="Chapter 26. Gathering System Information" /><link rel="prev" href="ch-Gathering_System_Information.html" title="Chapter 26. Gathering System Information" /><link rel="next" href="s1-sysinfo-filesystems.html" title="26.3. File Systems" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to v
iew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>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="26.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">26.2. Memory Usage</h2></div></div></div><a id="id671453" class="indexterm"></a><a id="id671466" class="indexterm"></a><a id="id671476" class="indexterm"></a><a id="id671485" 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: 645712 549720 95992 0 176248 224452 -/+ buffers/cache: 149020 496692 Swap: 1310712 0 1310712</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: 630 536 93 0 172 219 -/+ buffers/cache: 145 485 Swap: 1279 0 1279</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, go to <span class="guimenu"><strong>System</strong></span> > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>System Monitor</strong></span> or type <code class="command">gnome-system-monitor</code> at a shell prompt (such as an XTerm). Click on the <span class="guilabel"><strong>Resources</strong></span> tab.
+ </div><div class="figure" title="Figure 26.2. GNOME System Monitor - Resources tab" id="fig-sysinfo-memory"><div class="figure-contents"><div class="mediaobject"><img src="images/gnome-system-monitor-memory.png" width="444" 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 26.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 26. 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>26.3. File Systems</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-use-new-key.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-use-new-key.html
new file mode 100644
index 0000000..ef962da
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-use-new-key.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.8.6. How to configure the server to use the new key</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-httpd-secure-server.html" title="11.8. Apache HTTP Secure Server Configuration" /><link rel="prev" href="s2-secureserver-generatingkey.html" title="11.8.5. Generating a Key" /><link rel="next" href="s1-apache-additional-resources.html" title="11.9. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.h
tml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-secureserver-generatingkey.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="11.8.6. How to configure the server to use the new key" id="s1-use-new-key"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-use-new-key">11.8.6. How to configure the server to use the new key</h3></div></div></div><a id="id785934" class="indexterm"></a><div class="para">
+ The steps to configure the Apache HTTP Server to use the new key are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Obtain the signed certificate from the CA after submitting the CSR.
+ </div></li><li class="listitem"><div class="para">
+ Copy the certificate to the path, for example <code class="filename">/etc/pki/tls/certs/www.example.com.crt</code>
+ </div></li><li class="listitem"><div class="para">
+ Edit <code class="filename">/etc/httpd/conf.d/ssl.conf</code>. Change the SSLCertificateFile and SSLCertificateKey lines to be.
+ </div><pre class="screen">
+SSLCertificateFile /etc/pki/tls/certs/www.example.com.crt
+SSLCertificateKeyFile /etc/pki/tls/private/www.example.com.key
+</pre><div class="para">
+ where the "www.example.com" part should match the argument passed on the <code class="command">genkey</code> command.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-secureserver-generatingkey.html"><strong>Prev</strong>11.8.5. Generating a Key</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-additional-resources.html"><strong>Next</strong>11.9. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-additional-resources.html
new file mode 100644
index 0000000..ad941d5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-additional-resources.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ers_and_Groups.html" title="Chapter 22. Users and Groups" /><link rel="prev" href="s1-users-groups-shadow-utilities.html" title="22.6. Shadow Passwords" /><link rel="next" href="ch-Printer_Configuration.html" title="Chapter 23. Printer Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your b
rowser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Printer_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="22.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">22.7. Additional Resources</h2></div></div></div><a id="id964688" class="indexterm"></a><a id="id964702" 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="22.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">22.7.1. Installed Documentation</h3></div></div></div><a id="id964730" class="indexterm"></a><a id="id964749" 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><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><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>22.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-Printer_Configuration.html"><strong>Next</strong>Chapter 23. Printer Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-private-groups.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-private-groups.html
new file mode 100644
index 0000000..4f49309
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-private-groups.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>22.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ers_and_Groups.html" title="Chapter 22. Users and Groups" /><link rel="prev" href="s1-users-groups-standard-groups.html" title="22.4. Standard Groups" /><link rel="next" href="s1-users-groups-shadow-utilities.html" title="22.6. Shadow Passwords" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="next"><a accesskey="n" href="s1-users-groups-shadow-utilities.html"><strong>Next</strong></a></li></ul><div class="section" title="22.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">22.5. User Private Groups</h2></div></div></div><a id="id953402" class="indexterm"></a><a id="id953416" class="indexterm"></a><a id="id953431" class="indexterm"></a><a id="id953453" class="indexterm"></a><div c
lass="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="22.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">22.5.1. Group Directories</h3></div></div></div><a id="id953536" class="indexterm"></a><a id="id953551" 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>22.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>22.6. Shadow Passwords</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-shadow-utilities.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-shadow-utilities.html
new file mode 100644
index 0000000..ab1e258
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-shadow-utilities.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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ers_and_Groups.html" title="Chapter 22. Users and Groups" /><link rel="prev" href="s1-users-groups-private-groups.html" title="22.5. User Private Groups" /><link rel="next" href="s1-users-groups-additional-resources.html" title="22.7. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your
browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="22.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">22.6. Shadow Passwords</h2></div></div></div><a id="id985067" class="indexterm"></a><a id="id985082" 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>22.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>22.7. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-standard-groups.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-standard-groups.html
new file mode 100644
index 0000000..a93bfd4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-standard-groups.html
@@ -0,0 +1,322 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ers_and_Groups.html" title="Chapter 22. Users and Groups" /><link rel="prev" href="s1-users-groups-standard-users.html" title="22.3. Standard Users" /><link rel="next" href="s1-users-groups-private-groups.html" title="22.5. User Private Groups" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or en
able iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="next"><a accesskey="n" href="s1-users-groups-private-groups.html"><strong>Next</strong></a></li></ul><div class="section" title="22.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">22.4. Standard Groups</h2></div></div></div><a id="id899485" class="indexterm"></a><div class="para">
+ <a class="xref" href="s1-users-groups-standard-groups.html#tb-users-groups-group-etc" title="Table 22.5. Standard Groups">Table 22.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 22.5. Standard Groups" id="tb-users-groups-group-etc"><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, exim
+ </td></tr><tr><td>
+ news
+ </td><td>
+ 13
+ </td><td>
+ news
+ </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>
+ 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>
+ nobody
+ </td><td>
+ 99
+ </td><td>
+ </td></tr><tr><td>
+ users
+ </td><td>
+ 100
+ </td><td>
+ </td></tr><tr><td>
+ rpm
+ </td><td>
+ 37
+ </td><td>
+ </td></tr><tr><td>
+ utmp
+ </td><td>
+ 22
+ </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>
+ dbus
+ </td><td>
+ 81
+ </td><td>
+ </td></tr><tr><td>
+ ntp
+ </td><td>
+ 38
+ </td><td>
+ </td></tr><tr><td>
+ canna
+ </td><td>
+ 39
+ </td><td>
+ </td></tr><tr><td>
+ nscd
+ </td><td>
+ 28
+ </td><td>
+ </td></tr><tr><td>
+ rpc
+ </td><td>
+ 32
+ </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>
+ mailman
+ </td><td>
+ 41
+ </td><td>
+ </td></tr><tr><td>
+ exim
+ </td><td>
+ 93
+ </td><td>
+ </td></tr><tr><td>
+ named
+ </td><td>
+ 25
+ </td><td>
+ </td></tr><tr><td>
+ postgres
+ </td><td>
+ 26
+ </td><td>
+ </td></tr><tr><td>
+ sshd
+ </td><td>
+ 74
+ </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>
+ pvm
+ </td><td>
+ 24
+ </td><td>
+ </td></tr><tr><td>
+ apache
+ </td><td>
+ 48
+ </td><td>
+ </td></tr><tr><td>
+ xfs
+ </td><td>
+ 43
+ </td><td>
+ </td></tr><tr><td>
+ gdm
+ </td><td>
+ 42
+ </td><td>
+ </td></tr><tr><td>
+ htt
+ </td><td>
+ 101
+ </td><td>
+ </td></tr><tr><td>
+ mysql
+ </td><td>
+ 27
+ </td><td>
+ </td></tr><tr><td>
+ webalizer
+ </td><td>
+ 67
+ </td><td>
+ </td></tr><tr><td>
+ mailnull
+ </td><td>
+ 47
+ </td><td>
+ </td></tr><tr><td>
+ smmsp
+ </td><td>
+ 51
+ </td><td>
+ </td></tr><tr><td>
+ squid
+ </td><td>
+ 23
+ </td><td>
+ </td></tr><tr><td>
+ ldap
+ </td><td>
+ 55
+ </td><td>
+ </td></tr><tr><td>
+ netdump
+ </td><td>
+ 34
+ </td><td>
+ </td></tr><tr><td>
+ pcap
+ </td><td>
+ 77
+ </td><td>
+ </td></tr><tr><td>
+ quaggavt
+ </td><td>
+ 102
+ </td><td>
+ </td></tr><tr><td>
+ quagga
+ </td><td>
+ 92
+ </td><td>
+ </td></tr><tr><td>
+ radvd
+ </td><td>
+ 75
+ </td><td>
+ </td></tr><tr><td>
+ slocate
+ </td><td>
+ 21
+ </td><td>
+ </td></tr><tr><td>
+ wnn
+ </td><td>
+ 49
+ </td><td>
+ </td></tr><tr><td>
+ dovecot
+ </td><td>
+ 97
+ </td><td>
+ </td></tr><tr><td>
+ radiusd
+ </td><td>
+ 95
+ </td><td>
+ </td></tr></tbody></table></div><h6>Table 22.5. Standard Groups</h6></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>22.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>22.5. User Private Groups</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-standard-users.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-standard-users.html
new file mode 100644
index 0000000..fc7ca81
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-groups-standard-users.html
@@ -0,0 +1,514 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ers_and_Groups.html" title="Chapter 22. Users and Groups" /><link rel="prev" href="s2-redhat-config-users-process.html" title="22.2.2. Explaining the Process" /><link rel="next" href="s1-users-groups-standard-groups.html" title="22.4. Standard Groups" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="22.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">22.3. Standard Users</h2></div></div></div><a id="id876979" class="indexterm"></a><a id="id876994" class="indexterm"></a><div class="para">
+ <a class="xref" href="s1-users-groups-standard-users.html#tb-users-groups-group-use" title="Table 22.4. Standard Users">Table 22.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="22.4. Standard Groups">Section 22.4, “Standard Groups”</a> for a listing of standard groups.
+ </div><div class="table" title="Table 22.4. Standard Users" id="tb-users-groups-group-use"><div class="table-contents"><table summary="Standard Users" border="1"><colgroup><col width="29%" /><col width="10%" /><col width="10%" /><col width="30%" /><col width="21%" /></colgroup><thead><tr><th>
+ User
+ </th><th>
+ UID
+ </th><th>
+ GID
+ </th><th>
+ Home Directory
+ </th><th>
+ Shell
+ </th></tr></thead><tbody><tr><td>
+ root
+ </td><td>
+ 0
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/root</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ bin
+ </td><td>
+ 1
+ </td><td>
+ 1
+ </td><td>
+ <code class="filename">/bin</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ daemon
+ </td><td>
+ 2
+ </td><td>
+ 2
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ adm
+ </td><td>
+ 3
+ </td><td>
+ 4
+ </td><td>
+ <code class="filename">/var/adm</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ lp
+ </td><td>
+ 4
+ </td><td>
+ 7
+ </td><td>
+ <code class="filename">/var/spool/lpd</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ sync
+ </td><td>
+ 5
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/bin/sync</code>
+ </td></tr><tr><td>
+ shutdown
+ </td><td>
+ 6
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/sbin/shutdown</code>
+ </td></tr><tr><td>
+ halt
+ </td><td>
+ 7
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/sbin</code>
+ </td><td>
+ <code class="filename">/sbin/halt</code>
+ </td></tr><tr><td>
+ mail
+ </td><td>
+ 8
+ </td><td>
+ 12
+ </td><td>
+ <code class="filename">/var/spool/mail</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ news
+ </td><td>
+ 9
+ </td><td>
+ 13
+ </td><td>
+ <code class="filename">/etc/news</code>
+ </td><td>
+ </td></tr><tr><td>
+ uucp
+ </td><td>
+ 10
+ </td><td>
+ 14
+ </td><td>
+ <code class="filename">/var/spool/uucp</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ operator
+ </td><td>
+ 11
+ </td><td>
+ 0
+ </td><td>
+ <code class="filename">/root</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ games
+ </td><td>
+ 12
+ </td><td>
+ 100
+ </td><td>
+ <code class="filename">/usr/games</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ gopher
+ </td><td>
+ 13
+ </td><td>
+ 30
+ </td><td>
+ <code class="filename">/var/gopher</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ ftp
+ </td><td>
+ 14
+ </td><td>
+ 50
+ </td><td>
+ <code class="filename">/var/ftp</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ nobody
+ </td><td>
+ 99
+ </td><td>
+ 99
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ rpm
+ </td><td>
+ 37
+ </td><td>
+ 37
+ </td><td>
+ <code class="filename">/var/lib/rpm</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ vcsa
+ </td><td>
+ 69
+ </td><td>
+ 69
+ </td><td>
+ <code class="filename">/dev</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ dbus
+ </td><td>
+ 81
+ </td><td>
+ 81
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ ntp
+ </td><td>
+ 38
+ </td><td>
+ 38
+ </td><td>
+ <code class="filename">/etc/ntp</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ canna
+ </td><td>
+ 39
+ </td><td>
+ 39
+ </td><td>
+ <code class="filename">/var/lib/canna</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ nscd
+ </td><td>
+ 28
+ </td><td>
+ 28
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ rpc
+ </td><td>
+ 32
+ </td><td>
+ 32
+ </td><td>
+ <code class="filename">/var/lib/rpcbind</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ postfix
+ </td><td>
+ 89
+ </td><td>
+ 89
+ </td><td>
+ <code class="filename">/var/spool/postfix</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ mailman
+ </td><td>
+ 41
+ </td><td>
+ 41
+ </td><td>
+ <code class="filename">/var/mailman</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ named
+ </td><td>
+ 25
+ </td><td>
+ 25
+ </td><td>
+ <code class="filename">/var/named</code>
+ </td><td>
+ <code class="command">/bin/false</code>
+ </td></tr><tr><td>
+ amanda
+ </td><td>
+ 33
+ </td><td>
+ 6
+ </td><td>
+ <code class="filename">var/lib/amanda/</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ postgres
+ </td><td>
+ 26
+ </td><td>
+ 26
+ </td><td>
+ <code class="filename">/var/lib/pgsql</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ exim
+ </td><td>
+ 93
+ </td><td>
+ 93
+ </td><td>
+ <code class="filename">/var/spool/exim</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ sshd
+ </td><td>
+ 74
+ </td><td>
+ 74
+ </td><td>
+ <code class="filename">/var/empty/sshd</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ rpcuser
+ </td><td>
+ 29
+ </td><td>
+ 29
+ </td><td>
+ <code class="filename">/var/lib/nfs</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ nsfnobody
+ </td><td>
+ 65534
+ </td><td>
+ 65534
+ </td><td>
+ <code class="filename">/var/lib/nfs</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td></tr><tr><td>
+ pvm
+ </td><td>
+ 24
+ </td><td>
+ 24
+ </td><td>
+ <code class="filename">/usr/share/pvm3</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ apache
+ </td><td>
+ 48
+ </td><td>
+ 48
+ </td><td>
+ <code class="filename">/var/www</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ xfs
+ </td><td>
+ 43
+ </td><td>
+ 43
+ </td><td>
+ <code class="filename">/etc/X11/fs</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ gdm
+ </td><td>
+ 42
+ </td><td>
+ 42
+ </td><td>
+ <code class="filename">/var/gdm</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ htt
+ </td><td>
+ 100
+ </td><td>
+ 101
+ </td><td>
+ <code class="filename">/usr/lib/im</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ mysql
+ </td><td>
+ 27
+ </td><td>
+ 27
+ </td><td>
+ <code class="filename">/var/lib/mysql</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ webalizer
+ </td><td>
+ 67
+ </td><td>
+ 67
+ </td><td>
+ <code class="filename">/var/www/usage</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ mailnull
+ </td><td>
+ 47
+ </td><td>
+ 47
+ </td><td>
+ <code class="filename">/var/spool/mqueue</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ smmsp
+ </td><td>
+ 51
+ </td><td>
+ 51
+ </td><td>
+ <code class="filename">/var/spool/mqueue</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ squid
+ </td><td>
+ 23
+ </td><td>
+ 23
+ </td><td>
+ <code class="filename">/var/spool/squid</code>
+ </td><td>
+ <code class="filename">/sbin/nologin</code>
+ </td></tr><tr><td>
+ ldap
+ </td><td>
+ 55
+ </td><td>
+ 55
+ </td><td>
+ <code class="filename">/var/lib/ldap</code>
+ </td><td>
+ <code class="command">/bin/false</code>
+ </td></tr><tr><td>
+ netdump
+ </td><td>
+ 34
+ </td><td>
+ 34
+ </td><td>
+ <code class="filename">/var/crash</code>
+ </td><td>
+ <code class="command">/bin/bash</code>
+ </td></tr><tr><td>
+ pcap
+ </td><td>
+ 77
+ </td><td>
+ 77
+ </td><td>
+ <code class="filename">/var/arpwatch</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ radiusd
+ </td><td>
+ 95
+ </td><td>
+ 95
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="command">/bin/false</code>
+ </td></tr><tr><td>
+ radvd
+ </td><td>
+ 75
+ </td><td>
+ 75
+ </td><td>
+ <code class="filename">/</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ quagga
+ </td><td>
+ 92
+ </td><td>
+ 92
+ </td><td>
+ <code class="filename">/var/run/quagga</code>
+ </td><td>
+ <code class="command">/sbin/login</code>
+ </td></tr><tr><td>
+ wnn
+ </td><td>
+ 49
+ </td><td>
+ 49
+ </td><td>
+ <code class="filename">/var/lib/wnn</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr><tr><td>
+ dovecot
+ </td><td>
+ 97
+ </td><td>
+ 97
+ </td><td>
+ <code class="filename">/usr/libexec/dovecot</code>
+ </td><td>
+ <code class="command">/sbin/nologin</code>
+ </td></tr></tbody></table></div><h6>Table 22.4. Standard Users</h6></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>22.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>22.4. Standard Groups</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-tools.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-tools.html
new file mode 100644
index 0000000..f81d5eb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-users-tools.html
@@ -0,0 +1,194 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ers_and_Groups.html" title="Chapter 22. Users and Groups" /><link rel="prev" href="ers_and_Groups.html" title="Chapter 22. Users and Groups" /><link rel="next" href="s2-redhat-config-users-process.html" title="22.2.2. Explaining the Process" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your
browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ers_and_Groups.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-redhat-config-users-process.html"><strong>Next</strong></a></li></ul><div class="section" title="22.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">22.2. User and Group Management Tools</h2></div></div></div><a id="id598642" class="indexterm"></a><a id="id598664" class="indexterm"></a><a id="id598685" class="indexterm"></a><a id="id598707" 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="ers_and_Groups.html#s1-users-configui" title="22.1. User and Group Configuration">Section 22.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="22.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">22.2.1. Command Line Configuration</h3></div></div></div><a id="id996138" class="indexterm"></a><a id="id996153" class="indexterm"></a><a id="id996171" 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>Adding a User</h4><div class="para">
+ To add a user to the system:
+ </div><a id="id996198" 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="id813089" 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 22.1. useradd Command Line Options">Table 22.1, “ <code class="command">useradd</code> Command Line Options”</a>.
+ </div><div class="table" title="Table 22.1. useradd Command Line Options" id="table-useradd-options"><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><h6>Table 22.1. <code class="command">useradd</code> Command Line Options</h6></div><br class="table-break" /><h4>Adding a Group</h4><a id="id821536" class="indexterm"></a><a id="id821556" 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 22.2. groupadd Command Line Options">Table 22.2, “<code class="command">groupadd</code> Command Line Options”</a>.
+ </div><div class="table" title="Table 22.2. groupadd Command Line Options" id="table-groupadd-options"><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><h6>Table 22.2. <code class="command">groupadd</code> Command Line Options</h6></div><br class="table-break" /><h4>Password Aging</h4><a id="id677890" class="indexterm"></a><a id="id677904" class="indexterm"></a><a id="id677919" class="indexterm"></a><a id="id677929" class="indexterm"></a><a id="id677948" 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 22.3. chage Command Line Options">Table 22.3, “<code class="command">chage</code> Command Line Options”</a>, followed by the username.
+ </div><div class="important"><h2>Important</h2><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="22.6. Shadow Passwords">Section 22.6, “Shadow Passwords”</a>.
+ </div></div><div class="table" title="Table 22.3. chage Command Line Options" id="table-chage-options"><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><h6>Table 22.3. <code class="command">chage</code> Command Line Options</h6></div><br class="table-break" /><div class="note"><h2>Tip</h2><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 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"><h2>Caution</h2><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></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="ers_and_Groups.html"><strong>Prev</strong>Chapter 22. 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>22.2.2. Explaining the Process</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-additional-resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-additional-resources.html
new file mode 100644
index 0000000..a281d30
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-additional-resources.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_X_Window_System.html" title="Chapter 21. The X Window System" /><link rel="prev" href="s2-x-runlevels-5.html" title="21.5.2. Runlevel 5" /><link rel="next" href="s2-x-useful-websites.html" title="21.6.2. Useful Websites" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-runlevels-5.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-x-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" title="21.6. Additional Resources" id="s1-x-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-additional-resources">21.6. Additional Resources</h2></div></div></div><a id="id937296" class="indexterm"></a><div class="para">
+ There is a large amount of detailed information available about the X server, the clients that connect to it, and the assorted desktop environments and window managers.
+ </div><div class="section" title="21.6.1. Installed Documentation" id="s2-x-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-installed-documentation">21.6.1. Installed Documentation</h3></div></div></div><a id="id853625" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/X11/doc/</code> — contains detailed documentation on the X Window System architecture, as well as how to get additional information about the Xorg project as a new user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man xorg.conf</code> — Contains information about the <code class="filename">xorg.conf</code> configuration files, including the meaning and syntax for the different sections within the files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man Xorg</code> — Describes the <code class="command">Xorg</code> display server.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x-runlevels-5.html"><strong>Prev</strong>21.5.2. Runlevel 5</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-x-useful-websites.html"><strong>Next</strong>21.6.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-clients.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-clients.html
new file mode 100644
index 0000000..72b8eb7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-clients.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>21.2. Desktop Environments and Window Managers</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_X_Window_System.html" title="Chapter 21. The X Window System" /><link rel="prev" href="ch-The_X_Window_System.html" title="Chapter 21. The X Window System" /><link rel="next" href="s2-x-clients-winmanagers.html" title="21.2.2. Window Managers" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to vi
ew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_X_Window_System.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-x-clients-winmanagers.html"><strong>Next</strong></a></li></ul><div class="section" title="21.2. Desktop Environments and Window Managers" id="s1-x-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-clients">21.2. Desktop Environments and Window Managers</h2></div></div></div><a id="id730774" class="indexterm"></a><div class="para">
+ Once an X server is running, X client applications can connect to it and create a GUI for the user. A range of GUIs are possible with Fedora, from the rudimentary <em class="firstterm">Tab Window Manager</em> to the highly developed and interactive <em class="firstterm">GNOME</em> desktop environment that most Fedora users are familiar with.
+ </div><div class="para">
+ To create the latter, more comprehensive GUI, two main classes of X client application must connect to the X server: a <em class="firstterm">desktop environment</em> and a <em class="firstterm">window manager</em>.
+ </div><div class="section" title="21.2.1. Desktop Environments" id="s2-x-clients-desktop"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-clients-desktop">21.2.1. Desktop Environments</h3></div></div></div><a id="id730822" class="indexterm"></a><a id="id973247" class="indexterm"></a><a id="id973260" class="indexterm"></a><a id="id973274" class="indexterm"></a><a id="id973287" class="indexterm"></a><a id="id973305" class="indexterm"></a><div class="para">
+ A desktop environment integrates various X clients to create a common graphical user environment and development platform.
+ </div><div class="para">
+ Desktop environments have advanced features allowing X clients and other running processes to communicate with one another, while also allowing all applications written to work in that environment to perform advanced tasks, such as drag and drop operations.
+ </div><div class="para">
+ Fedora provides two desktop environments:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>GNOME</em></span> — The default desktop environment for Fedora based on the GTK+ 2 graphical toolkit.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em> <em class="firstterm">KDE</em> </em></span> — An alternative desktop environment based on the Qt 4 graphical toolkit.
+ </div></li></ul></div><div class="para">
+ Both GNOME and KDE have advanced productivity applications, such as word processors, spreadsheets, and Web browsers; both also provide tools to customize the look and feel of the GUI. Additionally, if both the GTK+ 2 and the Qt libraries are present, KDE applications can run in GNOME and vice-versa.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-The_X_Window_System.html"><strong>Prev</strong>Chapter 21. The X Window 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-x-clients-winmanagers.html"><strong>Next</strong>21.2.2. Window Managers</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-fonts.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-fonts.html
new file mode 100644
index 0000000..c00bc6d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-fonts.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>21.4. Fonts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_X_Window_System.html" title="Chapter 21. The X Window System" /><link rel="prev" href="s1-x-server-configuration.html" title="21.3. X Server Configuration Files" /><link rel="next" href="s2-x-fonts-core.html" title="21.4.2. Core X Font System" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable
iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-server-configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-x-fonts-core.html"><strong>Next</strong></a></li></ul><div class="section" title="21.4. Fonts" id="s1-x-fonts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-fonts">21.4. Fonts</h2></div></div></div><a id="id999079" class="indexterm"></a><div class="para">
+ Fedora uses two subsystems to manage and display fonts under X: <em class="firstterm">Fontconfig</em> and <code class="command">xfs</code>.
+ </div><div class="para">
+ The newer Fontconfig font subsystem simplifies font management and provides advanced display features, such as anti-aliasing. This system is used automatically for applications programmed using the Qt 3 or GTK+ 2 graphical toolkit.
+ </div><div class="para">
+ For compatibility, Fedora includes the original font subsystem, called the core X font subsystem. This system, which is over 15 years old, is based around the <em class="firstterm">X Font Server</em> (<em class="firstterm">xfs</em>).
+ </div><div class="para">
+ This section discusses how to configure fonts for X using both systems.
+ </div><div class="section" title="21.4.1. Fontconfig" id="s2-x-fonts-fontconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-fonts-fontconfig">21.4.1. Fontconfig</h3></div></div></div><a id="id999143" class="indexterm"></a><a id="id999161" class="indexterm"></a><a id="id999180" class="indexterm"></a><a id="id999198" class="indexterm"></a><div class="para">
+ The Fontconfig font subsystem allows applications to directly access fonts on the system and use Xft or other rendering mechanisms to render Fontconfig fonts with advanced anti-aliasing. Graphical applications can use the Xft library with Fontconfig to draw text to the screen.
+ </div><div class="para">
+ Over time, the Fontconfig/Xft font subsystem replaces the core X font subsystem.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ The Fontconfig font subsystem does not yet work for <span class="application"><strong>OpenOffice.org</strong></span>, which uses its own font rendering technology.
+ </div></div><div class="para">
+ It is important to note that Fontconfig uses the <code class="filename">/etc/fonts/fonts.conf</code> configuration file, which should not be edited by hand.
+ </div><div class="note"><h2>Tip</h2><div class="para">
+ Due to the transition to the new font system, GTK+ 1.2 applications are not affected by any changes made via the <span class="application"><strong>Font Preferences</strong></span> dialog (accessed by selecting System (on the panel) > <span class="guimenuitem"><strong>Preferences</strong></span> > <span class="guimenuitem"><strong>Fonts</strong></span>). For these applications, a font can be configured by adding the following lines to the file <code class="filename">~/.gtkrc.mine</code>:
+ </div><pre class="screen">style "user-font" {
+ fontset = "<em class="replaceable"><code><font-specification></code></em>"
+}
+
+widget_class "*" style "user-font"</pre><div class="para">
+ Replace <em class="replaceable"><code><font-specification></code></em> with a font specification in the style used by traditional X applications, such as <code class="command">-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*</code>. A full list of core fonts can be obtained by running <code class="command">xlsfonts</code> or created interactively using the <code class="command">xfontsel</code> command.
+ </div></div><div class="section" title="21.4.1.1. Adding Fonts to Fontconfig" id="s3-x-fonts-fontconfig-add"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-fonts-fontconfig-add">21.4.1.1. Adding Fonts to Fontconfig</h4></div></div></div><a id="id2002232" class="indexterm"></a><div class="para">
+ Adding new fonts to the Fontconfig subsystem is a straightforward process.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ To add fonts system-wide, copy the new fonts into the <code class="filename">/usr/share/fonts/</code> directory. It is a good idea to create a new subdirectory, such as <code class="filename">local/</code> or similar, to help distinguish between user-installed and default fonts.
+ </div><div class="para">
+ To add fonts for an individual user, copy the new fonts into the <code class="filename">.fonts/</code> directory in the user's home directory.
+ </div></li><li class="listitem"><div class="para">
+ Use the <code class="command">fc-cache</code> command to update the font information cache, as in the following example:
+ </div><pre class="screen"><code class="command">fc-cache <em class="replaceable"><code><path-to-font-directory></code></em></code></pre><div class="para">
+ In this command, replace <em class="replaceable"><code><path-to-font-directory></code></em> with the directory containing the new fonts (either <code class="filename">/usr/share/fonts/local/</code> or <code class="filename">/home/<em class="replaceable"><code><user></code></em>/.fonts/</code>).
+ </div></li></ol></div><div class="note"><h2>Tip</h2><div class="para">
+ Individual users may also install fonts graphically, by typing <code class="filename">fonts:///</code> into the <span class="application"><strong>Nautilus</strong></span> address bar, and dragging the new font files there.
+ </div></div><div class="important"><h2>Important</h2><div class="para">
+ If the font file name ends with a <code class="filename">.gz</code> extension, it is compressed and cannot be used until uncompressed. To do this, use the <code class="command">gunzip</code> command or double-click the file and drag the font to a directory in <span class="application"><strong>Nautilus</strong></span>.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x-server-configuration.html"><strong>Prev</strong>21.3. X Server 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-x-fonts-core.html"><strong>Next</strong>21.4.2. Core X Font System</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-runlevels.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-runlevels.html
new file mode 100644
index 0000000..416346a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-runlevels.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>21.5. Runlevels and X</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_X_Window_System.html" title="Chapter 21. The X Window System" /><link rel="prev" href="s2-x-fonts-core.html" title="21.4.2. Core X Font System" /><link rel="next" href="s2-x-runlevels-5.html" title="21.5.2. Runlevel 5" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display
.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-fonts-core.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-x-runlevels-5.html"><strong>Next</strong></a></li></ul><div class="section" title="21.5. Runlevels and X" id="s1-x-runlevels"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-runlevels">21.5. Runlevels and X</h2></div></div></div><a id="id760364" class="indexterm"></a><div class="para">
+ In most cases, the Fedora installer configures a machine to boot into a graphical login environment, known as <em class="firstterm">Runlevel 5</em>. It is possible, however, to boot into a text-only multi-user mode called <em class="firstterm">Runlevel 3</em> and begin an X session from there.
+ </div><div class="para">
+ For more information about runlevels, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html#s1-services-runlevels" title="6.1. Configuring the Default Runlevel">Section 6.1, “Configuring the Default Runlevel”</a>.
+ </div><div class="para">
+ The following subsections review how X starts up in both runlevel 3 and runlevel 5.
+ </div><div class="section" title="21.5.1. Runlevel 3" id="s2-x-runlevels-3"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-runlevels-3">21.5.1. Runlevel 3</h3></div></div></div><a id="id760420" class="indexterm"></a><a id="id760438" class="indexterm"></a><a id="id760457" class="indexterm"></a><a id="id760479" class="indexterm"></a><a id="id760498" class="indexterm"></a><a id="id760520" class="indexterm"></a><div class="para">
+ When in runlevel 3, the best way to start an X session is to log in and type <code class="command">startx</code>. The <code class="command">startx</code> command is a front-end to the <code class="command">xinit</code> command, which launches the X server (<code class="filename">Xorg</code>) and connects X client applications to it. Because the user is already logged into the system at runlevel 3, <code class="command">startx</code> does not launch a display manager or authenticate users. Refer to <a class="xref" href="s2-x-runlevels-5.html" title="21.5.2. Runlevel 5">Section 21.5.2, “Runlevel 5”</a> for more information about display managers.
+ </div><div class="para">
+ When the <code class="command">startx</code> command is executed, it searches for the <code class="filename">.xinitrc</code> file in the user's home directory to define the desktop environment and possibly other X client applications to run. If no <code class="filename">.xinitrc</code> file is present, it uses the system default <code class="filename">/etc/X11/xinit/xinitrc</code> file instead.
+ </div><div class="para">
+ The default <code class="command">xinitrc</code> script then searches for user-defined files and default system files, including <code class="filename">.Xresources</code>, <code class="filename">.Xmodmap</code>, and <code class="filename">.Xkbmap</code> in the user's home directory, and <code class="filename">Xresources</code>, <code class="filename">Xmodmap</code>, and <code class="filename">Xkbmap</code> in the <code class="filename">/etc/X11/</code> directory. The <code class="filename">Xmodmap</code> and <code class="filename">Xkbmap</code> files, if they exist, are used by the <code class="command">xmodmap</code> utility to configure the keyboard. The <code class="filename">Xresources</code> file is read to assign specific preference values to applications.
+ </div><div class="para">
+ After setting these options, the <code class="command">xinitrc</code> script executes all scripts located in the <code class="filename">/etc/X11/xinit/xinitrc.d/</code> directory. One important script in this directory is <code class="filename">xinput.sh</code>, which configures settings such as the default language.
+ </div><div class="para">
+ Next, the <code class="command">xinitrc</code> script attempts to execute <code class="filename">.Xclients</code> in the user's home directory and turns to <code class="filename">/etc/X11/xinit/Xclients</code> if it cannot be found. The purpose of the <code class="filename">Xclients</code> file is to start the desktop environment or, possibly, just a basic window manager. The <code class="filename">.Xclients</code> script in the user's home directory starts the user-specified desktop environment in the <code class="filename">.Xclients-default</code> file. If <code class="filename">.Xclients</code> does not exist in the user's home directory, the standard <code class="filename">/etc/X11/xinit/Xclients</code> script attempts to start another desktop environment, trying GNOME first and then KDE followed by <code class="command">twm</code>.
+ </div><div class="para">
+ When in runlevel 3, the user is returned to a text mode user session after ending an X session.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x-fonts-core.html"><strong>Prev</strong>21.4.2. Core X Font 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-x-runlevels-5.html"><strong>Next</strong>21.5.2. Runlevel 5</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-server-configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-server-configuration.html
new file mode 100644
index 0000000..d2d2a77
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s1-x-server-configuration.html
@@ -0,0 +1,266 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. X Server 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_X_Window_System.html" title="Chapter 21. The X Window System" /><link rel="prev" href="s2-x-clients-winmanagers.html" title="21.2.2. Window Managers" /><link rel="next" href="s1-x-fonts.html" title="21.4. Fonts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe d
isplay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-clients-winmanagers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-x-fonts.html"><strong>Next</strong></a></li></ul><div class="section" title="21.3. X Server Configuration Files" id="s1-x-server-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-x-server-configuration">21.3. X Server Configuration Files</h2></div></div></div><a id="id758802" class="indexterm"></a><a id="id868600" class="indexterm"></a><div class="para">
+ The X server is a single binary executable (<code class="filename">/usr/bin/Xorg</code>). Associated configuration files are stored in the <code class="filename">/etc/X11/</code> directory (as is a symbolic link — X — which points to <code class="filename">/usr/bin/Xorg</code>). The configuration file for the X server is <code class="filename">/etc/X11/xorg.conf</code>.
+ </div><div class="para">
+ The directory <code class="filename">/usr/lib/xorg/modules/</code> contains X server modules that can be loaded dynamically at runtime. By default, only some modules in <code class="filename">/usr/lib/xorg/modules/</code> are automatically loaded by the X server.
+ </div><div class="para">
+ To load optional modules, they must be specified in the X server configuration file, <code class="filename">/etc/X11/xorg.conf</code>. For more information about loading modules, refer to <a class="xref" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-modules" title="21.3.1.5. Module">Section 21.3.1.5, “ <code class="command">Module</code> ”</a>.
+ </div><div class="para">
+ When Fedora 13 is installed, the configuration files for X are created using information gathered about the system hardware during the installation process.
+ </div><div class="section" title="21.3.1. xorg.conf" id="s2-x-server-config-xorg.conf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-server-config-xorg.conf">21.3.1. <code class="filename">xorg.conf</code> </h3></div></div></div><a id="id868686" class="indexterm"></a><a id="id868708" class="indexterm"></a><a id="id868725" class="indexterm"></a><div class="para">
+ While there is rarely a need to manually edit the <code class="filename">/etc/X11/xorg.conf</code> file, it is useful to understand the various sections and optional parameters available, especially when troubleshooting.
+ </div><div class="section" title="21.3.1.1. The Structure" id="s3-x-server-config-xorg.conf-struct"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-struct">21.3.1.1. The Structure</h4></div></div></div><a id="id868764" class="indexterm"></a><a id="id729271" class="indexterm"></a><a id="id729297" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/X11/xorg.conf</code> file is comprised of many different sections which address specific aspects of the system hardware.
+ </div><div class="para">
+ Each section begins with a <code class="command">Section "<em class="replaceable"><code><section-name></code></em>"</code> line (where <em class="replaceable"><code><section-name></code></em> is the title for the section) and ends with an <code class="command">EndSection</code> line. Each section contains lines that include option names and one or more option values. These are sometimes enclosed in double quotes (<code class="command">"</code>).
+ </div><div class="para">
+ Lines beginning with a hash mark (<code class="command">#</code>) are not read by the X server and are used for human-readable comments.
+ </div><div class="para">
+ Some options within the <code class="filename">/etc/X11/xorg.conf</code> file accept a boolean switch which turns the feature on or off. Acceptable boolean values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">1</code>, <code class="command">on</code>, <code class="command">true</code>, or <code class="command">yes</code> — Turns the option on.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">0</code>, <code class="command">off</code>, <code class="command">false</code>, or <code class="command">no</code> — Turns the option off.
+ </div></li></ul></div><div class="para">
+ The following are some of the more important sections in the order in which they appear in a typical <code class="filename">/etc/X11/xorg.conf</code> file. More detailed information about the X server configuration file can be found in the <code class="filename">xorg.conf</code> man page.
+ </div></div><div class="section" title="21.3.1.2. ServerFlags" id="s3-x-server-config-xorg.conf-serverf"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-serverf">21.3.1.2. <code class="command">ServerFlags</code> </h4></div></div></div><a id="id990911" class="indexterm"></a><div class="para">
+ The optional <code class="command">ServerFlags</code> section contains miscellaneous global X server settings. Any settings in this section may be overridden by options placed in the <code class="command">ServerLayout</code> section (refer to <a class="xref" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-serverl" title="21.3.1.3. ServerLayout">Section 21.3.1.3, “ <code class="command">ServerLayout</code> ”</a> for details).
+ </div><div class="para">
+ Each entry within the <code class="command">ServerFlags</code> section is on its own line and begins with the term <code class="command">Option</code> followed by an option enclosed in double quotation marks (<code class="command">"</code>).
+ </div><div class="para">
+ The following is a sample <code class="command">ServerFlags</code> section:
+ </div><pre class="screen">Section "ServerFlags"
+ Option "DontZap" "true"
+EndSection</pre><div class="para">
+ The following lists some of the most useful options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">"DontZap" "<em class="replaceable"><code><boolean></code></em>"</code> — When the value of <em class="replaceable"><code><boolean></code></em> is set to true, this setting prevents the use of the <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Backspace</strong></span> key combination to immediately terminate the X server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">"DontZoom" "<em class="replaceable"><code><boolean></code></em>"</code> — When the value of <em class="replaceable"><code><boolean></code></em> is set to true, this setting prevents cycling through configured video resolutions using the <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Keypad-Plus</strong></span> and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Keypad-Minus</strong></span> key combinations.
+ </div></li></ul></div></div><div class="section" title="21.3.1.3. ServerLayout" id="s3-x-server-config-xorg.conf-serverl"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-serverl">21.3.1.3. <code class="command">ServerLayout</code> </h4></div></div></div><a id="id955640" class="indexterm"></a><div class="para">
+ The <code class="command">ServerLayout</code> section binds together the input and output devices controlled by the X server. At a minimum, this section must specify one output device and one input device. By default, a monitor (output device) and keyboard (input device) are specified.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">ServerLayout</code> section:
+ </div><pre class="screen">Section "ServerLayout"
+ Identifier "Default Layout"
+ Screen 0 "Screen0" 0 0
+ InputDevice "Mouse0" "CorePointer"
+ InputDevice "Keyboard0" "CoreKeyboard"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="command">ServerLayout</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Identifier</code> — Specifies a unique name for this <code class="command">ServerLayout</code> section.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Screen</code> — Specifies the name of a <code class="command">Screen</code> section to be used with the X server. More than one <code class="command">Screen</code> option may be present.
+ </div><div class="para">
+ The following is an example of a typical <code class="command">Screen</code> entry:
+ </div><pre class="screen">Screen 0 "Screen0" 0 0</pre><div class="para">
+ The first number in this example <code class="command">Screen</code> entry (<code class="command">0</code>) indicates that the first monitor connector or <em class="firstterm">head</em> on the video card uses the configuration specified in the <code class="command">Screen</code> section with the identifier <code class="command">"Screen0"</code>.
+ </div><div class="para">
+ An example of a <code class="command">Screen</code> section with the identifier <code class="command">"Screen0"</code> can be found in <a class="xref" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-screen" title="21.3.1.9. Screen">Section 21.3.1.9, “ <code class="command">Screen</code> ”</a>.
+ </div><div class="para">
+ If the video card has more than one head, another <code class="command">Screen</code> entry with a different number and a different <code class="command">Screen</code> section identifier is necessary .
+ </div><div class="para">
+ The numbers to the right of <code class="command">"Screen0"</code> give the absolute X and Y coordinates for the upper-left corner of the screen (<code class="command">0 0</code> by default).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">InputDevice</code> — Specifies the name of an <code class="command">InputDevice</code> section to be used with the X server.
+ </div><div class="para">
+ It is advisable that there be at least two <code class="command">InputDevice</code> entries: one for the default mouse and one for the default keyboard. The options <code class="command">CorePointer</code> and <code class="command">CoreKeyboard</code> indicate that these are the primary mouse and keyboard.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Option "<em class="replaceable"><code><option-name></code></em>"</code> — An optional entry which specifies extra parameters for the section. Any options listed here override those listed in the <code class="command">ServerFlags</code> section.
+ </div><div class="para">
+ Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf</code> man page.
+ </div></li></ul></div><div class="para">
+ It is possible to put more than one <code class="command">ServerLayout</code> section in the <code class="filename">/etc/X11/xorg.conf</code> file. By default, the server only reads the first one it encounters, however.
+ </div><div class="para">
+ If there is an alternative <code class="command">ServerLayout</code> section, it can be specified as a command line argument when starting an X session.
+ </div></div><div class="section" title="21.3.1.4. Files" id="s3-x-server-config-xorg.conf-files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-files">21.3.1.4. <code class="command">Files</code> </h4></div></div></div><a id="id895063" class="indexterm"></a><div class="para">
+ The <code class="command">Files</code> section sets paths for services vital to the X server, such as the font path. This is an optional section, these paths are normally detected automatically. This section may be used to override any automatically detected defaults.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">Files</code> section:
+ </div><pre class="screen">Section "Files"
+ RgbPath "/usr/share/X11/rgb.txt"
+ FontPath "unix/:7100"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="command">Files</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">RgbPath</code> — Specifies the location of the RGB color database. This database defines all valid color names in X and ties them to specific RGB values.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">FontPath</code> — Specifies where the X server must connect to obtain fonts from the <code class="command">xfs</code> font server.
+ </div><div class="para">
+ By default, the <code class="command">FontPath</code> is <code class="command">unix/:7100</code>. This tells the X server to obtain font information using UNIX-domain sockets for inter-process communication (IPC) on port 7100.
+ </div><div class="para">
+ Refer to <a class="xref" href="s1-x-fonts.html" title="21.4. Fonts">Section 21.4, “Fonts”</a> for more information concerning X and fonts.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ModulePath</code> — An optional parameter which specifies alternate directories which store X server modules.
+ </div></li></ul></div></div><div class="section" title="21.3.1.5. Module" id="s3-x-server-config-xorg.conf-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-modules">21.3.1.5. <code class="command">Module</code> </h4></div></div></div><a id="id904325" class="indexterm"></a><div class="para">
+ By default, the X server automatically loads the following modules from the <code class="filename">/usr/lib/xorg/modules/</code> directory:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">extmod</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dbe</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">glx</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">freetype</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">type1</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">record</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dri</code>
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The default directory for loading these modules can be changed by specifying a different directory with the optional <code class="command">ModulePath</code> parameter in the <code class="command">Files</code> section. Refer to <a class="xref" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-files" title="21.3.1.4. Files">Section 21.3.1.4, “ <code class="command">Files</code> ”</a> for more information on this section.
+ </div><div class="para">
+ Adding a <code class="command">Module</code> section to <code class="filename">/etc/X11/xorg.conf</code> instructs the X server to load the modules listed in this section <span class="emphasis"><em>instead</em></span> of the default modules.
+ </div><div class="para">
+ For example, the following typical <code class="command">Module</code> section:
+ </div><pre class="screen">Section "Module"
+ Load "fbdevhw"
+EndSection</pre><div class="para">
+ instructs the X server to load the <code class="filename">fbdevhw</code> instead of the default modules.
+ </div><div class="para">
+ As such, if you add a <code class="command">Module</code> section to <code class="filename">/etc/X11/xorg.conf</code>, you will need to specify any default modules you want to load as well as any extra modules.
+ </div></div><div class="section" title="21.3.1.6. InputDevice" id="s3-x-server-config-xorg.conf-inputd"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-inputd">21.3.1.6. <code class="command">InputDevice</code> </h4></div></div></div><a id="id642773" class="indexterm"></a><div class="para">
+ Each <code class="command">InputDevice</code> section configures one input device for the X server. Systems typically have at least one <code class="command">InputDevice</code> section for the keyboard. It is perfectly normal to have no entry for a mouse, as most mouse settings are automatically detected.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">InputDevice</code> section for a keyboard:
+ </div><pre class="screen">Section "InputDevice"
+ Identifier "Keyboard0"
+ Driver "kbd"
+ Option "XkbModel" "pc105"
+ Option "XkbLayout" "us"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="command">InputDevice</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Identifier</code> — Specifies a unique name for this <code class="command">InputDevice</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Driver</code> — Specifies the name of the device driver X must load for the device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Option</code> — Specifies necessary options pertaining to the device.
+ </div><div class="para">
+ A mouse may also be specified to override any autodetected defaults for the device. The following options are typically included when adding a mouse in the <code class="filename">xorg.conf</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Protocol</code> — Specifies the protocol used by the mouse, such as <code class="command">IMPS/2</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Device</code> — Specifies the location of the physical device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Emulate3Buttons</code> — Specifies whether to allow a two-button mouse to act like a three-button mouse when both mouse buttons are pressed simultaneously.
+ </div></li></ul></div><div class="para">
+ Consult the <code class="filename">xorg.conf</code> man page for a list of valid options for this section.
+ </div></li></ul></div></div><div class="section" title="21.3.1.7. Monitor" id="s3-x-server-config-xorg.conf-monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-monitor">21.3.1.7. <code class="command">Monitor</code> </h4></div></div></div><a id="id690524" class="indexterm"></a><div class="para">
+ Each <code class="command">Monitor</code> section configures one type of monitor used by the system. This is an optional entry as well, as most monitors are now automatically detected.
+ </div><div class="para">
+ This example illustrates a typical <code class="command">Monitor</code> section for a monitor:
+ </div><pre class="screen">Section "Monitor"
+ Identifier "Monitor0"
+ VendorName "Monitor Vendor"
+ ModelName "DDC Probed Monitor - ViewSonic G773-2"
+ DisplaySize 320 240
+ HorizSync 30.0 - 70.0
+ VertRefresh 50.0 - 180.0
+EndSection</pre><div class="warning"><h2>Warning</h2><div class="para">
+ Be careful when manually editing values in the <code class="command">Monitor</code> section of <code class="filename">/etc/X11/xorg.conf</code>. Inappropriate values can damage or destroy a monitor. Consult the monitor's documentation for a listing of safe operating parameters.
+ </div></div><div class="para">
+ The following are commonly entries used in the <code class="command">Monitor</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Identifier</code> — Specifies a unique name for this <code class="command">Monitor</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">VendorName</code> — An optional parameter which specifies the vendor of the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ModelName</code> — An optional parameter which specifies the monitor's model name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">DisplaySize</code> — An optional parameter which specifies, in millimeters, the physical size of the monitor's picture area.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">HorizSync</code> — Specifies the range of horizontal sync frequencies compatible with the monitor in kHz. These values help the X server determine the validity of built-in or specified <code class="command">Modeline</code> entries for the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">VertRefresh</code> — Specifies the range of vertical refresh frequencies supported by the monitor, in kHz. These values help the X server determine the validity of built in or specified <code class="command">Modeline</code> entries for the monitor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Modeline</code> — An optional parameter which specifies additional video modes for the monitor at particular resolutions, with certain horizontal sync and vertical refresh resolutions. Refer to the <code class="filename">xorg.conf</code> man page for a more detailed explanation of <code class="command">Modeline</code> entries.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Option "<em class="replaceable"><code><option-name></code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf</code> man page.
+ </div></li></ul></div></div><div class="section" title="21.3.1.8. Device" id="s3-x-server-config-xorg.conf-device"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-device">21.3.1.8. <code class="command">Device</code> </h4></div></div></div><a id="id655207" class="indexterm"></a><div class="para">
+ Each <code class="command">Device</code> section configures one video card on the system. While one <code class="command">Device</code> section is the minimum, additional instances may occur for each video card installed on the machine.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">Device</code> section for a video card:
+ </div><pre class="screen">Section "Device"
+ Identifier "Videocard0"
+ Driver "mga"
+ VendorName "Videocard vendor"
+ BoardName "Matrox Millennium G200"
+ VideoRam 8192
+ Option "dpms"
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="command">Device</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Identifier</code> — Specifies a unique name for this <code class="command">Device</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Driver</code> — Specifies which driver the X server must load to utilize the video card. A list of drivers can be found in <code class="filename">/usr/share/hwdata/videodrivers</code>, which is installed with the <code class="filename">hwdata</code> package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">VendorName</code> — An optional parameter which specifies the vendor of the video card.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">BoardName</code> — An optional parameter which specifies the name of the video card.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">VideoRam</code> — An optional parameter which specifies the amount of RAM available on the video card in kilobytes. This setting is only necessary for video cards the X server cannot probe to detect the amount of video RAM.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">BusID</code> — An entry which specifies the bus location of the video card. On systems with only one video card a <code class="command">BusID</code> entry is optional and may not even be present in the default <code class="filename">/etc/X11/xorg.conf</code> file. On systems with more than one video card, however, a <code class="command">BusID</code> entry must be present.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Screen</code> — An optional entry which specifies which monitor connector or head on the video card the <code class="command">Device</code> section configures. This option is only useful for video cards with multiple heads.
+ </div><div class="para">
+ If multiple monitors are connected to different heads on the same video card, separate <code class="command">Device</code> sections must exist and each of these sections must have a different <code class="command">Screen</code> value.
+ </div><div class="para">
+ Values for the <code class="command">Screen</code> entry must be an integer. The first head on the video card has a value of <code class="command">0</code>. The value for each additional head increments this value by one.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Option "<em class="replaceable"><code><option-name></code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf</code> man page.
+ </div><div class="para">
+ One of the more common options is <code class="command">"dpms"</code> (for Display Power Management Signaling, a VESA standard), which activates the Service Star energy compliance setting for the monitor.
+ </div></li></ul></div></div><div class="section" title="21.3.1.9. Screen" id="s3-x-server-config-xorg.conf-screen"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-screen">21.3.1.9. <code class="command">Screen</code> </h4></div></div></div><a id="id940318" class="indexterm"></a><div class="para">
+ Each <code class="command">Screen</code> section binds one video card (or video card head) to one monitor by referencing the <code class="command">Device</code> section and the <code class="command">Monitor</code> section for each. While one <code class="command">Screen</code> section is the minimum, additional instances may occur for each video card and monitor combination present on the machine.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">Screen</code> section:
+ </div><pre class="screen">Section "Screen"
+ Identifier "Screen0"
+ Device "Videocard0"
+ Monitor "Monitor0"
+ DefaultDepth 16
+
+ SubSection "Display"
+ Depth 24
+ Modes "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
+ EndSubSection
+
+ SubSection "Display"
+ Depth 16
+ Modes "1152x864" "1024x768" "800x600" "640x480"
+ EndSubSection
+EndSection</pre><div class="para">
+ The following entries are commonly used in the <code class="command">Screen</code> section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Identifier</code> — Specifies a unique name for this <code class="command">Screen</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Device</code> — Specifies the unique name of a <code class="command">Device</code> section. This is a required entry.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Monitor</code> — Specifies the unique name of a <code class="command">Monitor</code> section. This is only required if a specific <code class="command">Monitor</code> section is defined in the <code class="filename">xorg.conf</code> file. Normally, monitors are automatically detected.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">DefaultDepth</code> — Specifies the default color depth in bits. In the previous example, <code class="command">16</code> (which provides thousands of colors) is the default. Only one <code class="command">DefaultDepth</code> is permitted, although this can be overridden with the Xorg command line option <code class="command">-depth <em class="replaceable"><code><n></code></em> </code>,where <code class="command"><em class="replaceable"><code><n></code></em> </code> is any additional depth specified.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SubSection "Display"</code> — Specifies the screen modes available at a particular color depth. The <code class="command">Screen</code> section can have multiple <code class="command">Display</code> subsections, which are entirely optional since screen modes are automatically detected.
+ </div><div class="para">
+ This subsection is normally used to override autodetected modes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">Option "<em class="replaceable"><code><option-name></code></em>"</code> — An optional entry which specifies extra parameters for the section. Replace <em class="replaceable"><code><option-name></code></em> with a valid option listed for this section in the <code class="filename">xorg.conf</code> man page.
+ </div></li></ul></div></div><div class="section" title="21.3.1.10. DRI" id="s3-x-server-config-xorg.conf-dri"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-server-config-xorg.conf-dri">21.3.1.10. <code class="command">DRI</code> </h4></div></div></div><a id="id909499" class="indexterm"></a><div class="para">
+ The optional <code class="command">DRI</code> section specifies parameters for the <em class="firstterm">Direct Rendering Infrastructure</em> (<em class="firstterm">DRI</em>). DRI is an interface which allows 3D software applications to take advantage of 3D hardware acceleration capabilities built into most modern video hardware. In addition, DRI can improve 2D performance via hardware acceleration, if supported by the video card driver.
+ </div><div class="para">
+ This section rarely appears, as the DRI Group and Mode are automatically initialized to default values. If a different Group or Mode is desired, then adding this section to the <code class="filename">xorg.conf</code> file will override those defaults.
+ </div><div class="para">
+ The following example illustrates a typical <code class="command">DRI</code> section:
+ </div><pre class="screen">Section "DRI"
+ Group 0
+ Mode 0666
+EndSection</pre><div class="para">
+ Since different video cards use DRI in different ways, do not add to this section without first referring to <a href="http://dri.sourceforge.net/">http://dri.sourceforge.net/</a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-x-clients-winmanagers.html"><strong>Prev</strong>21.2.2. Window Managers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-x-fonts.html"><strong>Next</strong>21.4. Fonts</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-apache-mpm-containers.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-apache-mpm-containers.html
new file mode 100644
index 0000000..743496e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-apache-mpm-containers.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>11.5.3. MPM Specific Server-Pool 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-config.html" title="11.5. Configuration Directives in httpd.conf" /><link rel="prev" href="s2-apache-sslcommands.html" title="11.5.2. Configuration Directives for SSL" /><link rel="next" href="s1-apache-addmods.html" title="11.6. Adding Modules" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to vi
ew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-sslcommands.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-addmods.html"><strong>Next</strong></a></li></ul><div class="section" title="11.5.3. MPM Specific Server-Pool Directives" id="s2-apache-mpm-containers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mpm-containers">11.5.3. MPM Specific Server-Pool Directives</h3></div></div></div><a id="id1012990" class="indexterm"></a><div class="para">
+ As explained in <a class="xref" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-pool" title="11.2.2.1.2. Server-Pool Size Regulation">Section 11.2.2.1.2, “Server-Pool Size Regulation”</a>, the responsibility for managing characteristics of the server-pool falls to a module group called MPMs under Apache HTTP Server 2.0. The characteristics of the server-pool differ depending upon which MPM is used. For this reason, an <code class="command">IfModule</code> container is necessary to define the server-pool for the MPM in use.
+ </div><div class="para">
+ By default, Apache HTTP Server 2.0 defines the server-pool for both the <code class="command">prefork</code> and <code class="command">worker</code> MPMs.
+ </div><div class="para">
+ The following section list directives found within the MPM-specific server-pool containers.
+ </div><div class="formalpara" id="s3-apache-maxclients"><h5 class="formalpara">MaxClients</h5><a id="id595942" class="indexterm"></a><a id="id595961" class="indexterm"></a>
+ <code class="command">MaxClients</code> sets a limit on the total number of server processes, or simultaneously connected clients, that can run at one time. The main purpose of this directive is to keep a runaway Apache HTTP Server from crashing the operating system. For busy servers this value should be set to a high value. The server's default is set to 150 regardless of the MPM in use. However, it is not recommended that the value for <code class="command">MaxClients</code> exceeds <code class="command">256</code> when using the <code class="command">prefork</code> MPM.
+ </div><div class="formalpara" id="s3-apache-maxrequestsperchild"><h5 class="formalpara">MaxRequestsPerChild</h5><a id="id596019" class="indexterm"></a><a id="id596037" class="indexterm"></a>
+ <code class="command">MaxRequestsPerChild</code> sets the total number of requests each child server process serves before the child dies. The main reason for setting <code class="command">MaxRequestsPerChild</code> is to avoid long-lived process induced memory leaks. The default <code class="command">MaxRequestsPerChild</code> for the <code class="command">prefork</code> MPM is <code class="command">4000</code> and for the <code class="command">worker</code> MPM is <code class="command">0</code>.
+ </div><div class="formalpara" id="s3-apache-minmaxspareservers"><h5 class="formalpara">MinSpareServers and MaxSpareServers</h5><a id="id596105" class="indexterm"></a><a id="id906816" class="indexterm"></a><a id="id906835" class="indexterm"></a><a id="id906853" class="indexterm"></a>
+ These values are only used with the <code class="command">prefork</code> MPM. They adjust how the Apache HTTP Server dynamically adapts to the perceived load by maintaining an appropriate number of spare server processes based on the number of incoming requests. The server checks the number of servers waiting for a request and kills some if there are more than <code class="command">MaxSpareServers</code> or creates some if the number of servers is less than <code class="command">MinSpareServers</code>.
+ </div><div class="para">
+ The default <code class="command">MinSpareServers</code> value is <code class="command">5</code>; the default <code class="command">MaxSpareServers</code> value is <code class="command">20</code>. These default settings should be appropriate for most situations. Be careful not to increase the <code class="command">MinSpareServers</code> to a large number as doing so creates a heavy processing load on the server even when traffic is light.
+ </div><div class="formalpara" id="s3-apache-minmaxsparethreads"><h5 class="formalpara">MinSpareThreads and MaxSpareThreads</h5><a id="id906931" class="indexterm"></a><a id="id906949" class="indexterm"></a><a id="id906967" class="indexterm"></a><a id="id822505" class="indexterm"></a>
+ These values are only used with the <code class="command">worker</code> MPM. They adjust how the Apache HTTP Server dynamically adapts to the perceived load by maintaining an appropriate number of spare server threads based on the number of incoming requests. The server checks the number of server threads waiting for a request and kills some if there are more than <code class="command">MaxSpareThreads</code> or creates some if the number of servers is less than <code class="command">MinSpareThreads</code>.
+ </div><div class="para">
+ The default <code class="command">MinSpareThreads</code> value is <code class="command">25</code>; the default <code class="command">MaxSpareThreads</code> value is <code class="command">75</code>. These default settings should be appropriate for most situations. The value for <code class="command">MaxSpareThreads</code> must be greater than or equal to the sum of <code class="command">MinSpareThreads</code> and <code class="command">ThreadsPerChild</code>, else the Apache HTTP Server automatically corrects it.
+ </div><div class="formalpara" id="s3-apache-startservers"><h5 class="formalpara">StartServers</h5><a id="id822591" class="indexterm"></a><a id="id822609" class="indexterm"></a>
+ The <code class="command">StartServers</code> directive sets how many server processes are created upon startup. Since the Web server dynamically kills and creates server processes based on traffic load, it is not necessary to change this parameter. The Web server is set to start <code class="command">8</code> server processes at startup for the <code class="command">prefork</code> MPM and <code class="command">2</code> for the <code class="command">worker</code> MPM.
+ </div><div class="formalpara" id="s3-apache-threadsperchild"><h5 class="formalpara">ThreadsPerChild</h5><a id="id822670" class="indexterm"></a><a id="id811116" class="indexterm"></a>
+ This value is only used with the <code class="command">worker</code> MPM. It sets the number of threads within each child process. The default value for this directive is <code class="command">25</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-sslcommands.html"><strong>Prev</strong>11.5.2. Configuration Directives for SSL</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-addmods.html"><strong>Next</strong>11.6. Adding Modules</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-apache-sslcommands.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-apache-sslcommands.html
new file mode 100644
index 0000000..786fed0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-apache-sslcommands.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.5.2. Configuration Directives for SSL</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-config.html" title="11.5. Configuration Directives in httpd.conf" /><link rel="prev" href="s1-apache-config.html" title="11.5. Configuration Directives in httpd.conf" /><link rel="next" href="s2-apache-mpm-containers.html" title="11.5.3. MPM Specific Server-Pool Directives" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html
">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-config.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-apache-mpm-containers.html"><strong>Next</strong></a></li></ul><div class="section" title="11.5.2. Configuration Directives for SSL" id="s2-apache-sslcommands"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-sslcommands">11.5.2. Configuration Directives for SSL</h3></div></div></div><a id="id992491" class="indexterm"></a><a id="id992501" class="indexterm"></a><div class="para">
+ The directives in <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file can be configured to enable secure Web communications using SSL and TLS.
+ </div><div class="formalpara" id="s3-apache-setenvif"><h5 class="formalpara">SetEnvIf</h5><a id="id1012875" class="indexterm"></a><a id="id1012893" class="indexterm"></a>
+ <code class="command">SetEnvIf</code> sets environment variables based on the headers of incoming connections. It is <span class="emphasis"><em>not</em></span> solely an SSL directive, though it is present in the supplied <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file. It's purpose in this context is to disable HTTP keepalive and to allow SSL to close the connection without a closing notification from the client browser. This setting is necessary for certain browsers that do not reliably shut down the SSL connection.
+ </div><div class="para">
+ For more information on other directives within the SSL configuration file, refer to the following URLs:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ http://localhost/manual/mod/mod_ssl.html
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html">http://httpd.apache.org/docs/2.2/mod/mod_ssl.html</a>
+ </div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
+ In most cases, SSL directives are configured appropriately during the installation of Fedora. Be careful when altering Apache HTTP Secure Server directives, misconfiguration can lead to security vulnerabilities.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-config.html"><strong>Prev</strong>11.5. Configuration Directives in httpd.conf </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-containers.html"><strong>Next</strong>11.5.3. MPM Specific Server-Pool Directives</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-at-batch-controlling-access.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-at-batch-controlling-access.html
new file mode 100644
index 0000000..6a798af
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-at-batch-controlling-access.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-autotasks-at-batch.html" title="24.2. At and Batch" /><link rel="prev" href="s2-autotasks-commandline-options.html" title="24.2.4. Additional Command Line Options" /><link rel="next" href="s2-autotasks-at-batch-service.html" title="24.2.6. Starting and Stopping the Service" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Thi
s is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>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="24.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">24.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>24.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>24.2.6. Starting and Stopping the Service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-at-batch-service.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-at-batch-service.html
new file mode 100644
index 0000000..8716834
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-at-batch-service.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-autotasks-at-batch.html" title="24.2. At and Batch" /><link rel="prev" href="s2-autotasks-at-batch-controlling-access.html" title="24.2.5. Controlling Access to At and Batch" /><link rel="next" href="s1-autotasks-additional-resources.html" title="24.3. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN" class="section" title="24.2.6. Starting and Stopping the Service" id="s2-autotasks-at-batch-service" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" i
d="s2-autotasks-at-batch-service">24.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 6. Controlling Access to Services">Chapter 6, <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>24.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>24.3. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-at-batch-viewing.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-at-batch-viewing.html
new file mode 100644
index 0000000..a72819e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-at-batch-viewing.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-autotasks-at-batch.html" title="24.2. At and Batch" /><link rel="prev" href="s2-autotasks-batch-configuring.html" title="24.2.2. Configuring Batch Jobs" /><link rel="next" href="s2-autotasks-commandline-options.html" title="24.2.4. Additional Command Line Options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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</strong></a></li><li class="next"><a accesskey="n" href="s2-autotasks-commandline-options.html"><strong>Next</strong></a></li></ul><div class="section" title="24.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">24.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>24.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>24.2.4. Additional Command Line Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-batch-configuring.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-batch-configuring.html
new file mode 100644
index 0000000..01ca6aa
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-batch-configuring.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-autotasks-at-batch.html" title="24.2. At and Batch" /><link rel="prev" href="s1-autotasks-at-batch.html" title="24.2. At and Batch" /><link rel="next" href="s2-autotasks-at-batch-viewing.html" title="24.2.3. Viewing Pending Jobs" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable
iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="24.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">24.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 type <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 type <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 typing <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 use
d 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="24.2.3. Viewing Pending Jobs">Section 24.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="24.2.5. Controlling Access to At and Batch">Section 24.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>24.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>24.2.3. Viewing Pending Jobs</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-commandline-options.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-commandline-options.html
new file mode 100644
index 0000000..db282f9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-autotasks-commandline-options.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>24.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-autotasks-at-batch.html" title="24.2. At and Batch" /><link rel="prev" href="s2-autotasks-at-batch-viewing.html" title="24.2.3. Viewing Pending Jobs" /><link rel="next" href="s2-autotasks-at-batch-controlling-access.html" title="24.2.5. Controlling Access to At and Batch" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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>Prev</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="24.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">24.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 24.1. at and batch Command Line Options" id="tb-at-command-line-options"><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><h6>Table 24.1. <code class="command">at</code> and <code class="command">batch</code> Command Line Options</h6></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>24.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>24.2.5. Controlling Access to At and Batch</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-configuration-zone-reverse.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-configuration-zone-reverse.html
new file mode 100644
index 0000000..7a7ec43
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-configuration-zone-reverse.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>7.3.4. Reverse Name Resolution 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-zone.html" title="7.3. Zone Files" /><link rel="prev" href="s2-bind-zone-examples.html" title="7.3.3. Example Zone File" /><link rel="next" href="s1-bind-rndc.html" title="7.4. Using rndc" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe>
</div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="s1-bind-rndc.html"><strong>Next</strong></a></li></ul><div class="section" title="7.3.4. Reverse Name Resolution Zone Files" id="s2-bind-configuration-zone-reverse"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-configuration-zone-reverse">7.3.4. Reverse Name Resolution Zone Files</h3></div></div></div><a id="id571384" 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 FQDN. It looks very similar to a standard zone file, except that <code class="command">PTR</code> resource records are used to link the IP addresses to a fully qualified domain name.
+ </div><div class="para">
+ The following illustrates the layout of a <code class="command">PTR</code> record:
+ </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> is the last number in an IP address which points to a particular system's FQDN.
+ </div><div class="para">
+ In the following example, IP addresses <code class="command">10.0.1.1</code> through <code class="command">10.0.1.6</code> are pointed to corresponding FQDNs. It can be located in <code class="filename">/var/named/example.com.rr.zone</code>.
+ </div><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 class="para">
+ This zone file would be called into service with a <code class="command">zone</code> statement in the <code class="filename">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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-zone-examples.html"><strong>Prev</strong>7.3.3. Example Zone 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-bind-rndc.html"><strong>Next</strong>7.4. Using rndc </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-features-ipv6.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-features-ipv6.html
new file mode 100644
index 0000000..a128e48
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-features-ipv6.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.5.4. IP version 6</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-features.html" title="7.5. Advanced Features of BIND" /><link rel="prev" href="s2-bind-features-security.html" title="7.5.3. Security" /><link rel="next" href="s1-bind-mistakes.html" title="7.6. Common Mistakes to Avoid" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display
.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-security.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="7.5.4. IP version 6" id="s2-bind-features-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-ipv6">7.5.4. IP version 6</h3></div></div></div><a id="id970446" class="indexterm"></a><div class="para">
+ BIND version 9 supports name service in IP version 6 (IPv6) environments through the use of <code class="command">A6</code> zone records.
+ </div><div class="para">
+ If the network environment includes both IPv4 and IPv6 hosts, use the <code class="command">lwresd</code> lightweight resolver daemon on all network clients. This daemon is a very efficient, caching-only nameserver which understands the new <code class="command">A6</code> and <code class="command">DNAME</code> records used under IPv6. Refer to the <code class="command">lwresd</code> man page for more information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-security.html"><strong>Prev</strong>7.5.3. Security</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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>7.6. Common Mistakes to Avoid</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-features-security.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-features-security.html
new file mode 100644
index 0000000..dd4fb0b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-features-security.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>7.5.3. Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-features.html" title="7.5. Advanced Features of BIND" /><link rel="prev" href="s2-bind-features-views.html" title="7.5.2. Multiple Views" /><link rel="next" href="s2-bind-features-ipv6.html" title="7.5.4. IP version 6" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</ifr
ame></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-views.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="7.5.3. Security" id="s2-bind-features-security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-security">7.5.3. Security</h3></div></div></div><a id="id638494" class="indexterm"></a><div class="para">
+ BIND supports a number of different methods to protect the updating and transfer of zones, on both master and slave nameservers:
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="emphasis"><em>DNSSEC</em></span> </span></dt><dd><div class="para">
+ Short for <em class="firstterm">DNS SECurity</em>, this feature allows for zones to be cryptographically signed with a <em class="firstterm">zone key</em>.
+ </div><div class="para">
+ In this way, the information about a specific zone can be verified as coming from a nameserver that has signed it with a particular private key, as long as the recipient has that nameserver's public key.
+ </div><div class="para">
+ BIND version 9 also supports the SIG(0) public/private key method of message authentication.
+ </div></dd><dt><span class="term"> <span class="emphasis"><em>TSIG</em></span> </span></dt><dd><div class="para">
+ Short for <em class="firstterm">Transaction SIGnatures</em>, this feature allows a transfer from master to slave only after verifying that a shared secret key exists on both nameservers.
+ </div><div class="para">
+ This feature strengthens the standard IP address-based method of transfer authorization. An attacker 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">
+ BIND version 9 also supports <em class="firstterm">TKEY</em>, which is another shared secret key method of authorizing zone transfers.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-views.html"><strong>Prev</strong>7.5.2. Multiple Views</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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>7.5.4. IP version 6</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-features-views.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-features-views.html
new file mode 100644
index 0000000..7545254
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-features-views.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.5.2. Multiple Views</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-features.html" title="7.5. Advanced Features of BIND" /><link rel="prev" href="s1-bind-features.html" title="7.5. Advanced Features of BIND" /><link rel="next" href="s2-bind-features-security.html" title="7.5.3. Security" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe disp
lay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-security.html"><strong>Next</strong></a></li></ul><div class="section" title="7.5.2. 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">7.5.2. Multiple Views</h3></div></div></div><a id="id638435" class="indexterm"></a><div class="para">
+ Through the use of the <code class="command">view</code> statement in <code class="filename">named.conf</code>, BIND can present different information depending on which network a request originates from.
+ </div><div class="para">
+ 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">
+ The <code class="command">view</code> statement uses the <code class="command">match-clients</code> option to match IP addresses or entire networks and give them special options and zone data.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-features.html"><strong>Prev</strong>7.5. 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-security.html"><strong>Next</strong>7.5.3. Security</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-namedconf-comm.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-namedconf-comm.html
new file mode 100644
index 0000000..8f0693b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-namedconf-comm.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-namedconf.html" title="7.2. /etc/named.conf" /><link rel="prev" href="s2-bind-namedconf-state-other.html" title="7.2.2. Other Statement Types" /><link rel="next" href="s1-bind-zone.html" title="7.3. Zone Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe
></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="next"><a accesskey="n" href="s1-bind-zone.html"><strong>Next</strong></a></li></ul><div class="section" title="7.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">7.2.3. Comment Tags</h3></div></div></div><div class="para">
+ The following is a list of valid comment tags used within <code class="filename">named.conf</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">//</code> — When placed at the beginning of a line, that line is ignored by <code class="command">named</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">#</code> — When placed at the beginning of a line, that line is ignored by <code class="command">named</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">/*</code> and <code class="command">*/</code> — When text is enclosed in these tags, the block of text is ignored by <code class="command">named</code>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-namedconf-state-other.html"><strong>Prev</strong>7.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>7.3. Zone Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-namedconf-state-other.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-namedconf-state-other.html
new file mode 100644
index 0000000..c5c0e45
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-namedconf-state-other.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>7.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-namedconf.html" title="7.2. /etc/named.conf" /><link rel="prev" href="s1-bind-namedconf.html" title="7.2. /etc/named.conf" /><link rel="next" href="s2-bind-namedconf-comm.html" title="7.2.3. Comment Tags" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</if
rame></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s2-bind-namedconf-comm.html"><strong>Next</strong></a></li></ul><div class="section" title="7.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">7.2.2. Other Statement Types</h3></div></div></div><div class="para">
+ The following is a list of lesser used statement types available within <code class="filename">named.conf</code>:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">controls</code> </span></dt><dd><div class="para">
+ Configures various security requirements necessary to use the <code class="command">rndc</code> command to administer the <code class="command">named</code> service.
+ </div><div class="para">
+ Refer to <a class="xref" href="s1-bind-rndc.html#s2-bind-rndc-configuration-namedconf" title="7.4.1. Configuring /etc/named.conf">Section 7.4.1, “Configuring <code class="filename">/etc/named.conf</code> ”</a> to learn more about how the <code class="command">controls</code> statement is structured and what options are available.
+ </div></dd><dt><span class="term"> <code class="command">key "<em class="replaceable"><code><key-name></code></em>"</code> </span></dt><dd><div class="para">
+ Defines 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="command">key</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">algorithm <em class="replaceable"><code><algorithm-name></code></em> </code> — The type of algorithm used, such as <code class="command">hmac-md5</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">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="s2-bind-rndc-configuration-rndcconf.html" title="7.4.2. Configuring /etc/rndc.conf">Section 7.4.2, “Configuring <code class="filename">/etc/rndc.conf</code> ”</a> for instructions on how to write a <code class="command">key</code> statement.
+ </div></dd><dt><span class="term"> <code class="command">logging</code> </span></dt><dd><div class="para">
+ Allows for the use of multiple types of logs, called <em class="firstterm">channels</em>. By using the <code class="command">channel</code> option within the <code class="command">logging</code> statement, a customized type of log can be constructed — with its own file name (<code class="command">file</code>), size limit (<code class="command">size</code>), versioning (<code class="command">version</code>), and level of importance (<code class="command">severity</code>). Once a customized channel is defined, a <code class="command">category</code> option is used to categorize the channel and begin logging when <code class="command">named</code> is restarted.
+ </div><div class="para">
+ By default, <code class="command">named</code> logs standard messages to the <code class="command">rsyslog</code> daemon, which places them in <code class="filename">/var/log/messages</code>. This occurs because several standard channels are built into BIND with various severity levels, such as <code class="command">default_syslog</code> (which handles informational logging messages) and <code class="command">default_debug</code> (which specifically handles debugging messages). A default category, called <code class="command">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="7.7.1. Installed Documentation">Section 7.7.1, “Installed Documentation”</a>.
+ </div></dd><dt><span class="term"> <code class="command">server</code> </span></dt><dd><div class="para">
+ Specifies options that affect how <code class="command">named</code> should respond to remote nameservers, especially with regard to notifications and zone transfers.
+ </div><div class="para">
+ The <code class="command">transfer-format</code> option controls whether one resource record is sent with each message (<code class="command">one-answer</code>) or multiple resource records are sent with each message (<code class="command">many-answers</code>). While <code class="command">many-answers</code> is more efficient, only newer BIND nameservers understand it.
+ </div></dd><dt><span class="term"> <code class="command">trusted-keys</code> </span></dt><dd><div class="para">
+ Contains assorted public keys used for secure DNS (DNSSEC). Refer to <a class="xref" href="s2-bind-features-security.html" title="7.5.3. Security">Section 7.5.3, “Security”</a> for more information concerning BIND security.
+ </div></dd><dt><span class="term"> <code class="command">view "<em class="replaceable"><code><view-name></code></em>"</code> </span></dt><dd><div class="para">
+ Creates 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 may be used, but their names must be unique. The <code class="command">match-clients</code> option specifies the IP addresses that apply to a particular view. Any <code class="command">options</code> statement may also be used within a view, overriding the global options already configured for <code class="command">named</code>. Most <code class="command">view</code> statements contain multiple <code class="command">zone</code> statements that apply to the <code class="command">match-clients</code> list. The order in which <code class="command">view</code> statements are listed is important, as the first <code class="command">view</code> statement that matches a particular client's IP address is used.
+ </div><div class="para">
+ Refer to <a class="xref" href="s2-bind-features-views.html" title="7.5.2. Multiple Views">Section 7.5.2, “Multiple Views”</a> for more information about the <code class="command">view</code> statement.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-namedconf.html"><strong>Prev</strong>7.2. /etc/named.conf </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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>7.2.3. Comment Tags</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-related-books.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-related-books.html
new file mode 100644
index 0000000..e66cd42
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-related-books.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.7.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-additional-resources.html" title="7.7. Additional Resources" /><link rel="prev" href="s2-bind-useful-websites.html" title="7.7.2. Useful Websites" /><link rel="next" href="ch-OpenSSH.html" title="Chapter 8. OpenSSH" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</
iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="next"><a accesskey="n" href="ch-OpenSSH.html"><strong>Next</strong></a></li></ul><div class="section" title="7.7.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">7.7.3. Related Books</h3></div></div></div><a id="id960694" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">DNS and BIND</em> by Paul Albitz and Cricket Liu; O'Reilly & Associates — A popular reference that explains both common and esoteric BIND configuration options, as well as providing strategies for securing a DNS server.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">The Concise Guide to DNS and BIND</em> by Nicolai Langfeldt; Que — Looks at the connection between multiple network services and BIND, with an emphasis on task-oriented, technical topics.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-useful-websites.html"><strong>Prev</strong>7.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="ch-OpenSSH.html"><strong>Next</strong>Chapter 8. OpenSSH</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-rndc-configuration-rndcconf.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-rndc-configuration-rndcconf.html
new file mode 100644
index 0000000..9c1954f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-rndc-configuration-rndcconf.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>7.4.2. Configuring /etc/rndc.conf</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-rndc.html" title="7.4. Using rndc" /><link rel="prev" href="s1-bind-rndc.html" title="7.4. Using rndc" /><link rel="next" href="s2-bind-rndc-options.html" title="7.4.3. Command Line Options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div>
<p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-options.html"><strong>Next</strong></a></li></ul><div class="section" title="7.4.2. Configuring /etc/rndc.conf" id="s2-bind-rndc-configuration-rndcconf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-configuration-rndcconf">7.4.2. Configuring <code class="filename">/etc/rndc.conf</code> </h3></div></div></div><a id="id652945" class="indexterm"></a><a id="id652972" class="indexterm"></a><div class="para">
+ The <code class="command">key</code> is the most important statement in <code class="filename">/etc/rndc.conf</code>.
+ </div><pre class="screen">
+key "<em class="replaceable"><code><key-name></code></em>" {
+ algorithm hmac-md5;
+ secret "<em class="replaceable"><code><key-value></code></em>";
+};
+</pre><div class="para">
+ The <em class="replaceable"><code><key-name></code></em> and <em class="replaceable"><code><key-value></code></em> should be exactly the same as their settings in <code class="filename">/etc/named.conf</code>.
+ </div><div class="para">
+ To match the keys specified in the target server's <code class="filename">/etc/named.conf</code>, add the following lines to <code class="filename">/etc/rndc.conf</code>.
+ </div><pre class="screen">
+options {
+ default-server localhost;
+ default-key "<em class="replaceable"><code><key-name></code></em>";
+};
+</pre><div class="para">
+ This directive sets a global default key. However, the <code class="filename">rndc</code> configuration file can also specify different keys for different servers, as in the following example:
+ </div><pre class="screen">
+server localhost {
+ key "<em class="replaceable"><code><key-name></code></em>";
+};
+</pre><div class="important"><h2>Important</h2><div class="para">
+ Make sure that only the root user can read or write to the <code class="filename">/etc/rndc.conf</code> file.
+ </div></div><div class="para">
+ For more information about the <code class="filename">/etc/rndc.conf</code> file, refer to the <code class="filename">rndc.conf</code> man page.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-rndc.html"><strong>Prev</strong>7.4. Using rndc </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-options.html"><strong>Next</strong>7.4.3. Command Line Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-rndc-options.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-rndc-options.html
new file mode 100644
index 0000000..ccc950a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-rndc-options.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>7.4.3. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-rndc.html" title="7.4. Using rndc" /><link rel="prev" href="s2-bind-rndc-configuration-rndcconf.html" title="7.4.2. Configuring /etc/rndc.conf" /><link rel="next" href="s1-bind-features.html" title="7.5. Advanced Features of BIND" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or ena
ble iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-configuration-rndcconf.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-bind-features.html"><strong>Next</strong></a></li></ul><div class="section" title="7.4.3. Command Line Options" id="s2-bind-rndc-options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-options">7.4.3. Command Line Options</h3></div></div></div><a id="id962698" class="indexterm"></a><div class="para">
+ An <code class="command">rndc</code> command takes the following form:
+ </div><pre class="screen">rndc <em class="replaceable"><code><options></code></em> <em class="replaceable"><code><command></code></em> <em class="replaceable"><code><command-options></code></em>
+</pre><div class="para">
+ When executing <code class="command">rndc</code> on a properly configured localhost, the following commands are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">halt</code> — Stops the <code class="filename">named</code> service immediately.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">querylog</code> — Logs all queries made to this nameserver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">refresh</code> — Refreshes the nameserver's database.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">reload</code> — Reloads the zone files but keeps all other previously cached responses. This command also allows changes to zone files without losing all stored name resolutions.
+ </div><div class="para">
+ If changes made only affect a specific zone, reload only that specific zone by adding the name of the zone after the <code class="command">reload</code> command.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">stats</code> — Dumps the current <code class="command">named</code> statistics to the <code class="filename">/var/named/named.stats</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">stop</code> — Stops the server gracefully, saving any dynamic update and <em class="firstterm">Incremental Zone Transfers</em> (<em class="firstterm">IXFR</em>) data before exiting.
+ </div></li></ul></div><div class="para">
+ Occasionally, it may be necessary to override the default settings in the <code class="filename">/etc/rndc.conf</code> file. The following options are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-c <em class="replaceable"><code><configuration-file></code></em> </code> — Specifies the alternate location of a configuration file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-p <em class="replaceable"><code><port-number></code></em> </code> — Specifies a port number to use for the <code class="command">rndc</code> connection other than the default port 953.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-s <em class="replaceable"><code><server></code></em> </code> — Specifies a server other than the <code class="command">default-server</code> listed in <code class="filename">/etc/rndc.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-y <em class="replaceable"><code><key-name></code></em> </code> — Specifies a key other than the <code class="command">default-key</code> option in <code class="filename">/etc/rndc.conf</code>.
+ </div></li></ul></div><div class="para">
+ Additional information about these options can be found in the <code class="command">rndc</code> man page.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-configuration-rndcconf.html"><strong>Prev</strong>7.4.2. Configuring /etc/rndc.conf </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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>7.5. Advanced Features of BIND</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-useful-websites.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-useful-websites.html
new file mode 100644
index 0000000..b1aac34
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-useful-websites.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-additional-resources.html" title="7.7. Additional Resources" /><link rel="prev" href="s1-bind-additional-resources.html" title="7.7. Additional Resources" /><link rel="next" href="s2-bind-related-books.html" title="7.7.3. Related Books" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or en
able iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="7.7.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">7.7.2. Useful Websites</h3></div></div></div><a id="id700182" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.isc.org/index.pl?/sw/bind/">http://www.isc.org/index.pl?/sw/bind/</a> — 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></li><li class="listitem"><div class="para">
+ <a href="http://www.redhat.com/mirrors/LDP/HOWTO/DNS-HOWTO.html">http://www.redhat.com/mirrors/LDP/HOWTO/DNS-HOWTO.html</a> — Covers the use of BIND as a resolving, caching nameserver and the configuration of various zone files necessary to serve as the primary nameserver for a domain.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-additional-resources.html"><strong>Prev</strong>7.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="s2-bind-related-books.html"><strong>Next</strong>7.7.3. Related Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-zone-examples.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-zone-examples.html
new file mode 100644
index 0000000..02d48f6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-bind-zone-examples.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>7.3.3. Example Zone 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-zone.html" title="7.3. Zone Files" /><link rel="prev" href="s3-bind-zone-rr.html" title="7.3.2. Zone File Resource Records" /><link rel="next" href="s2-bind-configuration-zone-reverse.html" title="7.3.4. Reverse Name Resolution Zone Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-configuration-zone-reverse.html"><strong>Next</strong></a></li></ul><div class="section" title="7.3.3. Example Zone File" id="s2-bind-zone-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-zone-examples">7.3.3. Example Zone File</h3></div></div></div><a id="id602205" class="indexterm"></a><div class="para">
+ Seen individually, directives and resource records can be difficult to grasp. However, when placed together in a single file, they become easier to understand.
+ </div><div class="para">
+ The following example shows a very basic zone file.
+ </div><pre class="screen">$ORIGIN example.com.
+$TTL 86400
+@ 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
+;
+;
+ NS dns1.example.com.
+ NS dns2.example.com.
+dns1 A 10.0.1.1
+ AAAA aaaa:bbbb::1
+dns2 A 10.0.1.2
+ AAAA aaaa:bbbb::2
+;
+;
+@ MX 10 mail.example.com.
+ MX 20 mail2.example.com.
+mail A 10.0.1.5
+ AAAA aaaa:bbbb::5
+mail2 A 10.0.1.6
+ AAAA aaaa:bbbb::6
+;
+;
+; This sample zone file illustrates sharing the same IP addresses for multiple services:
+;
+services A 10.0.1.10
+ AAAA aaaa:bbbb::10
+ A 10.0.1.11
+ AAAA aaaa:bbbb::11
+
+ftp CNAME services.example.com.
+www CNAME services.example.com.
+;
+;
+</pre><div class="para">
+ In this example, standard directives and <code class="command">SOA</code> values are used. The authoritative nameservers are set as <code class="command">dns1.example.com</code> and <code class="command">dns2.example.com</code>, which have <code class="command">A</code> records that tie them to <code class="command">10.0.1.1</code> and <code class="command">10.0.1.2</code>, respectively.
+ </div><div class="para">
+ The email servers configured with the <code class="command">MX</code> records point to <code class="command">mail</code> and <code class="command">mail2</code> via <code class="command">A</code> records. Since the <code class="command">mail</code> and <code class="command">mail2</code> names do not end in a trailing period (<code class="command">.</code>), the <code class="command">$ORIGIN</code> domain is placed after them, expanding them to <code class="command">mail.example.com</code> and <code class="command">mail2.example.com</code>. Through the related <code class="command">A</code> resource records, their IP addresses can be determined.
+ </div><div class="para">
+ Services available at the standard names, such as <code class="command">www.example.com</code> (<acronym class="acronym">WWW</acronym>), are pointed at the appropriate servers using a <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">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><ul class="docnav"><li class="previous"><a accesskey="p" href="s3-bind-zone-rr.html"><strong>Prev</strong>7.3.2. Zone File 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-configuration-zone-reverse.html"><strong>Next</strong>7.3.4. Reverse Name Resolution Zone Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-mta-fetchmail.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-mta-fetchmail.html
new file mode 100644
index 0000000..7bbe27a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-mta-fetchmail.html
@@ -0,0 +1,105 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-mta.html" title="13.3. Mail Transport Agents" /><link rel="prev" href="s2-email-mta-postfix.html" title="13.3.2. Postfix" /><link rel="next" href="s1-email-switchmail.html" title="13.4. Mail Transport Agent (MTA) Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe d
isplay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-postfix.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-email-switchmail.html"><strong>Next</strong></a></li></ul><div class="section" title="13.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">13.3.3. Fetchmail</h3></div></div></div><a id="id598401" class="indexterm"></a><a id="id598416" 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 POP3 and IMAP. It can even forward email messages to an SMTP server, if necessary.
+ </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.
+ </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 25 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="13.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">13.3.3.1. Fetchmail Configuration Options</h4></div></div></div><a id="id940548" class="indexterm"></a><a id="id940563" 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 <code class="filename">.fetchmailrc</code> because it only checks skipped servers when specifically invoked, and does not affect any currently working configurations.
+ </div><div class="para">
+ A sample <code class="filename">.fetchmailrc</code> file looks similar to the following example:
+ </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 POP3, 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"><h2>Note</h2><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 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 here.
+ </div></div><div class="section" title="13.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">13.3.3.2. Global Options</h4></div></div></div><a id="id970569" class="indexterm"></a><a id="id970588" 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="13.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">13.3.3.3. Server Options</h4></div></div></div><a id="id990285" class="indexterm"></a><a id="id990304" 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="13.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">13.3.3.4. User Options</h4></div></div></div><a id="id765508" class="indexterm"></a><a id="id765526" 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="13.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">13.3.3.5. Fetchmail Command Options</h4></div></div></div><a id="id892553" 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="13.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">13.3.3.6. Informational or Debugging Options</h4></div></div></div><a id="id759827" 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="13.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">13.3.3.7. Special Options</h4></div></div></div><a id="id759928" 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-postfix.html"><strong>Prev</strong>13.3.2. Postfix</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-switchmail.html"><strong>Next</strong>13.4. Mail Transport Agent (MTA) Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-mta-postfix.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-mta-postfix.html
new file mode 100644
index 0000000..a01095a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-mta-postfix.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.3.2. Postfix</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-mta.html" title="13.3. Mail Transport Agents" /><link rel="prev" href="s1-email-mta.html" title="13.3. Mail Transport Agents" /><link rel="next" href="s2-email-mta-fetchmail.html" title="13.3.3. Fetchmail" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-fetchmail.html"><strong>Next</strong></a></li></ul><div class="section" title="13.3.2. Postfix" id="s2-email-mta-postfix"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-mta-postfix">13.3.2. Postfix</h3></div></div></div><a id="id604192" class="indexterm"></a><a id="id604207" 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="13.3.2.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">13.3.2.1. The Default Postfix Installation</h4></div></div></div><a id="id604259" 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">aliases</code> — A configurable list required by the mail protocol.
+ </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="important"><h2>Important</h2><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="s2-email-mta-postfix.html#s3-email-mta-postfix-conf" title="13.3.2.2. Basic Postfix Configuration">Section 13.3.2.2, “Basic Postfix Configuration”</a>.
+ </div></div><div class="para">
+ When changing some options within files in the <code class="filename">/etc/postfix/</code> directory, it may be necessary to restart the <code class="command">postfix</code> service for the changes to take effect. The easiest way to do this is to type the following command:
+ </div><pre class="screen">
+<code class="command">/sbin/service postfix restart</code>
+</pre></div><div class="section" title="13.3.2.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">13.3.2.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 mark (<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 <code class="filename">/etc/postfix/main.cf</code>. Additional resources including information about LDAP and SpamAssassin integration are available online at <a href="http://www.postfix.org/">http://www.postfix.org/</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-mta.html"><strong>Prev</strong>13.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>13.3.3. Fetchmail</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-procmail-recipes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-procmail-recipes.html
new file mode 100644
index 0000000..7205b5d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-procmail-recipes.html
@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.5.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-mda.html" title="13.5. Mail Delivery Agents" /><link rel="prev" href="s1-email-mda.html" title="13.5. Mail Delivery Agents" /><link rel="next" href="s1-email-mua.html" title="13.6. Mail User Agents" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div>
<p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="13.5.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">13.5.2. Procmail Recipes</h3></div></div></div><a id="id899188" 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="13.5.2.5. Recipe Examples">Section 13.5.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 <code class="command">*</code> character can further control the condition.
+ </div><div class="para">
+ The <code class="command"><em class="replaceable"><code><action-to-perform></code></em> </code> 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="13.5.2.4. Special Conditions and Actions">Section 13.5.2.4, “Special Conditions and Actions”</a> for more information.
+ </div><div class="section" title="13.5.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">13.5.2.1. Delivering vs. Non-Delivering Recipes</h4></div></div></div><a id="id988304" class="indexterm"></a><a id="id988322" 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="13.5.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">13.5.2.2. Flags</h4></div></div></div><a id="id988385" 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 occurs by default.
+ </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="13.5.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">13.5.2.3. Specifying a Local Lockfile</h4></div></div></div><a id="id742948" 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="13.5.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">13.5.2.4. Special Conditions and Actions</h4></div></div></div><a id="id742995" class="indexterm"></a><a id="id743014" 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 <code class="command">*</code> character 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="13.5.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">13.5.2.5. Recipe Examples</h4></div></div></div><a id="id1012176" 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"><h2>Caution</h2><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 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="13.7. Additional Resources">Section 13.7, “Additional Resources”</a> for more detailed and powerful recipes.
+ </div></div><div class="section" title="13.5.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">13.5.2.6. Spam Filters</h4></div></div></div><a id="id605549" class="indexterm"></a><a id="id605568" class="indexterm"></a><a id="id1013222" 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="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="command">spamd</code>) and client application (<code class="command">spamc</code>). Configuring SpamAssassin this way, however, requires root access to the host.
+ </div><div class="para">
+ To start the <code class="command">spamd</code> daemon, type the following command as root:
+ </div><pre class="screen">
+<code class="command">/sbin/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 6. Controlling Access to Services">Chapter 6, <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>13.5. 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>13.6. Mail User Agents</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-related-books.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-related-books.html
new file mode 100644
index 0000000..a863438
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-related-books.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.7.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-additional-resources.html" title="13.7. Additional Resources" /><link rel="prev" href="s2-email-useful-websites.html" title="13.7.2. Useful Websites" /><link rel="next" href="ch-Lightweight_Directory_Access_Protocol_LDAP.html" title="Chapter 14. Lightweight Directory Access Protocol (LDAP)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">
This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="ch-Lightweight_Directory_Access_Protocol_LDAP.html"><strong>Next</strong></a></li></ul><div class="section" title="13.7.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">13.7.3. Related Books</h3></div></div></div><a id="id2001437" 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>13.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="ch-Lightweight_Directory_Access_Protocol_LDAP.html"><strong>Next</strong>Chapter 14. Lightweight Directory Access Protocol...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-types-mda.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-types-mda.html
new file mode 100644
index 0000000..3bedbe3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-types-mda.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-types.html" title="13.2. Email Program Classifications" /><link rel="prev" href="s1-email-types.html" title="13.2. Email Program Classifications" /><link rel="next" href="s2-email-types-mua.html" title="13.2.3. Mail User Agent" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enabl
e iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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" href="s2-email-types-mua.html"><strong>Next</strong></a></li></ul><div class="section" title="13.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">13.2.2. Mail Delivery Agent</h3></div></div></div><a id="id934946" class="indexterm"></a><a id="id726066" class="indexterm"></a><a id="id726079" 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>13.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>13.2.3. Mail User Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-types-mua.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-types-mua.html
new file mode 100644
index 0000000..367ef3c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-types-mua.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-types.html" title="13.2. Email Program Classifications" /><link rel="prev" href="s2-email-types-mda.html" title="13.2.2. Mail Delivery Agent" /><link rel="next" href="s1-email-mta.html" title="13.3. Mail Transport Agents" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe d
isplay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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" href="s1-email-mta.html"><strong>Next</strong></a></li></ul><div class="section" title="13.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">13.2.3. Mail User Agent</h3></div></div></div><a id="id726136" class="indexterm"></a><a id="id726153" class="indexterm"></a><a id="id726167" 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 POP or IMAP protocols, setting up mailboxes to store messages, and sending outbound messages to an MTA.
+ </div><div class="para">
+ MUAs may be graphical, such as Evolution, or have simple text-based interfaces, such as <code class="command">pine</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-types-mda.html"><strong>Prev</strong>13.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>13.3. Mail Transport Agents</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-useful-websites.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-useful-websites.html
new file mode 100644
index 0000000..07a3a3a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-email-useful-websites.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>13.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-additional-resources.html" title="13.7. Additional Resources" /><link rel="prev" href="s1-email-additional-resources.html" title="13.7. Additional Resources" /><link rel="next" href="s2-email-related-books.html" title="13.7.3. Related Books" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browse
r or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="next"><a accesskey="n" href="s2-email-related-books.html"><strong>Next</strong></a></li></ul><div class="section" title="13.7.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">13.7.2. Useful Websites</h3></div></div></div><a id="id1005357" 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>13.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="s2-email-related-books.html"><strong>Next</strong>13.7.3. Related Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-useful-websites.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-useful-websites.html
new file mode 100644
index 0000000..1653e3b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-useful-websites.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ftp-resources.html" title="12.6. Additional Resources" /><link rel="prev" href="s1-ftp-resources.html" title="12.6. Additional Resources" /><link rel="next" href="ch-email.html" title="Chapter 13. Email" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><
p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-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="12.6.2. Useful Websites" id="s2-ftp-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-useful-websites">12.6.2. Useful Websites</h3></div></div></div><a id="id1015332" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://vsftpd.beasts.org/">http://vsftpd.beasts.org/</a> — The <code class="command">vsftpd</code> project page is a great place to locate the latest documentation and to contact the author of the software.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://slacksite.com/other/ftp.html">http://slacksite.com/other/ftp.html</a> — This website provides a concise explanation of the differences between active and passive mode FTP.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.ietf.org/rfc/rfc0959.txt">http://www.ietf.org/rfc/rfc0959.txt</a> — The original <em class="firstterm">Request for Comments</em> (<em class="firstterm">RFC</em>) of the FTP protocol from the IETF.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ftp-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="ch-email.html"><strong>Next</strong>Chapter 13. Email</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-anon.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-anon.html
new file mode 100644
index 0000000..444ed63
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-anon.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>12.5.3. Anonymous User 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options" /><link rel="prev" href="s2-ftp-vsftpd-conf-opt-login.html" title="12.5.2. Log In Options and Access Controls" /><link rel="next" href="s2-ftp-vsftpd-conf-opt-usr.html" title="12.5.4. Local User Options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, t
o view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-vsftpd-conf-opt-login.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ftp-vsftpd-conf-opt-usr.html"><strong>Next</strong></a></li></ul><div class="section" title="12.5.3. Anonymous User Options" id="s2-ftp-vsftpd-conf-opt-anon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-anon">12.5.3. Anonymous User Options</h3></div></div></div><a id="id728916" class="indexterm"></a><div class="para">
+ The following lists directives which control anonymous user access to the server. To use these options, the <code class="command">anonymous_enable</code> directive must be set to <code class="command">YES</code>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">anon_mkdir_write_enable</code> — When enabled in conjunction with the <code class="command">write_enable</code> directive, anonymous users are allowed to create new directories within a parent directory which has write permissions.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">anon_root</code> — Specifies the directory <code class="command">vsftpd</code> changes to after an anonymous user logs in.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">anon_upload_enable</code> — When enabled in conjunction with the <code class="command">write_enable</code> directive, anonymous users are allowed to upload files within a parent directory which has write permissions.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">anon_world_readable_only</code> — When enabled, anonymous users are only allowed to download world-readable files.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ftp_username</code> — Specifies the local user account (listed in <code class="filename">/etc/passwd</code>) used for the anonymous FTP user. The home directory specified in <code class="filename">/etc/passwd</code> for the user is the root directory of the anonymous FTP user.
+ </div><div class="para">
+ The default value is <code class="command">ftp</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no_anon_password</code> — When enabled, the anonymous user is not asked for a password.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">secure_email_list_enable</code> — When enabled, only a specified list of email passwords for anonymous logins are accepted. This is a convenient way to offer limited security to public content without the need for virtual users.
+ </div><div class="para">
+ Anonymous logins are prevented unless the password provided is listed in <code class="command">/etc/vsftpd.email_passwords</code>. The file format is one password per line, with no trailing white spaces.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-vsftpd-conf-opt-login.html"><strong>Prev</strong>12.5.2. Log In Options and Access Controls</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ftp-vsftpd-conf-opt-usr.html"><strong>Next</strong>12.5.4. Local User Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-dir.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-dir.html
new file mode 100644
index 0000000..22de259
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-dir.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>12.5.5. Directory 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options" /><link rel="prev" href="s2-ftp-vsftpd-conf-opt-usr.html" title="12.5.4. Local User Options" /><link rel="next" href="s2-ftp-vsftpd-conf-opt-file.html" title="12.5.6. File Transfer Options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade y
our browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-vsftpd-conf-opt-usr.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ftp-vsftpd-conf-opt-file.html"><strong>Next</strong></a></li></ul><div class="section" title="12.5.5. Directory Options" id="s2-ftp-vsftpd-conf-opt-dir"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-dir">12.5.5. Directory Options</h3></div></div></div><a id="id720121" class="indexterm"></a><div class="para">
+ The following lists directives which affect directories.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">dirlist_enable</code> — When enabled, users are allowed to view directory lists.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">dirmessage_enable</code> — When enabled, a message is displayed whenever a user enters a directory with a message file. This message resides within the current directory. The name of this file is specified in the <code class="command">message_file</code> directive and is <code class="filename">.message</code> by default.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>. Note, in Fedora, the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">force_dot_files</code> — When enabled, files beginning with a dot (<code class="computeroutput">.</code>) are listed in directory listings, with the exception of the <code class="filename">.</code> and <code class="filename">..</code> files.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">hide_ids</code> — When enabled, all directory listings show <code class="computeroutput">ftp</code> as the user and group for each file.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">message_file</code> — Specifies the name of the message file when using the <code class="command">dirmessage_enable</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">.message</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">text_userdb_names</code> — When enabled, test usernames and group names are used in place of UID and GID entries. Enabling this option may slow performance of the server.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">use_localtime</code> — When enabled, directory listings reveal the local time for the computer instead of GMT.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-vsftpd-conf-opt-usr.html"><strong>Prev</strong>12.5.4. Local User 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-ftp-vsftpd-conf-opt-file.html"><strong>Next</strong>12.5.6. File Transfer Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-file.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-file.html
new file mode 100644
index 0000000..77d07b2
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-file.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>12.5.6. File Transfer 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options" /><link rel="prev" href="s2-ftp-vsftpd-conf-opt-dir.html" title="12.5.5. Directory Options" /><link rel="next" href="s2-ftp-vsftpd-conf-opt-log.html" title="12.5.7. Logging Options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your
browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-vsftpd-conf-opt-dir.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ftp-vsftpd-conf-opt-log.html"><strong>Next</strong></a></li></ul><div class="section" title="12.5.6. File Transfer Options" id="s2-ftp-vsftpd-conf-opt-file"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-file">12.5.6. File Transfer Options</h3></div></div></div><a id="id829885" class="indexterm"></a><div class="para">
+ The following lists directives which affect directories.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">download_enable</code> — When enabled, file downloads are permitted.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">chown_uploads</code> — When enabled, all files uploaded by anonymous users are owned by the user specified in the <code class="command">chown_username</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">chown_username</code> — Specifies the ownership of anonymously uploaded files if the <code class="command">chown_uploads</code> directive is enabled.
+ </div><div class="para">
+ The default value is <code class="command">root</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">write_enable</code> — When enabled, FTP commands which can change the file system are allowed, such as <code class="command">DELE</code>, <code class="command">RNFR</code>, and <code class="command">STOR</code>.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-vsftpd-conf-opt-dir.html"><strong>Prev</strong>12.5.5. Directory 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-ftp-vsftpd-conf-opt-log.html"><strong>Next</strong>12.5.7. Logging Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-log.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-log.html
new file mode 100644
index 0000000..aa5be09
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-log.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>12.5.7. Logging 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options" /><link rel="prev" href="s2-ftp-vsftpd-conf-opt-file.html" title="12.5.6. File Transfer Options" /><link rel="next" href="s2-ftp-vsftpd-conf-opt-net.html" title="12.5.8. Network Options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your b
rowser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-vsftpd-conf-opt-file.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ftp-vsftpd-conf-opt-net.html"><strong>Next</strong></a></li></ul><div class="section" title="12.5.7. Logging Options" id="s2-ftp-vsftpd-conf-opt-log"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-log">12.5.7. Logging Options</h3></div></div></div><a id="id856562" class="indexterm"></a><div class="para">
+ The following lists directives which affect <code class="command">vsftpd</code>'s logging behavior.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">dual_log_enable</code> — When enabled in conjunction with <code class="command">xferlog_enable</code>, <code class="command">vsftpd</code> writes two files simultaneously: a <code class="command">wu-ftpd</code>-compatible log to the file specified in the <code class="command">xferlog_file</code> directive (<code class="filename">/var/log/xferlog</code> by default) and a standard <code class="command">vsftpd</code> log file specified in the <code class="command">vsftpd_log_file</code> directive (<code class="filename">/var/log/vsftpd.log</code> by default).
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">log_ftp_protocol</code> — When enabled in conjunction with <code class="command">xferlog_enable</code> and with <code class="command">xferlog_std_format</code> set to <code class="command">NO</code>, all FTP commands and responses are logged. This directive is useful for debugging.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">syslog_enable</code> — When enabled in conjunction with <code class="command">xferlog_enable</code>, all logging normally written to the standard <code class="command">vsftpd</code> log file specified in the <code class="command">vsftpd_log_file</code> directive (<code class="filename">/var/log/vsftpd.log</code> by default) is sent to the system logger instead under the FTPD facility.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">vsftpd_log_file</code> — Specifies the <code class="command">vsftpd</code> log file. For this file to be used, <code class="command">xferlog_enable</code> must be enabled and <code class="command">xferlog_std_format</code> must either be set to <code class="command">NO</code> or, if <code class="command">xferlog_std_format</code> is set to <code class="command">YES</code>, <code class="command">dual_log_enable</code> must be enabled. It is important to note that if <code class="command">syslog_enable</code> is set to <code class="command">YES</code>, the system log is used instead of the file specified in this directive.
+ </div><div class="para">
+ The default value is <code class="filename">/var/log/vsftpd.log</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">xferlog_enable</code> — When enabled, <code class="command">vsftpd</code> logs connections (<code class="command">vsftpd</code> format only) and file transfer information to the log file specified in the <code class="command">vsftpd_log_file</code> directive (<code class="filename">/var/log/vsftpd.log</code> by default). If <code class="command">xferlog_std_format</code> is set to <code class="command">YES</code>, file transfer information is logged but connections are not, and the log file specified in <code class="command">xferlog_file</code> (<code class="filename">/var/log/xferlog</code> by default) is used instead. It is important to note that both log files and log formats are used if <code class="command">dual_log_enable</code> is set to <code class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>. Note, in Fedora, the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">xferlog_file</code> — Specifies the <code class="command">wu-ftpd</code>-compatible log file. For this file to be used, <code class="command">xferlog_enable</code> must be enabled and <code class="command">xferlog_std_format</code> must be set to <code class="command">YES</code>. It is also used if <code class="command">dual_log_enable</code> is set to <code class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code class="filename">/var/log/xferlog</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">xferlog_std_format</code> — When enabled in conjunction with <code class="command">xferlog_enable</code>, only a <code class="command">wu-ftpd</code>-compatible file transfer log is written to the file specified in the <code class="command">xferlog_file</code> directive (<code class="filename">/var/log/xferlog</code> by default). It is important to note that this file only logs file transfers and does not log connections to the server.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>. Note, in Fedora, the value is set to <code class="command">YES</code>.
+ </div></li></ul></div><div class="important"><h2>Important</h2><div class="para">
+ To maintain compatibility with log files written by the older <code class="command">wu-ftpd</code> FTP server, the <code class="command">xferlog_std_format</code> directive is set to <code class="command">YES</code> under Fedora. However, this setting means that connections to the server are not logged.
+ </div><div class="para">
+ To both log connections in <code class="command">vsftpd</code> format and maintain a <code class="command">wu-ftpd</code>-compatible file transfer log, set <code class="command">dual_log_enable</code> to <code class="command">YES</code>.
+ </div><div class="para">
+ If maintaining a <code class="command">wu-ftpd</code>-compatible file transfer log is not important, either set <code class="command">xferlog_std_format</code> to <code class="command">NO</code>, comment the line with a hash mark (<code class="command">#</code>), or delete the line entirely.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-vsftpd-conf-opt-file.html"><strong>Prev</strong>12.5.6. File Transfer 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-ftp-vsftpd-conf-opt-net.html"><strong>Next</strong>12.5.8. Network Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-login.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-login.html
new file mode 100644
index 0000000..358dd35
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-login.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.2. Log In Options and Access Controls</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options" /><link rel="prev" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options" /><link rel="next" href="s2-ftp-vsftpd-conf-opt-anon.html" title="12.5.3. Anonymous User Options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, t
o view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-vsftpd-conf.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ftp-vsftpd-conf-opt-anon.html"><strong>Next</strong></a></li></ul><div class="section" title="12.5.2. Log In Options and Access Controls" id="s2-ftp-vsftpd-conf-opt-login"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-login">12.5.2. Log In Options and Access Controls</h3></div></div></div><a id="id909036" class="indexterm"></a><a id="id909058" class="indexterm"></a><div class="para">
+ The following is a list of directives which control the login behavior and access control mechanisms.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">anonymous_enable</code> — When enabled, anonymous users are allowed to log in. The usernames <code class="computeroutput">anonymous</code> and <code class="computeroutput">ftp</code> are accepted.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div><div class="para">
+ Refer to <a class="xref" href="s2-ftp-vsftpd-conf-opt-anon.html" title="12.5.3. Anonymous User Options">Section 12.5.3, “Anonymous User Options”</a> for a list of directives affecting anonymous users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">banned_email_file</code> — If the <code class="command">deny_email_enable</code> directive is set to <code class="command">YES</code>, this directive specifies the file containing a list of anonymous email passwords which are not permitted access to the server.
+ </div><div class="para">
+ The default value is <code class="filename">/etc/vsftpd.banned_emails</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">banner_file</code> — Specifies the file containing text displayed when a connection is established to the server. This option overrides any text specified in the <code class="command">ftpd_banner</code> directive.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">cmds_allowed</code> — Specifies a comma-delimited list of FTP commands allowed by the server. All other commands are rejected.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">deny_email_enable</code> — When enabled, any anonymous user utilizing email passwords specified in the <code class="filename">/etc/vsftpd.banned_emails</code> are denied access to the server. The name of the file referenced by this directive can be specified using the <code class="command">banned_email_file</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ftpd_banner</code> — When enabled, the string specified within this directive is displayed when a connection is established to the server. This option can be overridden by the <code class="command">banner_file</code> directive.
+ </div><div class="para">
+ By default <code class="command">vsftpd</code> displays its standard banner.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">local_enable</code> — When enabled, local users are allowed to log into the system.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div><div class="para">
+ Refer to <a class="xref" href="s2-ftp-vsftpd-conf-opt-usr.html" title="12.5.4. Local User Options">Section 12.5.4, “Local User Options”</a> for a list of directives affecting local users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pam_service_name</code> — Specifies the PAM service name for <code class="command">vsftpd</code>.
+ </div><div class="para">
+ The default value is <code class="command">ftp</code>. Note, in Fedora, the value is set to <code class="command">vsftpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ The default value is <code class="command">NO</code>. Note, in Fedora, the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">userlist_deny</code> — When used in conjunction with the <code class="command">userlist_enable</code> directive and set to <code class="command">NO</code>, all local users are denied access unless the username is listed in the file specified by the <code class="command">userlist_file</code> directive. Because access is denied before the client is asked for a password, setting this directive to <code class="command">NO</code> prevents local users from submitting unencrypted passwords over the network.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">userlist_enable</code> — When enabled, the users listed in the file specified by the <code class="command">userlist_file</code> directive are denied access. Because access is denied before the client is asked for a password, users are prevented from submitting unencrypted passwords over the network.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>, however under Fedora the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">userlist_file</code> — Specifies the file referenced by <code class="command">vsftpd</code> when the <code class="command">userlist_enable</code> directive is enabled.
+ </div><div class="para">
+ The default value is <code class="command">/etc/vsftpd.user_list</code> and is created during installation.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ftp-vsftpd-conf.html"><strong>Prev</strong>12.5. vsftpd Configuration 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-ftp-vsftpd-conf-opt-anon.html"><strong>Next</strong>12.5.3. Anonymous User Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-net.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-net.html
new file mode 100644
index 0000000..a68d801
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-net.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>12.5.8. Network 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options" /><link rel="prev" href="s2-ftp-vsftpd-conf-opt-log.html" title="12.5.7. Logging Options" /><link rel="next" href="s1-ftp-resources.html" title="12.6. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enab
le iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-vsftpd-conf-opt-log.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ftp-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="12.5.8. Network Options" id="s2-ftp-vsftpd-conf-opt-net"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-net">12.5.8. Network Options</h3></div></div></div><a id="id719075" class="indexterm"></a><div class="para">
+ The following lists directives which affect how <code class="command">vsftpd</code> interacts with the network.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">accept_timeout</code> — Specifies the amount of time for a client using passive mode to establish a connection.
+ </div><div class="para">
+ The default value is <code class="command">60</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">anon_max_rate</code> — Specifies the maximum data transfer rate for anonymous users in bytes per second.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit the transfer rate.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">connect_from_port_20</code> When enabled, <code class="command">vsftpd</code> runs with enough privileges to open port 20 on the server during active mode data transfers. Disabling this option allows <code class="command">vsftpd</code> to run with less privileges, but may be incompatible with some FTP clients.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>. Note, in Fedora, the value is set to <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">connect_timeout</code> — Specifies the maximum amount of time a client using active mode has to respond to a data connection, in seconds.
+ </div><div class="para">
+ The default value is <code class="command">60</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">data_connection_timeout</code> — Specifies maximum amount of time data transfers are allowed to stall, in seconds. Once triggered, the connection to the remote client is closed.
+ </div><div class="para">
+ The default value is <code class="command">300</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ftp_data_port</code> — Specifies the port used for active data connections when <code class="command">connect_from_port_20</code> is set to <code class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code class="command">20</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">idle_session_timeout</code> — Specifies the maximum amount of time between commands from a remote client. Once triggered, the connection to the remote client is closed.
+ </div><div class="para">
+ The default value is <code class="command">300</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">listen_address</code> — Specifies the IP address on which <code class="command">vsftpd</code> listens for network connections.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div><div class="note"><h2>Tip</h2><div class="para">
+ If running multiple copies of <code class="command">vsftpd</code> serving different IP addresses, the configuration file for each copy of the <code class="command">vsftpd</code> daemon must have a different value for this directive. Refer to <a class="xref" href="s1-ftp-vsftpd-start.html#s2-ftp-vsftpd-start-multi" title="12.4.1. Starting Multiple Copies of vsftpd">Section 12.4.1, “Starting Multiple Copies of <code class="command">vsftpd</code> ”</a> for more information about multihomed FTP servers.
+ </div></div></li><li class="listitem"><div class="para">
+ <code class="command">listen_address6</code> — Specifies the IPv6 address on which <code class="command">vsftpd</code> listens for network connections when <code class="command">listen_ipv6</code> is set to <code class="command">YES</code>.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div><div class="note"><h2>Tip</h2><div class="para">
+ If running multiple copies of <code class="command">vsftpd</code> serving different IP addresses, the configuration file for each copy of the <code class="command">vsftpd</code> daemon must have a different value for this directive. Refer to <a class="xref" href="s1-ftp-vsftpd-start.html#s2-ftp-vsftpd-start-multi" title="12.4.1. Starting Multiple Copies of vsftpd">Section 12.4.1, “Starting Multiple Copies of <code class="command">vsftpd</code> ”</a> for more information about multihomed FTP servers.
+ </div></div></li><li class="listitem"><div class="para">
+ <code class="command">listen_port</code> — Specifies the port on which <code class="command">vsftpd</code> listens for network connections.
+ </div><div class="para">
+ The default value is <code class="command">21</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">local_max_rate</code> — Specifies the maximum rate data is transferred for local users logged into the server in bytes per second.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit the transfer rate.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">max_clients</code> — Specifies the maximum number of simultaneous clients allowed to connect to the server when it is running in standalone mode. Any additional client connections would result in an error message.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit connections.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">max_per_ip</code> — Specifies the maximum of clients allowed to connected from the same source IP address.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit connections.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pasv_address</code> — Specifies the IP address for the public facing IP address of the server for servers behind Network Address Translation (NAT) firewalls. This enables <code class="command">vsftpd</code> to hand out the correct return address for passive mode connections.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pasv_enable</code> — When enabled, passive mode connects are allowed.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pasv_max_port</code> — Specifies the highest possible port sent to the FTP clients for passive mode connections. This setting is used to limit the port range so that firewall rules are easier to create.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit the highest passive port range. The value must not exceed <code class="command">65535</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pasv_min_port</code> — Specifies the lowest possible port sent to the FTP clients for passive mode connections. This setting is used to limit the port range so that firewall rules are easier to create.
+ </div><div class="para">
+ The default value is <code class="command">0</code>, which does not limit the lowest passive port range. The value must not be lower <code class="command">1024</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pasv_promiscuous</code> — When enabled, data connections are not checked to make sure they are originating from the same IP address. This setting is only useful for certain types of tunneling.
+ </div><div class="warning"><h2>Caution</h2><div class="para">
+ Do not enable this option unless absolutely necessary as it disables an important security feature which verifies that passive mode connections originate from the same IP address as the control connection that initiates the data transfer.
+ </div></div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">port_enable</code> — When enabled, active mode connects are allowed.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-vsftpd-conf-opt-log.html"><strong>Prev</strong>12.5.7. Logging 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="s1-ftp-resources.html"><strong>Next</strong>12.6. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-usr.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-usr.html
new file mode 100644
index 0000000..ed31df8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf-opt-usr.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>12.5.4. Local User 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options" /><link rel="prev" href="s2-ftp-vsftpd-conf-opt-anon.html" title="12.5.3. Anonymous User Options" /><link rel="next" href="s2-ftp-vsftpd-conf-opt-dir.html" title="12.5.5. Directory Options" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade
your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-vsftpd-conf-opt-anon.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ftp-vsftpd-conf-opt-dir.html"><strong>Next</strong></a></li></ul><div class="section" title="12.5.4. Local User Options" id="s2-ftp-vsftpd-conf-opt-usr"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ftp-vsftpd-conf-opt-usr">12.5.4. Local User Options</h3></div></div></div><a id="id955042" class="indexterm"></a><div class="para">
+ The following lists directives which characterize the way local users access the server. To use these options, the <code class="command">local_enable</code> directive must be set to <code class="command">YES</code>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">chmod_enable</code> — When enabled, the FTP command <code class="command">SITE CHMOD</code> is allowed for local users. This command allows the users to change the permissions on files.
+ </div><div class="para">
+ The default value is <code class="command">YES</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">chroot_list_enable</code> — When enabled, the local users listed in the file specified in the <code class="command">chroot_list_file</code> directive are placed in a <code class="command">chroot</code> jail upon log in.
+ </div><div class="para">
+ If enabled in conjunction with the <code class="command">chroot_local_user</code> directive, the local users listed in the file specified in the <code class="command">chroot_list_file</code> directive are <span class="emphasis"><em>not</em></span> placed in a <code class="command">chroot</code> jail upon log in.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">chroot_list_file</code> — Specifies the file containing a list of local users referenced when the <code class="command">chroot_list_enable</code> directive is set to <code class="command">YES</code>.
+ </div><div class="para">
+ The default value is <code class="command">/etc/vsftpd.chroot_list</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">chroot_local_user</code> — When enabled, local users are change-rooted to their home directories after logging in.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div><div class="warning"><h2>Warning</h2><div class="para">
+ Enabling <code class="command">chroot_local_user</code> opens up a number of security issues, especially for users with upload privileges. For this reason, it is <span class="emphasis"><em>not</em></span> recommended.
+ </div></div></li><li class="listitem"><div class="para">
+ <code class="command">guest_enable</code> — When enabled, all non-anonymous users are logged in as the user <code class="command">guest</code>, which is the local user specified in the <code class="command">guest_username</code> directive.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">guest_username</code> — Specifies the username the <code class="command">guest</code> user is mapped to.
+ </div><div class="para">
+ The default value is <code class="command">ftp</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">local_root</code> — Specifies the directory <code class="command">vsftpd</code> changes to after a local user logs in.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">local_umask</code> — Specifies the umask value for file creation. Note that the default value is in octal form (a numerical system with a base of eight), which includes a "0" prefix. Otherwise the value is treated as a base-10 integer.
+ </div><div class="para">
+ The default value is <code class="command">022</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">passwd_chroot_enable</code> — When enabled in conjunction with the <code class="command">chroot_local_user</code> directive, <code class="command">vsftpd</code> change-roots local users based on the occurrence of the <code class="command">/./</code> in the home directory field within <code class="filename">/etc/passwd</code>.
+ </div><div class="para">
+ The default value is <code class="command">NO</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">user_config_dir</code> — Specifies the path to a directory containing configuration files bearing the name of local system users that contain specific setting for that user. Any directive in the user's configuration file overrides those found in <code class="filename">/etc/vsftpd/vsftpd.conf</code>.
+ </div><div class="para">
+ There is no default value for this directive.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-vsftpd-conf-opt-anon.html"><strong>Prev</strong>12.5.3. Anonymous User 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-ftp-vsftpd-conf-opt-dir.html"><strong>Next</strong>12.5.5. Directory Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf.html
new file mode 100644
index 0000000..b9b06c1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ftp-vsftpd-conf.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>12.3. Files Installed with vsftpd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-FTP.html" title="Chapter 12. FTP" /><link rel="prev" href="s1-ftp-servers.html" title="12.2. FTP Servers" /><link rel="next" href="s1-ftp-vsftpd-start.html" title="12.4. Starting and Stopping vsftpd" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe><
/div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ftp-servers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ftp-vsftpd-start.html"><strong>Next</strong></a></li></ul><div class="section" title="12.3. Files Installed with vsftpd" id="s2-ftp-vsftpd-conf"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s2-ftp-vsftpd-conf">12.3. Files Installed with <code class="command">vsftpd</code> </h2></div></div></div><a id="id766660" class="indexterm"></a><div class="para">
+ The <code class="filename">vsftpd</code> RPM installs the daemon (<code class="filename">/usr/sbin/vsftpd</code>), its configuration and related files, as well as FTP directories onto the system. The following lists the files and directories related to <code class="command">vsftpd</code> configuration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/etc/rc.d/init.d/vsftpd</code> — The <span class="emphasis"><em>initialization script</em></span> (<em class="firstterm">initscript</em>) used by the <code class="command">/sbin/service</code> command to start, stop, or reload <code class="command">vsftpd</code>. Refer to <a class="xref" href="s1-ftp-vsftpd-start.html" title="12.4. Starting and Stopping vsftpd">Section 12.4, “Starting and Stopping <code class="command">vsftpd</code> ”</a> for more information about using this script.
+ </div></li><li xml:lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN" class="listitem" lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN"><div class="para">
+ <code class="filename">/etc/pam.d/vsftpd</code> — The Pluggable Authentication Modules (PAM) configuration file for <code class="command">vsftpd</code>. This file specifies the requirements a user must meet to login to the FTP server. For more information on PAM, refer to the <em class="citetitle">Pluggable Authentication Modules (PAM)</em> chapter of the Fedora 13 <em class="citetitle">Security Guide</em>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/vsftpd/vsftpd.conf</code> — The configuration file for <code class="command">vsftpd</code>. Refer to <a class="xref" href="s1-ftp-vsftpd-conf.html" title="12.5. vsftpd Configuration Options">Section 12.5, “ <code class="command">vsftpd</code> Configuration Options”</a> for a list of important options contained within this file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/vsftpd.ftpusers</code> — A list of users not allowed to log into <code class="command">vsftpd</code>. By default, this list includes the <code class="command">root</code>, <code class="command">bin</code>, and <code class="command">daemon</code> users, among others.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/etc/vsftpd.user_list</code> — This file can be configured to either deny or allow access to the users listed, depending on whether the <code class="command">userlist_deny</code> directive is set to <code class="command">YES</code> (default) or <code class="command">NO</code> in <code class="filename">/etc/vsftpd/vsftpd.conf</code>. If <code class="filename">/etc/vsftpd.user_list</code> is used to grant access to users, the usernames listed must <span class="emphasis"><em>not</em></span> appear in <code class="filename">/etc/vsftpd.ftpusers</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/var/ftp/</code> — The directory containing files served by <code class="command">vsftpd</code>. It also contains the <code class="filename">/var/ftp/pub/</code> directory for anonymous users. Both directories are world-readable, but writable only by the root user.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ftp-servers.html"><strong>Prev</strong>12.2. FTP Servers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ftp-vsftpd-start.html"><strong>Next</strong>12.4. Starting and Stopping vsftpd </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-httpd-default-settings.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-httpd-default-settings.html
new file mode 100644
index 0000000..19d1675
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-httpd-default-settings.html
@@ -0,0 +1,139 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Default 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-config-ui.html" title="11.4. Apache HTTP Server Configuration" /><link rel="prev" href="s1-apache-config-ui.html" title="11.4. Apache HTTP Server Configuration" /><link rel="next" href="s1-apache-config.html" title="11.5. Configuration Directives in httpd.conf" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-config-ui.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-config.html"><strong>Next</strong></a></li></ul><div class="section" title="11.4.2. Default Settings" id="s2-httpd-default-settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-httpd-default-settings">11.4.2. Default Settings</h3></div></div></div><div class="para">
+ After defining the <span class="guilabel"><strong>Server Name</strong></span>, <span class="guilabel"><strong>Webmaster email address</strong></span>, and <span class="guilabel"><strong>Available Addresses</strong></span>, click the <span class="guilabel"><strong>Virtual Hosts</strong></span> tab. The figure below illustrates the <span class="guilabel"><strong>Virtual Hosts</strong></span> tab.
+ </div><div class="figure" title="Figure 11.3. Virtual Hosts Tab" id="httpd-virtual-hosts"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-virtualhosts.png" alt="Virtual Hosts Tab" /><div class="longdesc"><div class="para">
+ Virtual Hosts Tab
+ </div></div></div></div><h6>Figure 11.3. Virtual Hosts Tab</h6></div><br class="figure-break" /><div class="para">
+ Clicking on <span class="guilabel"><strong>Edit</strong></span> will display the <span class="guilabel"><strong>Virtual Host Properties</strong></span> window from which you can set your preferred settings. To add new settings, click on the <span class="guilabel"><strong>Add</strong></span> button which will also display the <span class="guilabel"><strong>Virtual Host Properties</strong></span> window. Clicking on the <span class="guilabel"><strong>Edit Default Settings</strong></span> button, displays the <span class="guilabel"><strong>Virtual Host Properties</strong></span> window without the <span class="guilabel"><strong>General Options</strong></span> tab.
+ </div><div class="para">
+ In the <span class="guilabel"><strong>General Options</strong></span> tab, you can change the hostname, the document root directory and also set the webmaster's email address. In the Host information, you can set the Virtual Host's IP Address and Host Name. The figure below illustrates the <span class="guilabel"><strong>General Options</strong></span> tab.
+ </div><div class="figure" title="Figure 11.4. General Options" id="httpd-general-options"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-general-options.png" width="444" alt="General Options" /><div class="longdesc"><div class="para">
+ General Options
+ </div></div></div></div><h6>Figure 11.4. General Options</h6></div><br class="figure-break" /><div class="para">
+ If you add a virtual host, the settings you configure for the virtual host take precedence for that virtual host. For a directive not defined within the virtual host settings, the default value is used.
+ </div><div class="section" title="11.4.2.1. Site Configuration" id="s3-httpd-site-config"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-httpd-site-config">11.4.2.1. Site Configuration</h4></div></div></div><div class="para">
+ The figure below illustrates the <span class="guibutton"><strong>Page Options</strong></span>tab from which you can configure the <span class="guilabel"><strong>Directory Page Search List</strong></span> and <span class="guilabel"><strong>Error Pages</strong></span>. If you are unsure of these settings, do not modify them.
+ </div><div class="figure" title="Figure 11.5. Site Configuration" id="httpd-site-config-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-siteconfig.png" width="444" alt="Site Configuration" /><div class="longdesc"><div class="para">
+ Site Configuration
+ </div></div></div></div><h6>Figure 11.5. Site Configuration</h6></div><br class="figure-break" /><a id="id663079" class="indexterm"></a><div class="para">
+ The entries listed in the <span class="guilabel"><strong>Directory Page Search List</strong></span> define the <a href="http://httpd.apache.org/docs/2.2/mod/mod_dir.html#directoryindex"><code class="command">DirectoryIndex</code> </a> directive. The <code class="command">DirectoryIndex</code> is the default page served by the server when a user requests an index of a directory by specifying a forward slash (/) at the end of the directory name.
+ </div><div class="para">
+ For example, when a user requests the page <code class="command">http://www.example.com/this_directory/</code>, they are going to get either the <code class="command">DirectoryIndex</code> page, if it exists, or a server-generated directory list. The server tries to find one of the files listed in the <code class="command">DirectoryIndex</code> directive and returns the first one it finds.
+ <a id="id663134" class="indexterm"></a>
+ If it does not find any of these files and if <code class="command">Options Indexes</code> is set for that directory, the server generates and returns a list, in HTML format, of the subdirectories and files in the directory.
+ </div><a id="id663159" class="indexterm"></a><div class="para">
+ Use the <span class="guilabel"><strong>Error Code</strong></span> section to configure Apache HTTP Server to redirect the client to a local or external URL in the event of a problem or error. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#errordocument"><code class="command">ErrorDocument</code> </a> directive. If a problem or error occurs when a client tries to connect to the Apache HTTP Server, the default action is to display the short error message shown in the <span class="guilabel"><strong>Error Code</strong></span> column. To override this default configuration, select the error code and click the <span class="guilabel"><strong>Edit</strong></span> button. Choose <span class="guimenuitem"><strong>Default</strong></span> to display the default short error message. Choose <span class="guimenuitem"><strong>URL</strong></span> to redirect the client to an external URL and enter a complete URL, including the <code class="command
">http://</code>, in the <span class="guilabel"><strong>Location</strong></span> field. Choose <span class="guimenuitem"><strong>File</strong></span> to redirect the client to an internal URL and enter a file location under the document root for the Web server. The location must begin the a slash (/) and be relative to the Document Root.
+ </div><div class="para">
+ For example, to redirect a 404 Not Found error code to a webpage that you created in a file called <code class="filename">404.html</code>, copy <code class="filename">404.html</code> to <code class="filename"><em class="replaceable"><code>DocumentRoot</code></em>/../error/404.html</code>. In this case, <em class="replaceable"><code>DocumentRoot</code></em> is the Document Root directory that you have defined (the default is <code class="filename">/var/www/html/</code>). If the Document Root is left as the default location, the file should be copied to <code class="filename">/var/www/error/404.html</code>. Then, choose <span class="guimenuitem"><strong>File</strong></span> as the Behavior for <span class="guilabel"><strong>404 - Not Found</strong></span> error code and enter <code class="filename">/error/404.html</code> as the <span class="guimenuitem"><strong>Location</strong></span>.
+ </div><div class="para">
+ From the <span class="guilabel"><strong>Default Error Page Footer</strong></span> menu, you can choose one of the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Show footer with email address</strong></span> — Display the default footer at the bottom of all error pages along with the email address of the website maintainer specified by the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#serveradmin"><code class="command">ServerAdmin</code> </a> directive.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Show footer</strong></span> — Display just the default footer at the bottom of error pages.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>No footer</strong></span> — Do not display a footer at the bottom of error pages.
+ </div></li></ul></div></div><div class="section" title="11.4.2.2. SSL Support" id="s3-httpd-ssl-variables"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-httpd-ssl-variables">11.4.2.2. SSL Support</h4></div></div></div><div class="para">
+ The <code class="command">mod_ssl</code> enables encryption of the HTTP protocol over SSL. SSL (Secure Sockets Layer) protocol is used for communication and encryption over TCP/IP networks. The SSL tab enables you to configure SSL for your server. To configure SSL you need to provide the path to your:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Certificate file - equivalent to using the <code class="command">SSLCertificateFile</code> directive which points the path to the PEM (Privacy Enhanced Mail)-encoded server certificate file.
+ </div></li><li class="listitem"><div class="para">
+ Key file - equivalent to using the <code class="command">SSLCertificateKeyFile</code> directive which points the path to the PEM-encoded server private key file.
+ </div></li><li class="listitem"><div class="para">
+ Certificate chain file - equivalent to using the <code class="command">SSLCertificateChainFile</code> directive which points the path to the certificate file containing all the server's chain of certificates.
+ </div></li><li class="listitem"><div class="para">
+ Certificate authority file - is an encrypted file used to confirm the authenticity or identity of parties communicating with the server.
+ </div></li></ul></div><div class="para">
+ You can find out more about configuration directives for SSL on <a href="http://httpd.apache.org/docs/2.2/mod/directives.html#S"> http://httpd.apache.org/docs/2.2/mod/directives.html#S</a>. You also need to determine which SSL options to enable. These are equivalent to using the <code class="command">SSLOptions</code> with the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ FakeBasicAuth - enables standard authentication methods used by Apache. This means that the Client X509 certificate's Subject Distinguished Name (DN) is translated into a basic HTTP username.
+ </div></li><li class="listitem"><div class="para">
+ ExportCertData - creates CGI environment variables in <code class="command">SSL_SERVER_CERT</code>, <code class="command">SSL_CLIENT_CERT</code> and <code class="command">SSL_CLIENT_CERT_CHAIN_n</code> where n is a number 0,1,2,3,4... These files are used for more certificate checks by CGI scripts.
+ </div></li><li class="listitem"><div class="para">
+ CompatEnvVars - enables backward compatibility for Apache SSL by adding CGI environment variables.
+ </div></li><li class="listitem"><div class="para">
+ StrictRequire - enables strict access which forces denial of access whenever the <code class="command">SSLRequireSSL</code> and <code class="command">SSLRequire</code> directives indicate access is forbiden.
+ </div></li><li class="listitem"><div class="para">
+ OptRenegotiate - enables avoidance of unnecessary handshakes by <code class="command">mod_ssl</code> which also performs safe parameter checks. It is recommended to enable OptRenegotiate on a per directory basis.
+ </div></li></ul></div><div class="para">
+ More information on the above SSL options can be found on <a href="http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#ssloptions"> http://httpd.apache.org/docs/2.2/mod/mod_ssl.html#ssloptions</a>. The figure below illustrates the SSL tab and the options discussed above.
+ </div><div class="figure" title="Figure 11.6. SSL" id="httpd-virtualhosts-ssl"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-virtualhosts-ssl.png" width="444" alt="SSL" /><div class="longdesc"><div class="para">
+ SSL
+ </div></div></div></div><h6>Figure 11.6. SSL</h6></div><br class="figure-break" /></div><div class="section" title="11.4.2.3. Logging" id="s3-httpd-logging"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-httpd-logging">11.4.2.3. Logging</h4></div></div></div><a id="id899396" class="indexterm"></a><a id="id899415" class="indexterm"></a><div class="para">
+ Use the <span class="guilabel"><strong>Logging</strong></span> tab to configure options for specific transfer and error logs.
+ </div><div class="para">
+ By default, the server writes the transfer log to the <code class="filename">/var/log/httpd/access_log</code> file and the error log to the <code class="filename">/var/log/httpd/error_log</code> file.
+ </div><div class="para">
+ The transfer log contains a list of all attempts to access the Web server. It records the IP address of the client that is attempting to connect, the date and time of the attempt, and the file on the Web server that it is trying to retrieve. Enter the name of the path and file in which to store this information. If the path and file name do not start with a slash (/), the path is relative to the server root directory as configured. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/mod_log_config.html#transferlog"><code class="command">TransferLog</code> </a> directive.
+ </div><div class="figure" title="Figure 11.7. Logging" id="httpd-logging-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-logging.png" width="444" alt="Logging" /><div class="longdesc"><div class="para">
+ Logging
+ </div></div></div></div><h6>Figure 11.7. Logging</h6></div><br class="figure-break" /><a id="id595475" class="indexterm"></a><a id="id595494" class="indexterm"></a><div class="para">
+ You can configure a custom log format by checking <span class="guilabel"><strong>Use custom logging facilities</strong></span> and entering a custom log string in the <span class="guilabel"><strong>Custom Log String</strong></span> field. This configures the <a href="http://httpd.apache.org/docs/2.2/mod/mod_log_config.html#logformat"><code class="command">LogFormat</code> </a> directive. Refer to <a href="http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#formats"> http://httpd.apache.org/docs/2.2/mod/mod_log_config.html#logformat</a> for details on the format of this directive.
+ </div><a id="id595540" class="indexterm"></a><div class="para">
+ The error log contains a list of any server errors that occur. Enter the name of the path and file in which to store this information. If the path and file name do not start with a slash (/), the path is relative to the server root directory as configured. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#errorlog"><code class="command">ErrorLog</code> </a> directive.
+ </div><a id="id595238" class="indexterm"></a><div class="para">
+ Use the <span class="guilabel"><strong>Log Level</strong></span> menu to set the verbosity of the error messages in the error logs. It can be set (from least verbose to most verbose) to emerg, alert, crit, error, warn, notice, info or debug. This option corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#loglevel"><code class="command">LogLevel</code> </a> directive.
+ </div><a id="id595275" class="indexterm"></a><div class="para">
+ The value chosen with the <span class="guilabel"><strong>Reverse DNS Lookup</strong></span> menu defines the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#hostnamelookups"><code class="command">HostnameLookups</code> </a> directive. Choosing <span class="guilabel"><strong>No Reverse Lookup</strong></span> sets the value to off. Choosing <span class="guilabel"><strong>Reverse Lookup</strong></span> sets the value to on. Choosing <span class="guilabel"><strong>Double Reverse Lookup</strong></span> sets the value to double.
+ </div><div class="para">
+ If you choose <span class="guilabel"><strong>Reverse Lookup</strong></span>, your server automatically resolves the IP address for each connection which requests a document from your Web server. Resolving the IP address means that your server makes one or more connections to the DNS in order to find out the hostname that corresponds to a particular IP address.
+ </div><div class="para">
+ If you choose <span class="guilabel"><strong>Double Reverse Lookup</strong></span>, your server performs a double-reverse DNS. In other words, after a reverse lookup is performed, a forward lookup is performed on the result. At least one of the IP addresses in the forward lookup must match the address from the first reverse lookup.
+ </div><div class="para">
+ Generally, you should leave this option set to <span class="guilabel"><strong>No Reverse Lookup</strong></span>, because the DNS requests add a load to your server and may slow it down. If your server is busy, the effects of trying to perform these reverse lookups or double reverse lookups may be quite noticeable.
+ </div><div class="para">
+ Reverse lookups and double reverse lookups are also an issue for the Internet as a whole. Each individual connection made to look up each hostname adds up. Therefore, for your own Web server's benefit, as well as for the Internet's benefit, you should leave this option set to <span class="guilabel"><strong>No Reverse Lookup</strong></span>.
+ </div></div><div class="section" title="11.4.2.4. Environment Variables" id="s3-httpd-environment-variables"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-httpd-environment-variables">11.4.2.4. Environment Variables</h4></div></div></div><div class="para">
+ Use the <span class="guilabel"><strong>Environment</strong></span> tab to configure options for specific variables to set, pass, or unset for CGI scripts.
+ </div><div class="para">
+ Sometimes it is necessary to modify environment variables for CGI scripts or server-side include (SSI) pages. The Apache HTTP Server can use the <code class="command">mod_env</code> module to configure the environment variables which are passed to CGI scripts and SSI pages. Use the <span class="guilabel"><strong>Environment Variables</strong></span> page to configure the directives for this module.
+ </div><div class="para">
+ Use the <span class="guilabel"><strong>Set for CGI Scripts</strong></span> section to set an environment variable that is passed to CGI scripts and SSI pages. For example, to set the environment variable <code class="filename">MAXNUM</code> to <code class="filename">50</code>, click the <span class="guibutton"><strong>Add</strong></span> button inside the <span class="guilabel"><strong>Set for CGI Script</strong></span> section, as shown in <a class="xref" href="s2-httpd-default-settings.html#httpd-environment-variables-screen" title="Figure 11.8. Environment Variables">Figure 11.8, “Environment Variables”</a>, and type <strong class="userinput"><code>MAXNUM</code></strong> in the <span class="guilabel"><strong>Environment Variable</strong></span> text field and <strong class="userinput"><code>50</code></strong> in the <span class="guilabel"><strong>Value to set</strong></span> text field. Click <span class="guibutton"><strong>OK</strong></span> to add it to the
list. The <span class="guilabel"><strong>Set for CGI Scripts</strong></span> section configures the <a href="http://httpd.apache.org/docs/2.2/mod/mod_env.html#setenv"><code class="command">SetEnv</code> </a> directive.
+ </div><div class="para">
+ Use the <span class="guilabel"><strong>Pass to CGI Scripts</strong></span> section to pass the value of an environment variable when the server is first started to CGI scripts. To see this environment variable, type the command <code class="command">env</code> at a shell prompt. Click the <span class="guibutton"><strong>Add</strong></span> button inside the <span class="guilabel"><strong>Pass to CGI Scripts</strong></span> section and enter the name of the environment variable in the resulting dialog box. Click <span class="guibutton"><strong>OK</strong></span> to add it to the list. The <span class="guilabel"><strong>Pass to CGI Scripts</strong></span> section configures the <a href="http://httpd.apache.org/docs/2.2/mod/mod_env.html#passenv"><code class="command">PassEnv</code> </a> directive.
+ </div><div class="figure" title="Figure 11.8. Environment Variables" id="httpd-environment-variables-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-environment.png" width="444" alt="Environment Variables" /><div class="longdesc"><div class="para">
+ Environment Variables
+ </div></div></div></div><h6>Figure 11.8. Environment Variables</h6></div><br class="figure-break" /><div class="para">
+ To remove an environment variable so that the value is not passed to CGI scripts and SSI pages, use the <span class="guilabel"><strong>Unset for CGI Scripts</strong></span> section. Click <span class="guibutton"><strong>Add</strong></span> in the <span class="guilabel"><strong>Unset for CGI Scripts</strong></span> section, and enter the name of the environment variable to unset. Click <span class="guibutton"><strong>OK</strong></span> to add it to the list. This corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/mod_env.html#unsetenv"><code class="command">UnsetEnv</code> </a> directive.
+ </div><div class="para">
+ To edit any of these environment values, select it from the list and click the corresponding <span class="guibutton"><strong>Edit</strong></span> button. To delete any entry from the list, select it and click the corresponding <span class="guibutton"><strong>Delete</strong></span> button.
+ </div><div class="para">
+ To learn more about environment variables in the Apache HTTP Server, refer to the following: <a href="http://httpd.apache.org/docs/2.2/env.html">http://httpd.apache.org/docs/2.2/env.html</a>
+ </div></div><div class="section" title="11.4.2.5. Directories" id="s3-httpd-directories"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-httpd-directories">11.4.2.5. Directories</h4></div></div></div><div class="para">
+ Use the <span class="guilabel"><strong>Directories</strong></span> page in the <span class="guilabel"><strong>Performance</strong></span> tab to configure options for specific directories. This corresponds to the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#directory"><code class="command"><Directory></code> </a> directive.
+ </div><div class="figure" title="Figure 11.9. Directories" id="httpd-directories-screen"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-directories.png" width="444" alt="Directories" /><div class="longdesc"><div class="para">
+ Directories
+ </div></div></div></div><h6>Figure 11.9. Directories</h6></div><br class="figure-break" /><div class="para">
+ Click the <span class="guibutton"><strong>Edit</strong></span> button in the top right-hand corner to configure the <span class="guilabel"><strong>Default Directory Options</strong></span> for all directories that are not specified in the <span class="guilabel"><strong>Directory</strong></span> list below it. The options that you choose are listed as the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#options"><code class="command">Options</code> </a> directive within the <a href="http://httpd.apache.org/docs/2.2/mod/core.html#directory"> <code class="command"><Directory></code> </a> directive. You can configure the following options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>ExecCGI</strong></span> — Allow execution of CGI scripts. CGI scripts are not executed if this option is not chosen.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>FollowSymLinks</strong></span> — Allow symbolic links to be followed.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Includes</strong></span> — Allow server-side includes.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>IncludesNOEXEC</strong></span> — Allow server-side includes, but disable the <code class="command">#exec</code> and <code class="command">#include</code> commands in CGI scripts.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Indexes</strong></span> — Display a formatted list of the directory's contents, if no <code class="command">DirectoryIndex</code> (such as <code class="filename">index.html</code>) exists in the requested directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Multiview</strong></span> — Support content-negotiated multiviews; this option is disabled by default.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>SymLinksIfOwnerMatch</strong></span> — Only follow symbolic links if the target file or directory has the same owner as the link.
+ </div></li></ul></div><div class="para">
+ To specify options for specific directories, click the <span class="guibutton"><strong>Add</strong></span> button beside the <span class="guilabel"><strong>Directory</strong></span> list box. A window as shown in <a class="xref" href="s2-httpd-default-settings.html#httpd-directories-add" title="Figure 11.10. Directory Settings">Figure 11.10, “Directory Settings”</a> appears. Enter the directory to configure in the <span class="guilabel"><strong>Directory</strong></span> text field at the bottom of the window. Select the options in the right-hand list and configure the <a href="http://httpd.apache.org/docs-2.0/mod/mod_access.html#order"><code class="command">Order</code> </a> directive with the left-hand side options. The <code class="command">Order</code> directive controls the order in which allow and deny directives are evaluated. In the <span class="guilabel"><strong>Allow hosts from</strong></span> and <span class="guilabel"><strong>Deny hosts from</strong></
span> text field, you can specify one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Allow all hosts — Type <strong class="userinput"><code>all</code></strong> to allow access to all hosts.
+ </div></li><li class="listitem"><div class="para">
+ Partial domain name — Allow all hosts whose names match or end with the specified string.
+ </div></li><li class="listitem"><div class="para">
+ Full IP address — Allow access to a specific IP address.
+ </div></li><li class="listitem"><div class="para">
+ A subnet — Such as <strong class="userinput"><code>192.168.1.0/255.255.255.0</code></strong>
+ </div></li><li class="listitem"><div class="para">
+ A network CIDR specification — such as <strong class="userinput"><code>10.3.0.0/16</code></strong>
+ </div></li></ul></div><div class="figure" title="Figure 11.10. Directory Settings" id="httpd-directories-add"><div class="figure-contents"><div class="mediaobject"><img src="images/httpd-directories-add.png" width="444" alt="Directory Settings" /><div class="longdesc"><div class="para">
+ Directory Settings
+ </div></div></div></div><h6>Figure 11.10. Directory Settings</h6></div><br class="figure-break" /><div class="para">
+ If you check the <span class="guilabel"><strong>Let .htaccess files override directory options</strong></span>, the configuration directives in the <code class="filename">.htaccess</code> file take precedence.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-config-ui.html"><strong>Prev</strong>11.4. Apache HTTP Server 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-apache-config.html"><strong>Next</strong>11.5. Configuration Directives in httpd.conf </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-kernel-boot-loader-iseries.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-kernel-boot-loader-iseries.html
new file mode 100644
index 0000000..94edeb9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-kernel-boot-loader-iseries.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>29.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-kernel-boot-loader.html" title="29.6. Verifying the Boot Loader" /><link rel="prev" href="s1-kernel-boot-loader.html" title="29.6. Verifying the Boot Loader" /><link rel="next" href="s2-kernel-boot-loader-pseries.html" title="29.6.3. Configuring the YABOOT Boot Loader" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This i
s an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="29.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">29.6.2. Configuring the <span class="trademark">OS/400</span>® Boot Loader</h3></div></div></div><div class="para">
+ The <code class="filename">/boot/vmlinitrd-<em class="replaceable"><code><kernel-version></code></em> </code> file
+ <a id="id857403" class="indexterm"></a>
+ <a id="id857415" class="indexterm"></a>
+ 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>29.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>29.6.3. Configuring the YABOOT Boot Loader</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-kernel-boot-loader-pseries.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-kernel-boot-loader-pseries.html
new file mode 100644
index 0000000..d3c624c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-kernel-boot-loader-pseries.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>29.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-kernel-boot-loader.html" title="29.6. Verifying the Boot Loader" /><link rel="prev" href="s2-kernel-boot-loader-iseries.html" title="29.6.2. Configuring the OS/400® Boot Loader" /><link rel="next" href="ch-General_Parameters_and_Modules.html" title="Chapter 30. General Parameters and Modules" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../.
./../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-General_Parameters_and_Modules.html"><strong>Next</strong></a></li></ul><div class="section" title="29.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">29.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>29.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-General_Parameters_and_Modules.html"><strong>Next</strong>Chapter 30. General Parameters and Modules</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-keys-checking.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-keys-checking.html
new file mode 100644
index 0000000..c857457
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-keys-checking.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to
view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="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_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-additional-resources-web.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-additional-resources-web.html
new file mode 100644
index 0000000..1a60997
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-additional-resources-web.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.9.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ldap-additional-resources.html" title="14.9. Additional Resources" /><link rel="prev" href="s1-ldap-additional-resources.html" title="14.9. Additional Resources" /><link rel="next" href="s2-ldap-related-books.html" title="14.9.3. Related Books" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser o
r enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-additional-resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ldap-related-books.html"><strong>Next</strong></a></li></ul><div class="section" title="14.9.2. Useful Websites" id="s2-ldap-additional-resources-web"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-additional-resources-web">14.9.2. Useful Websites</h3></div></div></div><a id="id726297" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.openldap.org">http://www.openldap.org/</a> — Home of the OpenLDAP Project. This website contains a wealth of information about configuring OpenLDAP as well as a future roadmap and version changes.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.padl.com">http://www.padl.com/</a> — Developers of <code class="filename">nss_ldap</code> and <code class="filename">pam_ldap</code>, among other useful LDAP tools.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.kingsmountain.com/ldapRoadmap.shtml">http://www.kingsmountain.com/ldapRoadmap.shtml</a> — Jeff Hodges' LDAP Road Map contains links to several useful FAQs and emerging news concerning the LDAP protocol.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.ldapman.org/articles/">http://www.ldapman.org/articles/</a> — Articles that offer a good introduction to LDAP, including methods to design a directory tree and customizing directory structures.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ldap-additional-resources.html"><strong>Prev</strong>14.9. 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-ldap-related-books.html"><strong>Next</strong>14.9.3. Related Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-applications.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-applications.html
new file mode 100644
index 0000000..f0ec28f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-applications.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.3. LDAP Client Applications</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ldap-daemonsutils.html" title="14.3. OpenLDAP Daemons and Utilities" /><link rel="prev" href="s2-ldap-other-apps.html" title="14.3.2. PHP4, LDAP, and the Apache HTTP Server" /><link rel="next" href="s1-ldap-files.html" title="14.4. OpenLDAP Configuration Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-other-apps.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ldap-files.html"><strong>Next</strong></a></li></ul><div class="section" title="14.3.3. LDAP Client Applications" id="s2-ldap-applications"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-applications">14.3.3. LDAP Client Applications</h3></div></div></div><a id="id662866" class="indexterm"></a><div class="para">
+ There are graphical LDAP clients available which support creating and modifying directories, but they are <span class="emphasis"><em>not</em></span> included with Fedora.
+ </div><div class="para">
+ Other LDAP clients access directories as read-only, using them to reference, but not alter, organization-wide information. Some examples of such applications are Sendmail, <span class="application"><strong>Mozilla</strong></span>, <span class="application"><strong>Ekiga</strong></span>, and <span class="application"><strong>Evolution</strong></span>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ldap-other-apps.html"><strong>Prev</strong>14.3.2. PHP4, LDAP, and 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="s1-ldap-files.html"><strong>Next</strong>14.4. OpenLDAP Configuration Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-migrate.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-migrate.html
new file mode 100644
index 0000000..4df29e7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-migrate.html
@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.7.2. Migrating Old Authentication Information to LDAP 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ldap-pam.html" title="14.7. Configuring a System to Authenticate Using OpenLDAP" /><link rel="prev" href="s1-ldap-pam.html" title="14.7. Configuring a System to Authenticate Using OpenLDAP" /><link rel="next" href="s1-ldap-migrate.html" title="14.8. Migrating Directories from Earlier Releases" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" c
lass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-pam.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ldap-migrate.html"><strong>Next</strong></a></li></ul><div class="section" title="14.7.2. Migrating Old Authentication Information to LDAP Format" id="s2-ldap-migrate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-migrate">14.7.2. Migrating Old Authentication Information to LDAP Format</h3></div></div></div><div class="para">
+ The <code class="filename">/usr/share/openldap/migration/</code> directory contains a set of shell and Perl scripts for migrating authentication information into an LDAP format.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ Perl must be installed on the system to use these scripts.
+ </div></div><div class="para">
+ First, modify the <code class="filename">migrate_common.ph</code> file so that it reflects the correct domain. The default DNS domain should be changed from its default value to something like:
+ </div><pre class="screen">
+<code class="command">$DEFAULT_MAIL_DOMAIN = "<em class="replaceable"><code>example</code></em>";</code>
+</pre><div class="para">
+ The default base should also be changed to something like:
+ </div><pre class="screen">
+<code class="command">$DEFAULT_BASE = "dc=<em class="replaceable"><code>example</code></em>,dc=<em class="replaceable"><code>com</code></em>";</code>
+</pre><div class="para">
+ The job of migrating a user database into a format that is LDAP readable falls to a group of migration scripts installed in the same directory. Using <a class="xref" href="s2-ldap-migrate.html#tb-ldap-migratescripts" title="Table 14.1. LDAP Migration Scripts">Table 14.1, “LDAP Migration Scripts”</a>, decide which script to run to migrate the user database.
+ </div><div class="para">
+ Run the appropriate script based on the existing name service.
+ </div><div class="para">
+ The <code class="filename">README</code> and the <code class="filename">migration-tools.txt</code> files in the <code class="filename">/usr/share/openldap/migration/</code> directory provide more details on how to migrate the information.
+ </div><div class="table" title="Table 14.1. LDAP Migration Scripts" id="tb-ldap-migratescripts"><div class="table-contents"><table summary="LDAP Migration Scripts" border="1"><colgroup><col width="30%" /><col width="20%" /><col width="50%" /></colgroup><thead><tr><th>
+ Existing name service
+ </th><th>
+ Is LDAP running?
+ </th><th>
+ Script to Use
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc</code> flat files
+ </td><td>
+ yes
+ </td><td>
+ <code class="filename">migrate_all_online.sh</code>
+ </td></tr><tr><td>
+ <code class="filename">/etc</code> flat files
+ </td><td>
+ no
+ </td><td>
+ <code class="filename">migrate_all_offline.sh</code>
+ </td></tr><tr><td>
+ NetInfo
+ </td><td>
+ yes
+ </td><td>
+ <code class="filename">migrate_all_netinfo_online.sh</code>
+ </td></tr><tr><td>
+ NetInfo
+ </td><td>
+ no
+ </td><td>
+ <code class="filename">migrate_all_netinfo_offline.sh</code>
+ </td></tr><tr><td>
+ NIS (YP)
+ </td><td>
+ yes
+ </td><td>
+ <code class="filename">migrate_all_nis_online.sh</code>
+ </td></tr><tr><td>
+ NIS (YP)
+ </td><td>
+ no
+ </td><td>
+ <code class="filename">migrate_all_nis_offline.sh</code>
+ </td></tr></tbody></table></div><h6>Table 14.1. LDAP Migration Scripts</h6></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ldap-pam.html"><strong>Prev</strong>14.7. Configuring a System to Authenticate Using ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ldap-migrate.html"><strong>Next</strong>14.8. Migrating Directories from Earlier Releases</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-other-apps.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-other-apps.html
new file mode 100644
index 0000000..3c29863
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-other-apps.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.2. PHP4, LDAP, and 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ldap-daemonsutils.html" title="14.3. OpenLDAP Daemons and Utilities" /><link rel="prev" href="s1-ldap-daemonsutils.html" title="14.3. OpenLDAP Daemons and Utilities" /><link rel="next" href="s2-ldap-applications.html" title="14.3.3. LDAP Client Applications" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifra
me, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-daemonsutils.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ldap-applications.html"><strong>Next</strong></a></li></ul><div class="section" title="14.3.2. PHP4, LDAP, and the Apache HTTP Server" id="s2-ldap-other-apps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-other-apps">14.3.2. PHP4, LDAP, and the Apache HTTP Server</h3></div></div></div><a id="id866926" class="indexterm"></a><a id="id866940" class="indexterm"></a><div class="para">
+ Fedora includes a package containing an LDAP module for the PHP server-side scripting language.
+ </div><div class="para">
+ The <code class="filename">php-ldap</code> package adds LDAP support to the PHP4 HTML-embedded scripting language via the <code class="filename">/usr/lib/php4/ldap.so</code> module. This module allows PHP4 scripts to access information stored in an LDAP directory.
+ </div><div class="para">
+ Fedora ships with the <code class="filename">mod_authz_ldap</code> module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. The <code class="filename">mod_ssl</code> module is required when using the <code class="filename">mod_authz_ldap</code> module.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ The <code class="filename">mod_authz_ldap</code> module does not authenticate a user to an LDAP directory using an encrypted password hash. This functionality is provided by the experimental <code class="filename">mod_auth_ldap</code> module, which is not included with Fedora. Refer to the Apache Software Foundation website online at <a href="http://www.apache.org/">http://www.apache.org/</a> for details on the status of this module.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ldap-daemonsutils.html"><strong>Prev</strong>14.3. OpenLDAP Daemons and Utilities</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-ldap-applications.html"><strong>Next</strong>14.3.3. LDAP Client Applications</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-related-books.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-related-books.html
new file mode 100644
index 0000000..eedde80
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ldap-related-books.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.9.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ldap-additional-resources.html" title="14.9. Additional Resources" /><link rel="prev" href="s2-ldap-additional-resources-web.html" title="14.9.2. Useful Websites" /><link rel="next" href="ch-Authentication_Configuration.html" title="Chapter 15. Authentication Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to v
iew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-ldap-additional-resources-web.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="14.9.3. Related Books" id="s2-ldap-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ldap-related-books">14.9.3. Related Books</h3></div></div></div><a id="id726409" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">OpenLDAP by Example</em> by John Terpstra and Benjamin Coles; Prentice Hall.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Implementing LDAP</em> by Mark Wilcox; Wrox Press, Inc.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Understanding and Deploying LDAP Directory Services</em> by Tim Howes et al.; Macmillan Technical Publishing.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ldap-additional-resources-web.html"><strong>Prev</strong>14.9.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-Authentication_Configuration.html"><strong>Next</strong>Chapter 15. Authentication Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-modules-bonding.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-modules-bonding.html
new file mode 100644
index 0000000..ce70d90
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-modules-bonding.html
@@ -0,0 +1,193 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>30.5.2. The Channel Bonding 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-modules-ethernet.html" title="30.5. Ethernet Parameters" /><link rel="prev" href="s1-modules-ethernet.html" title="30.5. Ethernet Parameters" /><link rel="next" href="s1-kernel-modules-additional-resources.html" title="30.6. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade y
our browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-modules-ethernet.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="30.5.2. The Channel Bonding Module" id="s2-modules-bonding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-modules-bonding">30.5.2. The Channel Bonding Module</h3></div></div></div><a id="id573296" class="indexterm"></a><a id="id573308" class="indexterm"></a><div class="para">
+ Fedora allows administrators to bind NICs
+ <a id="id573323" class="indexterm"></a>
+ together into a single channel using the <code class="filename">bonding</code> kernel module
+ <a id="id573338" class="indexterm"></a>
+ and a special network interface, called a <em class="firstterm">channel bonding interface</em> <a id="id573354" class="indexterm"></a>
+ <a id="id972212" class="indexterm"></a>
+ . Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
+ </div><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="s2-modules-bonding.html#s3-modules-bonding-directives" title="30.5.2.1. Bonding Module Directives">Section 30.5.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="30.5.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">30.5.2.1. Bonding Module Directives</h4></div></div></div><a id="id972334" class="indexterm"></a><a id="id972346" 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
+ <a id="id972380" class="indexterm"></a>
+ <a id="id972392" class="indexterm"></a>
+ 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> <a id="id972422" class="indexterm"></a>
+ <a id="id972434" class="indexterm"></a>
+ 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 <code class="filename">/sys</code>.
+ </div><div class="para">
+ All bonded interfaces can be configured dynamically by interacting with and manipulating files under the <code class="filename">/sys/class/net/</code> directory. After you have created a channel bonding interface file such as <code class="filename">ifcfg-bond0</code> and inserted <em class="parameter"><code>SLAVE=bond0</code></em> directives in the bonded interfaces 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 then proceed to testing and determining the best parameters for your bonded 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">~]# ifconfig bond0 up</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">~]# ifconfig
+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">~]# cat /sys/class/net/bonding_masters
+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">~]# ifconfig bond0 down</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">~]# echo 1000 > /sys/class/net/bond0/bonding/miimon</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">~]# echo 6 > /sys/class/net/bond0/bonding/mode</pre><div class="para">
+ ...or, using the name of the mode:
+ </div><pre class="screen">~]# echo balance-alb > /sys/class/net/bond0/bonding/mode</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 bonded 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 bonded 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 is a list of available channel bonding module parameters for the <code class="filename">bonding</code> module. For more in-depth information on configuring channel bonding and the exhaustive list of bonding module parameters, install the <span class="package">kernel-doc</span> package (refer to <a class="xref" href="s1-kernel-modules-additional-resources.html" title="30.6. Additional Resources">Section 30.6, “Additional Resources”</a>) and then locate and reference the <code class="filename">bonding.txt</code> file:
+ </div><pre class="screen">~]# yum -y install kernel-doc
+~]# gedit $(rpm -ql kernel-doc |grep -i bonding.txt) &</pre><div class="variablelist" title="Bonding Interface Parameters"><h6>Bonding Interface Parameters</h6><dl><dt><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"><h2>Important</h2><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 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><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><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><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><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><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><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">~]# ethtool <em class="replaceable"><code><interface_name></code></em> | grep "Link detected:"</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"><h2>Important</h2><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></dd><dt><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><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 option affects only the active-backup mode.
+ </div></dd><dt><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><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 option 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><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><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"><h2>Tip</h2><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></dd><dt><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 option 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="s1-modules-ethernet.html"><strong>Prev</strong>30.5. Ethernet 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="s1-kernel-modules-additional-resources.html"><strong>Next</strong>30.6. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-alias.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-alias.html
new file mode 100644
index 0000000..d52be78
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-alias.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an i
frame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id612321" class="indexterm"></a><a id="id612338" 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"><h2>Caution</h2><div class="para">
+ Alias interfaces do not support DHCP.
+ </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_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html
new file mode 100644
index 0000000..2abda27
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-chan.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This i
s an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>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="id838661" class="indexterm"></a><a id="id838679" 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"><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><h6>Example 4.1. Sample ifcfg-bond0 interface configuration file</h6></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"><h2>Important: put all bonding module parameters in ifcfg-bondN files</h2><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="s2-modules-bonding.html" title="30.5.2. The Channel Bonding Module">Section 30.5.2, “The Channel Bonding Module”</a>.
+ </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_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-other.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-other.html
new file mode 100644
index 0000000..4204314
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-other.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view i
t upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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>Prev</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><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"><h2>Warning</h2><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></dd><dt><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><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_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-ppp0.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-ppp0.html
new file mode 100644
index 0000000..c13fb77
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-networkscripts-interfaces-ppp0.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, t
o view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>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="id857877" 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><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><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><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><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><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><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><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><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><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><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><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><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><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_Draft_Documentation/0.1/html/Deployment_Guide/s2-openssh-useful-websites.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-openssh-useful-websites.html
new file mode 100644
index 0000000..3740836
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-openssh-useful-websites.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-openssh-additional-resources.html" title="8.5. Additional Resources" /><link rel="prev" href="s1-openssh-additional-resources.html" title="8.5. Additional Resources" /><link rel="next" href="ch-Samba.html" title="Chapter 9. Samba" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifram
e display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Samba.html"><strong>Next</strong></a></li></ul><div class="section" title="8.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">8.5.2. Useful Websites</h3></div></div></div><div class="variablelist"><dl><dt><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><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><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>8.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-Samba.html"><strong>Next</strong>Chapter 9. Samba</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-events.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-events.html
new file mode 100644
index 0000000..b44b412
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-events.html
@@ -0,0 +1,172 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>27.2.2. Setting Events to Monitor</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-oprofile-configuring.html" title="27.2. Configuring OProfile" /><link rel="prev" href="s1-oprofile-configuring.html" title="27.2. Configuring OProfile" /><link rel="next" href="s2-oprofile-starting-separate.html" title="27.2.3. Separating Kernel and User-space Profiles" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifram
e, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-configuring.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-starting-separate.html"><strong>Next</strong></a></li></ul><div class="section" title="27.2.2. Setting Events to Monitor" id="s2-oprofile-events"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-events">27.2.2. Setting Events to Monitor</h3></div></div></div><a id="id857623" class="indexterm"></a><div class="para">
+ Most processors contain <em class="firstterm">counters</em>, which are used by OProfile to monitor specific events. As shown in <a class="xref" href="s2-oprofile-events.html#tb-oprofile-processors" title="Table 27.2. OProfile Processors and Counters">Table 27.2, “OProfile Processors and Counters”</a>, the number of counters available depends on the processor.
+ </div><div class="table" title="Table 27.2. OProfile Processors and Counters" id="tb-oprofile-processors"><div class="table-contents"><table summary="OProfile Processors and Counters" border="1"><colgroup><col width="43%" /><col width="29%" /><col width="29%" /></colgroup><thead><tr><th>
+ Processor
+ </th><th>
+ <code class="command">cpu_type</code>
+ </th><th>
+ Number of Counters
+ </th></tr></thead><tbody><tr><td>
+ Pentium Pro
+ </td><td>
+ i386/ppro
+ </td><td>
+ 2
+ </td></tr><tr><td>
+ Pentium II
+ </td><td>
+ i386/pii
+ </td><td>
+ 2
+ </td></tr><tr><td>
+ Pentium III
+ </td><td>
+ i386/piii
+ </td><td>
+ 2
+ </td></tr><tr><td>
+ Pentium 4 (non-hyper-threaded)
+ </td><td>
+ i386/p4
+ </td><td>
+ 8
+ </td></tr><tr><td>
+ Pentium 4 (hyper-threaded)
+ </td><td>
+ i386/p4-ht
+ </td><td>
+ 4
+ </td></tr><tr><td>
+ Athlon
+ </td><td>
+ i386/athlon
+ </td><td>
+ 4
+ </td></tr><tr><td>
+ AMD64
+ </td><td>
+ x86-64/hammer
+ </td><td>
+ 4
+ </td></tr><tr><td>
+ TIMER_INT
+ </td><td>
+ timer
+ </td><td>
+ 1
+ </td></tr><tr><td>
+ IBM eServer iSeries and pSeries
+ </td><td>
+ timer
+ </td><td>
+ 1
+ </td></tr><tr><td>
+ </td><td>
+ ppc64/power4
+ </td><td>
+ 8
+ </td></tr><tr><td>
+ </td><td>
+ ppc64/power5
+ </td><td>
+ 6
+ </td></tr><tr><td>
+ </td><td>
+ ppc64/970
+ </td><td>
+ 8
+ </td></tr><tr><td>
+ IBM eServer S/390 and S/390x
+ </td><td>
+ timer
+ </td><td>
+ 1
+ </td></tr><tr><td>
+ IBM eServer zSeries
+ </td><td>
+ timer
+ </td><td>
+ 1
+ </td></tr></tbody></table></div><h6>Table 27.2. OProfile Processors and Counters</h6></div><br class="table-break" /><div class="para">
+ Use <a class="xref" href="s2-oprofile-events.html#tb-oprofile-processors" title="Table 27.2. OProfile Processors and Counters">Table 27.2, “OProfile Processors and Counters”</a> to verify that the correct processor type was detected and to determine the number of events that can be monitored simultaneously. <code class="computeroutput">timer</code> is used as the processor type if the processor does not have supported performance monitoring hardware.
+ </div><div class="para">
+ If <code class="computeroutput">timer</code> is used, events cannot be set for any processor because the hardware does not have support for hardware performance counters. Instead, the timer interrupt is used for profiling.
+ </div><div class="para">
+ If <code class="computeroutput">timer</code> is not used as the processor type, the events monitored can be changed, and counter 0 for the processor is set to a time-based event by default. If more than one counter exists on the processor, the counters other than counter 0 are not set to an event by default. The default events monitored are shown in <a class="xref" href="s2-oprofile-events.html#tb-oprofile-default-events" title="Table 27.3. Default Events">Table 27.3, “Default Events”</a>.
+ </div><div class="table" title="Table 27.3. Default Events" id="tb-oprofile-default-events"><div class="table-contents"><table summary="Default Events" border="1"><colgroup><col width="25%" /><col width="33%" /><col width="42%" /></colgroup><thead><tr><th>
+ Processor
+ </th><th>
+ Default Event for Counter
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ Pentium Pro, Pentium II, Pentium III, Athlon, AMD64
+ </td><td>
+ CPU_CLK_UNHALTED
+ </td><td>
+ The processor's clock is not halted
+ </td></tr><tr><td>
+ Pentium 4 (HT and non-HT)
+ </td><td>
+ GLOBAL_POWER_EVENTS
+ </td><td>
+ The time during which the processor is not stopped
+ </td></tr><tr><td>
+ TIMER_INT
+ </td><td>
+ (none)
+ </td><td>
+ Sample for each timer interrupt
+ </td></tr><tr><td>
+ ppc64/power4
+ </td><td>
+ CYCLES
+ </td><td>
+ Processor Cycles
+ </td></tr><tr><td>
+ ppc64/power5
+ </td><td>
+ CYCLES
+ </td><td>
+ Processor Cycles
+ </td></tr><tr><td>
+ ppc64/970
+ </td><td>
+ CYCLES
+ </td><td>
+ Processor Cycles
+ </td></tr></tbody></table></div><h6>Table 27.3. Default Events</h6></div><br class="table-break" /><div class="para">
+ The number of events that can be monitored at one time is determined by the number of counters for the processor. However, it is not a one-to-one correlation; on some processors, certain events must be mapped to specific counters. To determine the number of counters available, execute the following command:
+ </div><pre class="screen">
+<code class="command">ls -d /dev/oprofile/[0-9]*</code>
+</pre><div class="para">
+ The events available vary depending on the processor type. To determine the events available for profiling, execute the following command as root (the list is specific to the system's processor type):
+ </div><a id="id951906" class="indexterm"></a><a id="id951923" class="indexterm"></a><pre class="screen">
+<code class="command">ophelp</code>
+</pre><div class="para">
+ The events for each counter can be configured via the command line or with a graphical interface. For more information on the graphical interface, refer to <a class="xref" href="s1-oprofile-gui.html" title="27.8. Graphical Interface">Section 27.8, “Graphical Interface”</a>. If the counter cannot be set to a specific event, an error message is displayed.
+ </div><div class="para">
+ To set the event for each configurable counter via the command line, use <code class="command">opcontrol</code>:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em> </code>
+</pre><div class="para">
+ Replace <em class="replaceable"><code><event-name></code></em> with the exact name of the event from <code class="command">ophelp</code>, and replace <em class="replaceable"><code><sample-rate></code></em> with the number of events between samples.
+ </div><div class="section" title="27.2.2.1. Sampling Rate" id="s3-oprofile-events-sampling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-oprofile-events-sampling">27.2.2.1. Sampling Rate</h4></div></div></div><a id="id952001" class="indexterm"></a><div class="para">
+ By default, a time-based event set is selected. It creates a sample every 100,000 clock cycles per processor. If the timer interrupt is used, the timer is set to whatever the jiffy rate is and is not user-settable. If the <code class="computeroutput">cpu_type</code> is not <code class="computeroutput">timer</code>, each event can have a <em class="firstterm">sampling rate</em> set for it. The sampling rate is the number of events between each sample snapshot.
+ </div><div class="para">
+ When setting the event for the counter, a sample rate can also be specified:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em> </code>
+</pre><div class="para">
+ Replace <em class="replaceable"><code><sample-rate></code></em> with the number of events to wait before sampling again. The smaller the count, the more frequent the samples. For events that do not happen frequently, a lower count may be needed to capture the event instances.
+ </div><div class="warning"><h2>Caution</h2><div class="para">
+ Be extremely careful when setting sampling rates. Sampling too frequently can overload the system, causing the system to appear as if it is frozen or causing the system to actually freeze.
+ </div></div></div><div class="section" title="27.2.2.2. Unit Masks" id="s3-oprofile-events-unit-masks"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-oprofile-events-unit-masks">27.2.2.2. Unit Masks</h4></div></div></div><a id="id847765" class="indexterm"></a><div class="para">
+ Some user performance monitoring events may also require unit masks to further define the event.
+ </div><div class="para">
+ Unit masks for each event are listed with the <code class="command">ophelp</code> command. The values for each unit mask are listed in hexadecimal format. To specify more than one unit mask, the hexadecimal values must be combined using a bitwise <em class="firstterm">or</em> operation.
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em>:<em class="replaceable"><code><unit-mask></code></em> </code>
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-configuring.html"><strong>Prev</strong>27.2. Configuring OProfile</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-starting-separate.html"><strong>Next</strong>27.2.3. Separating Kernel and User-space Profiles</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-module-output.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-module-output.html
new file mode 100644
index 0000000..bbbf8f9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-module-output.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>27.5.3. Getting more detailed output on the 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="27.5. Analyzing the Data" /><link rel="prev" href="s2-oprofile-reading-opreport-single.html" title="27.5.2. Using opreport on a Single Executable" /><link rel="next" href="s2-oprofile-reading-opannotate.html" title="27.5.4. Using opannotate" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../
toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-reading-opreport-single.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-reading-opannotate.html"><strong>Next</strong></a></li></ul><div class="section" title="27.5.3. Getting more detailed output on the modules" id="s2-oprofile-module-output"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-module-output">27.5.3. Getting more detailed output on the modules</h3></div></div></div><a id="id843066" class="indexterm"></a><a id="id843085" c
lass="indexterm"></a><div class="para">
+ OProfile collects data on a system-wide basis for kernel- and user-space code running on the machine. However, once a module is loaded into the kernel, the information about the origin of the kernel module is lost. The module could have come from the initrd file on boot up, the directory with the various kernel modules, or a locally created kernel module. As a result when OProfile records sample for a module, it just lists the samples for the modules for an executable in the root directory, but this is unlikely to be the place with the actual code for the module. You will need to take some steps to make sure that analysis tools get the executable.
+ </div><div class="para">
+ For example on an AMD64 machine the sampling is set up to record "Data cache accesses" and "Data cache misses" and assuming you would like to see the data for the ext3 module:
+ </div><pre class="screen">
+<code class="command">$ opreport /ext3</code>
+CPU: AMD64 processors, speed 797.948 MHz (estimated)
+Counted DATA_CACHE_ACCESSES events (Data cache accesses) with a unit mask of 0x00 (No unit mask) count 500000
+Counted DATA_CACHE_MISSES events (Data cache misses) with a unit mask of 0x00 (No unit mask) count 500000
+DATA_CACHE_ACC...|DATA_CACHE_MIS...|
+samples| %| samples| %|
+------------------------------------
+148721 100.000 1493 100.000 ext3
+</pre><div class="para">
+ To get a more detailed view of the actions of the module, you will need to either have the module unstripped (e.g. installed from a custom build) or have the debuginfo RPM installed for the kernel.
+ </div><div class="para">
+ Find out which kernel is running, "uname -a", get the appropriate debuginfo rpm, and install on the machine.
+ </div><div class="para">
+ Then make a symbolic link so oprofile finds the code for the module in the correct place:
+ </div><pre class="screen">
+ <code class="command"># ln -s /lib/modules/`uname -r`/kernel/fs/ext3/ext3.ko /ext3</code>
+</pre><div class="para">
+ Then the detailed information can be obtained with:
+ </div><pre class="screen">
+<code class="command"># opreport image:/ext3 -l|more</code>
+warning: could not check that the binary file /ext3 has not been modified since the profile was taken. Results may be inaccurate.
+CPU: AMD64 processors, speed 797.948 MHz (estimated)
+Counted DATA_CACHE_ACCESSES events (Data cache accesses) with a unit mask of 0x00 (No unit mask) count 500000
+Counted DATA_CACHE_MISSES events (Data cache misses) with a unit mask of 0x00 (No unit mask) count 500000
+samples % samples % symbol name
+16728 11.2479 7 0.4689 ext3_group_sparse
+16454 11.0637 4 0.2679 ext3_count_free_blocks
+14583 9.8056 51 3.4159 ext3_fill_super
+8281 5.5681 129 8.6403 ext3_ioctl
+7810 5.2514 62 4.1527 ext3_write_info
+7286 4.8991 67 4.4876 ext3_ordered_writepage
+6509 4.3767 130 8.7073 ext3_new_inode
+6378 4.2886 156 10.4488 ext3_new_block
+5932 3.9887 87 5.8272 ext3_xattr_block_list
+...
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-reading-opreport-single.html"><strong>Prev</strong>27.5.2. Using opreport on a Single Executable</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-reading-opannotate.html"><strong>Next</strong>27.5.4. Using opannotate </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-reading-opannotate.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-reading-opannotate.html
new file mode 100644
index 0000000..19994d1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-reading-opannotate.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>27.5.4. Using opannotate</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="27.5. Analyzing the Data" /><link rel="prev" href="s2-oprofile-module-output.html" title="27.5.3. Getting more detailed output on the modules" /><link rel="next" href="s1-oprofile-dev-oprofile.html" title="27.6. Understanding /dev/oprofile/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe
, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-module-output.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-dev-oprofile.html"><strong>Next</strong></a></li></ul><div class="section" title="27.5.4. Using opannotate" id="s2-oprofile-reading-opannotate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-reading-opannotate">27.5.4. Using <code class="command">opannotate</code> </h3></div></div></div><a id="id843182" class="indexterm"></a><a id="id843200" class="indexterm"></a><div class="para">
+ The <code class="command">opannotate</code> tool tries to match the samples for particular instructions to the corresponding lines in the source code. The resulting files generated should have the samples for the lines at the left. It also puts in a comment at the beginning of each function listing the total samples for the function.
+ </div><div class="para">
+ For this utility to work, the executable must be compiled with GCC's <code class="option">-g</code> option. By default, Fedora packages are not compiled with this option.
+ </div><div class="para">
+ The general syntax for <code class="command">opannotate</code> is as follows:
+ </div><pre class="screen">
+<code class="command">opannotate --search-dirs <em class="replaceable"><code><src-dir></code></em> --source <em class="replaceable"><code><executable></code></em> </code>
+</pre><div class="para">
+ The directory containing the source code and the executable to be analyzed must be specified. Refer to the <code class="command">opannotate</code> man page for a list of additional command line options.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-module-output.html"><strong>Prev</strong>27.5.3. Getting more detailed output on the modul...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-dev-oprofile.html"><strong>Next</strong>27.6. Understanding /dev/oprofile/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-reading-opreport-single.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-reading-opreport-single.html
new file mode 100644
index 0000000..eef6347
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-reading-opreport-single.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>27.5.2. Using opreport on a Single Executable</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="27.5. Analyzing the Data" /><link rel="prev" href="s1-oprofile-analyzing-data.html" title="27.5. Analyzing the Data" /><link rel="next" href="s2-oprofile-module-output.html" title="27.5.3. Getting more detailed output on the modules" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-analyzing-data.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-module-output.html"><strong>Next</strong></a></li></ul><div class="section" title="27.5.2. Using opreport on a Single Executable" id="s2-oprofile-reading-opreport-single"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-reading-opreport-single">27.5.2. Using <code class="command">opreport</code> on a Single Executable</h3></div></div></div><a id="id877262" class="indexterm"></a><a id="id
877284" class="indexterm"></a><div class="para">
+ To retrieve more detailed profiled information about a specific executable, use <code class="command">opreport</code>:
+ </div><pre class="screen">
+<code class="command">opreport <em class="replaceable"><code><mode></code></em> <em class="replaceable"><code><executable></code></em> </code>
+</pre><div class="para">
+ <em class="replaceable"><code><executable></code></em> must be the full path to the executable to be analyzed. <em class="replaceable"><code><mode></code></em> must be one of the following:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="option">-l</code> </span></dt><dd><div class="para">
+ List sample data by symbols. For example, the following is part of the output from running the command <code class="command">opreport -l /lib/tls/libc-<em class="replaceable"><code><version></code></em>.so</code>:
+ </div><pre class="screen"> samples % symbol name 12 21.4286 __gconv_transform_utf8_internal 5 8.9286 _int_malloc 4 7.1429 malloc 3 5.3571 __i686.get_pc_thunk.bx 3 5.3571 _dl_mcount_wrapper_check 3 5.3571 mbrtowc 3 5.3571 memcpy 2 3.5714 _int_realloc 2 3.5714 _nl_intern_locale_data 2 3.5714 free 2 3.5714 strcmp 1 1.7857 __ctype_get_mb_cur_max 1 1.7857 __unregister_atfork 1 1.7857 __write_nocancel 1 1.7857 _dl_addr 1 1.7857 _int_free 1 1.7857 _itoa_word 1 1.7857 calc_eclosure_iter 1 1.7857 fopen@@GLIBC_2.1 1 1.7857 getpid 1 1.7857 memmove 1 1.7857 msort_with_tmp 1 1.7857 strcpy 1 1.7857 strlen 1 1.7857 vfprintf 1 1.7857 write</pre><div class="para">
+ The first column is the number of samples for the symbol, the second column is the percentage of samples for this symbol relative to the overall samples for the executable, and the third column is the symbol name.
+ </div><div class="para">
+ To sort the output from the largest number of samples to the smallest (reverse order), use <code class="option">-r</code> in conjunction with the <code class="option">-l</code> option.
+ </div></dd><dt><span class="term"> <code class="option">-i <em class="replaceable"><code><symbol-name></code></em> </code> </span></dt><dd><div class="para">
+ List sample data specific to a symbol name. For example, the following output is from the command <code class="command">opreport -l -i __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code><version></code></em>.so</code>:
+ </div><pre class="screen"> samples % symbol name 12 100.000 __gconv_transform_utf8_internal</pre><div class="para">
+ The first line is a summary for the symbol/executable combination.
+ </div><div class="para">
+ The first column is the number of samples for the memory symbol. The second column is the percentage of samples for the memory address relative to the total number of samples for the symbol. The third column is the symbol name.
+ </div></dd><dt><span class="term"> <code class="option">-d</code> </span></dt><dd><div class="para">
+ List sample data by symbols with more detail than <code class="option">-l</code>. For example, the following output is from the command <code class="command">opreport -l -d __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code><version></code></em>.so</code>:
+ </div><pre class="screen"> vma samples % symbol name 00a98640 12 100.000 __gconv_transform_utf8_internal 00a98640 1 8.3333 00a9868c 2 16.6667 00a9869a 1 8.3333 00a986c1 1 8.3333 00a98720 1 8.3333 00a98749 1 8.3333 00a98753 1 8.3333 00a98789 1 8.3333 00a98864 1 8.3333 00a98869 1 8.3333 00a98b08 1 8.3333</pre><div class="para">
+ The data is the same as the <code class="option">-l</code> option except that for each symbol, each virtual memory address used is shown. For each virtual memory address, the number of samples and percentage of samples relative to the number of samples for the symbol is displayed.
+ </div></dd><dt><span class="term"> <code class="option">-x</code> <em class="replaceable"><code><symbol-name></code></em> </span></dt><dd><div class="para">
+ Exclude the comma-separated list of symbols from the output.
+ </div></dd><dt><span class="term"> <code class="option">session</code>:<em class="replaceable"><code><name></code></em> </span></dt><dd><div class="para">
+ Specify the full path to the session or a directory relative to the <code class="filename">/var/lib/oprofile/samples/</code> directory.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-analyzing-data.html"><strong>Prev</strong>27.5. Analyzing the Data</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-module-output.html"><strong>Next</strong>27.5.3. Getting more detailed output on the modul...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-starting-separate.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-starting-separate.html
new file mode 100644
index 0000000..fd2030f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-starting-separate.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>27.2.3. Separating Kernel and User-space Profiles</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-oprofile-configuring.html" title="27.2. Configuring OProfile" /><link rel="prev" href="s2-oprofile-events.html" title="27.2.2. Setting Events to Monitor" /><link rel="next" href="s1-oprofile-starting.html" title="27.3. Starting and Stopping OProfile" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, t
o view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-events.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-starting.html"><strong>Next</strong></a></li></ul><div class="section" title="27.2.3. Separating Kernel and User-space Profiles" id="s2-oprofile-starting-separate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-starting-separate">27.2.3. Separating Kernel and User-space Profiles</h3></div></div></div><a id="id847826" class="indexterm"></a><div class="para">
+ By default, kernel mode and user mode information is gathered for each event. To configure OProfile to ignore events in kernel mode for a specific counter, execute the following command:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em>:<em class="replaceable"><code><unit-mask></code></em>:0</code>
+</pre><div class="para">
+ Execute the following command to start profiling kernel mode for the counter again:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em>:<em class="replaceable"><code><unit-mask></code></em>:1</code>
+</pre><div class="para">
+ To configure OProfile to ignore events in user mode for a specific counter, execute the following command:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em>:<em class="replaceable"><code><unit-mask></code></em>:<em class="replaceable"><code><kernel></code></em>:0</code>
+</pre><div class="para">
+ Execute the following command to start profiling user mode for the counter again:
+ </div><pre class="screen">
+<code class="command">opcontrol --event=<em class="replaceable"><code><event-name></code></em>:<em class="replaceable"><code><sample-rate></code></em>:<em class="replaceable"><code><unit-mask></code></em>:<em class="replaceable"><code><kernel></code></em>:1</code>
+</pre><div class="para">
+ When the OProfile daemon writes the profile data to sample files, it can separate the kernel and library profile data into separate sample files. To configure how the daemon writes to sample files, execute the following command as root:
+ </div><pre class="screen">
+<code class="command">opcontrol --separate=<em class="replaceable"><code><choice></code></em> </code>
+</pre><div class="para">
+ <em class="replaceable"><code><choice></code></em> can be one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">none</code> — do not separate the profiles (default)
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">library</code> — generate per-application profiles for libraries
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">kernel</code> — generate per-application profiles for the kernel and kernel modules
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">all</code> — generate per-application profiles for libraries and per-application profiles for the kernel and kernel modules
+ </div></li></ul></div><div class="para">
+ If <code class="option">--separate=library</code> is used, the sample file name includes the name of the executable as well as the name of the library.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ These configuration changes will take effect when <code class="command">oprofile</code> is restarted.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-events.html"><strong>Prev</strong>27.2.2. Setting Events to Monitor</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-oprofile-starting.html"><strong>Next</strong>27.3. Starting and Stopping OProfile</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-useful-websites.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-useful-websites.html
new file mode 100644
index 0000000..9f8f76a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-oprofile-useful-websites.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>27.9.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-oprofile-additional-resources.html" title="27.9. Additional Resources" /><link rel="prev" href="s1-oprofile-additional-resources.html" title="27.9. Additional Resources" /><link rel="next" href="ch-abrt.html" title="Chapter 28. ABRT" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable i
frame display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-oprofile-additional-resources.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="27.9.2. Useful Websites" id="s2-oprofile-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-oprofile-useful-websites">27.9.2. Useful Websites</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://oprofile.sourceforge.net/">http://oprofile.sourceforge.net/</a> — Contains the latest documentation, mailing lists, IRC channels, and more.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-additional-resources.html"><strong>Prev</strong>27.9. 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-abrt.html"><strong>Next</strong>Chapter 28. ABRT</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-printing-useful-websites.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-printing-useful-websites.html
new file mode 100644
index 0000000..3a94a79
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-printing-useful-websites.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.9.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-printing-additional-resources.html" title="23.9. Additional Resources" /><link rel="prev" href="s1-printing-additional-resources.html" title="23.9. Additional Resources" /><link rel="next" href="ch-Automated_Tasks.html" title="Chapter 24. Automated Tasks" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade yo
ur browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-printing-additional-resources.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="23.9.2. Useful Websites" id="s2-printing-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-printing-useful-websites">23.9.2. Useful Websites</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.linuxprinting.org">http://www.linuxprinting.org</a> — <em class="citetitle">GNU/Linux Printing</em> contains a large amount of information about printing in Linux.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.cups.org/">http://www.cups.org/</a> — Documentation, FAQs, and newsgroups about CUPS.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-additional-resources.html"><strong>Prev</strong>23.9. 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-Automated_Tasks.html"><strong>Next</strong>Chapter 24. Automated Tasks</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-cmdline.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-cmdline.html
new file mode 100644
index 0000000..8ab099a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-cmdline.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="next" href="s2-proc-cpuinfo.html" title="17.2.3. /proc/cpuinfo" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrad
e your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="next"><a accesskey="n" href="s2-proc-cpuinfo.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2.2. <code class="filename">/proc/cmdline</code> </h3></div></div></div><a id="id886792" 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>17.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>17.2.3. /proc/cpuinfo </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-cpuinfo.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-cpuinfo.html
new file mode 100644
index 0000000..00929ee
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-cpuinfo.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-cmdline.html" title="17.2.2. /proc/cmdline" /><link rel="next" href="s2-proc-crypto.html" title="17.2.4. /proc/crypto" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifram
e display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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" href="s2-proc-crypto.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2.3. <code class="filename">/proc/cpuinfo</code> </h3></div></div></div><a id="id817259" 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>17.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>17.2.4. /proc/crypto </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-crypto.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-crypto.html
new file mode 100644
index 0000000..14ea225
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-crypto.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-cpuinfo.html" title="17.2.3. /proc/cpuinfo" /><link rel="next" href="s2-proc-devices.html" title="17.2.5. /proc/devices" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifra
me display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.4. <code class="filename">/proc/crypto</code> </h3></div></div></div><a id="id607114" 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>17.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>17.2.5. /proc/devices </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-devices.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-devices.html
new file mode 100644
index 0000000..c8b7640
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-devices.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-crypto.html" title="17.2.4. /proc/crypto" /><link rel="next" href="s2-proc-dma.html" title="17.2.6. /proc/dma" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe displa
y.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dma.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2.5. <code class="filename">/proc/devices</code> </h3></div></div></div><a id="id921781" class="indexterm"></a><a id="id921806" class="indexterm"></a><a id="id921832" class="indexterm"></a><a id="id921845" class="indexterm"></a><a id="id921863" class="indexterm"></a><a id="id921881" 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>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>17.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>17.2.6. /proc/dma </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-bus.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-bus.html
new file mode 100644
index 0000000..0ad05e1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-bus.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="prev" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="next" href="s2-proc-dir-driver.html" title="17.3.3. /proc/driver/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifram
e display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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" href="s2-proc-dir-driver.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.3.2. <code class="filename">/proc/bus/</code> </h3></div></div></div><a id="id851565" 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>17.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-dir-driver.html"><strong>Next</strong>17.3.3. /proc/driver/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-driver.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-driver.html
new file mode 100644
index 0000000..8a41bda
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-driver.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>17.3.3. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-bus.html" title="17.3.2. /proc/bus/" /><link rel="next" href="s2-proc-dir-fs.html" title="17.3.4. /proc/fs" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></d
iv><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-dir-fs.html"><strong>Next</strong></a></li></ul><div class="section" title="17.3.3. /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">17.3.3. <code class="filename">/proc/driver/</code> </h3></div></div></div><a id="id605742" 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>version</code></em>/Documentation/rtc.txt</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-bus.html"><strong>Prev</strong>17.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-fs.html"><strong>Next</strong>17.3.4. /proc/fs </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-fs.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-fs.html
new file mode 100644
index 0000000..992be9b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-fs.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.4. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-driver.html" title="17.3.3. /proc/driver/" /><link rel="next" href="s2-proc-dir-irq.html" title="17.3.5. /proc/irq/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe
></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-dir-irq.html"><strong>Next</strong></a></li></ul><div class="section" title="17.3.4. /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">17.3.4. <code class="filename">/proc/fs</code> </h3></div></div></div><a id="id605822" 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>17.3.3. /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>17.3.5. /proc/irq/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-irq.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-irq.html
new file mode 100644
index 0000000..1a97931
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-irq.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.5. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-fs.html" title="17.3.4. /proc/fs" /><link rel="next" href="s2-proc-dir-net.html" title="17.3.6. /proc/net/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div>
<p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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.html"><strong>Next</strong></a></li></ul><div class="section" title="17.3.5. /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">17.3.5. <code class="filename">/proc/irq/</code> </h3></div></div></div><a id="id624098" 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>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>17.3.4. /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>17.3.6. /proc/net/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-net.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-net.html
new file mode 100644
index 0000000..893a037
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-net.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>17.3.6. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-irq.html" title="17.3.5. /proc/irq/" /><link rel="next" href="s2-proc-dir-scsi.html" title="17.3.7. /proc/scsi/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe><
/div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-scsi.html"><strong>Next</strong></a></li></ul><div class="section" title="17.3.6. /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">17.3.6. <code class="filename">/proc/net/</code> </h3></div></div></div><a id="id624173" 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>17.3.5. /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>17.3.7. /proc/scsi/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-scsi.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-scsi.html
new file mode 100644
index 0000000..4a55b36
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-scsi.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>17.3.7. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-net.html" title="17.3.6. /proc/net/" /><link rel="next" href="s2-proc-dir-sys.html" title="17.3.8. /proc/sys/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></
div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.3.7. /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">17.3.7. <code class="filename">/proc/scsi/</code> </h3></div></div></div><a id="id621650" 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>17.3.6. /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>17.3.8. /proc/sys/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-sys.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-sys.html
new file mode 100644
index 0000000..4ebb4f3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-sys.html
@@ -0,0 +1,326 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.8. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-scsi.html" title="17.3.7. /proc/scsi/" /><link rel="next" href="s2-proc-dir-sysvipc.html" title="17.3.9. /proc/sysvipc/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</
iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.3.8. /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">17.3.8. <code class="filename">/proc/sys/</code> </h3></div></div></div><a id="id824266" class="indexterm"></a><a id="id824288" class="indexterm"></a><a id="id824303" class="indexterm"></a><a id="id824333" class="indexterm"></a><a id="id824352" class="indexterm"></a><a id="id668011" 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"><h2>Caution</h2><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 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"><h2>Note</h2><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="17.4. Using the sysctl Command">Section 17.4, “Using the <code class="command">sysctl</code> Command”</a>.
+ </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="17.3.8.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">17.3.8.1. <code class="filename">/proc/sys/dev/</code> </h4></div></div></div><a id="id974658" 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="17.3.8.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">17.3.8.2. <code class="filename">/proc/sys/fs/</code> </h4></div></div></div><a id="id801004" 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="17.3.8.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">17.3.8.3. <code class="filename">/proc/sys/kernel/</code> </h4></div></div></div><a id="id885940" class="indexterm"></a><a id="id885970" class="indexterm"></a><a id="id885985" class="indexterm"></a><a id="id719682" class="indexterm"></a><a id="id719701" 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"><h2>Important</h2><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></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">1990</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"><h2>Caution</h2><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 class="para">
+ Refer to <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>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="17.3.8.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">17.3.8.4. <code class="filename">/proc/sys/net/</code> </h4></div></div></div><a id="id999494" class="indexterm"></a><a id="id999525" class="indexterm"></a><a id="id999539" class="indexterm"></a><a id="id999553" 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"><h2>Caution</h2><div class="para">
+ An erroneous change to these files may affect remote connectivity to the system.
+ </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>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>version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><div class="section" title="17.3.8.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">17.3.8.5. <code class="filename">/proc/sys/vm/</code> </h4></div></div></div><a id="id949337" class="indexterm"></a><a id="id949368" class="indexterm"></a><a id="id949382" 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"><h2>Tip</h2><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></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>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>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"><h2>Note</h2><div class="para">
+ This setting is only recommended for systems with swap areas larger than physical memory.
+ </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>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>17.3.7. /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>17.3.9. /proc/sysvipc/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-sysvipc.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-sysvipc.html
new file mode 100644
index 0000000..30fc9c1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dir-sysvipc.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.9. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-sys.html" title="17.3.8. /proc/sys/" /><link rel="next" href="s2-proc-tty.html" title="17.3.10. /proc/tty/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></
div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.3.9. /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">17.3.9. <code class="filename">/proc/sysvipc/</code> </h3></div></div></div><a id="id636732" 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>17.3.8. /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>17.3.10. /proc/tty/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dma.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dma.html
new file mode 100644
index 0000000..89dba35
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-dma.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-devices.html" title="17.2.5. /proc/devices" /><link rel="next" href="s2-proc-execdomains.html" title="17.2.7. /proc/execdomains" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable
iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s2-proc-execdomains.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2.6. <code class="filename">/proc/dma</code> </h3></div></div></div><a id="id787246" 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>17.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>17.2.7. /proc/execdomains </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-execdomains.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-execdomains.html
new file mode 100644
index 0000000..d7bfdf4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-execdomains.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-dma.html" title="17.2.6. /proc/dma" /><link rel="next" href="s2-proc-fb.html" title="17.2.8. /proc/fb" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</
iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.7. <code class="filename">/proc/execdomains</code> </h3></div></div></div><a id="id973450" class="indexterm"></a><a id="id973472" class="indexterm"></a><a id="id973489" 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>17.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>17.2.8. /proc/fb </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-fb.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-fb.html
new file mode 100644
index 0000000..994d8f8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-fb.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-execdomains.html" title="17.2.7. /proc/execdomains" /><link rel="next" href="s2-proc-filesystems.html" title="17.2.9. /proc/filesystems" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or
enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="next"><a accesskey="n" href="s2-proc-filesystems.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2.8. <code class="filename">/proc/fb</code> </h3></div></div></div><a id="id973538" class="indexterm"></a><a id="id893010" 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>17.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>17.2.9. /proc/filesystems </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-filesystems.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-filesystems.html
new file mode 100644
index 0000000..b127b24
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-filesystems.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-fb.html" title="17.2.8. /proc/fb" /><link rel="next" href="s2-proc-interrupts.html" title="17.2.10. /proc/interrupts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable if
rame display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.9. <code class="filename">/proc/filesystems</code> </h3></div></div></div><a id="id893055" 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>17.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>17.2.10. /proc/interrupts </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-interrupts.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-interrupts.html
new file mode 100644
index 0000000..2b762a5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-interrupts.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-filesystems.html" title="17.2.9. /proc/filesystems" /><link rel="next" href="s2-proc-iomem.html" title="17.2.11. /proc/iomem" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or e
nable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s2-proc-iomem.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2.10. <code class="filename">/proc/interrupts</code> </h3></div></div></div><a id="id893122" 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>17.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>17.2.11. /proc/iomem </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-iomem.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-iomem.html
new file mode 100644
index 0000000..93a74f9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-iomem.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-interrupts.html" title="17.2.10. /proc/interrupts" /><link rel="next" href="s2-proc-ioports.html" title="17.2.12. /proc/ioports" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or ena
ble iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s2-proc-ioports.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2.11. <code class="filename">/proc/iomem</code> </h3></div></div></div><a id="id824503" 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>17.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>17.2.12. /proc/ioports </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-ioports.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-ioports.html
new file mode 100644
index 0000000..58d6fb9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-ioports.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-iomem.html" title="17.2.11. /proc/iomem" /><link rel="next" href="s2-proc-kcore.html" title="17.2.13. /proc/kcore" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe d
isplay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.12. <code class="filename">/proc/ioports</code> </h3></div></div></div><a id="id660963" 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>17.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>17.2.13. /proc/kcore </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-kcore.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-kcore.html
new file mode 100644
index 0000000..2c4619c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-kcore.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-ioports.html" title="17.2.12. /proc/ioports" /><link rel="next" href="s2-proc-kmsg.html" title="17.2.14. /proc/kmsg" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe d
isplay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.13. <code class="filename">/proc/kcore</code> </h3></div></div></div><a id="id661023" 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"><h2>Caution</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-ioports.html"><strong>Prev</strong>17.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>17.2.14. /proc/kmsg </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-kmsg.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-kmsg.html
new file mode 100644
index 0000000..32276aa
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-kmsg.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-kcore.html" title="17.2.13. /proc/kcore" /><link rel="next" href="s2-proc-loadavg.html" title="17.2.15. /proc/loadavg" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.14. <code class="filename">/proc/kmsg</code> </h3></div></div></div><a id="id720582" 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>17.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>17.2.15. /proc/loadavg </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-loadavg.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-loadavg.html
new file mode 100644
index 0000000..08a69d1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-loadavg.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-kmsg.html" title="17.2.14. /proc/kmsg" /><link rel="next" href="s2-proc-locks.html" title="17.2.16. /proc/locks" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe dis
play.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-locks.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2.15. <code class="filename">/proc/loadavg</code> </h3></div></div></div><a id="id1017288" 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>17.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>17.2.16. /proc/locks </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-locks.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-locks.html
new file mode 100644
index 0000000..2edd0d4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-locks.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-loadavg.html" title="17.2.15. /proc/loadavg" /><link rel="next" href="s2-proc-mdstat.html" title="17.2.17. /proc/mdstat" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifra
me display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.16. <code class="filename">/proc/locks</code> </h3></div></div></div><a id="id1017356" 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>17.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>17.2.17. /proc/mdstat </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-mdstat.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-mdstat.html
new file mode 100644
index 0000000..d80872b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-mdstat.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-locks.html" title="17.2.16. /proc/locks" /><link rel="next" href="s2-proc-meminfo.html" title="17.2.18. /proc/meminfo" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifram
e display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.17. <code class="filename">/proc/mdstat</code> </h3></div></div></div><a id="id686869" 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>17.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>17.2.18. /proc/meminfo </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-meminfo.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-meminfo.html
new file mode 100644
index 0000000..0b3e9fb
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-meminfo.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-mdstat.html" title="17.2.17. /proc/mdstat" /><link rel="next" href="s2-proc-misc.html" title="17.2.19. /proc/misc" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe d
isplay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="s2-proc-misc.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2.18. <code class="filename">/proc/meminfo</code> </h3></div></div></div><a id="id607185" 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>17.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>17.2.19. /proc/misc </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-misc.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-misc.html
new file mode 100644
index 0000000..ff145d7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-misc.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-meminfo.html" title="17.2.18. /proc/meminfo" /><link rel="next" href="s2-proc-modules.html" title="17.2.20. /proc/modules" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifr
ame display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.19. <code class="filename">/proc/misc</code> </h3></div></div></div><a id="id1020096" 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>17.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>17.2.20. /proc/modules </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-modules.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-modules.html
new file mode 100644
index 0000000..6b1335b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-modules.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-misc.html" title="17.2.19. /proc/misc" /><link rel="next" href="s2-proc-mounts.html" title="17.2.21. /proc/mounts" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe d
isplay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.20. <code class="filename">/proc/modules</code> </h3></div></div></div><a id="id936037" 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"><h2>Note</h2><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><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>17.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>17.2.21. /proc/mounts </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-mounts.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-mounts.html
new file mode 100644
index 0000000..a380a39
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-mounts.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-modules.html" title="17.2.20. /proc/modules" /><link rel="next" href="s2-proc-mtrr.html" title="17.2.22. /proc/mtrr" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.21. <code class="filename">/proc/mounts</code> </h3></div></div></div><a id="id936154" 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>17.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>17.2.22. /proc/mtrr </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-mtrr.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-mtrr.html
new file mode 100644
index 0000000..eba074b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-mtrr.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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-mounts.html" title="17.2.21. /proc/mounts" /><link rel="next" href="s2-proc-partitions.html" title="17.2.23. /proc/partitions" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable
iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.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">17.2.22. <code class="filename">/proc/mtrr</code> </h3></div></div></div><a id="id769131" 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>version</code></em>/Documentation/mtrr.txt
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-mounts.html"><strong>Prev</strong>17.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>17.2.23. /proc/partitions </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-partitions.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-partitions.html
new file mode 100644
index 0000000..2b4bde5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-partitions.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>17.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-mtrr.html" title="17.2.22. /proc/mtrr" /><link rel="next" href="s2-proc-pci.html" title="17.2.24. /proc/pci" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe disp
lay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-pci.html"><strong>Next</strong></a></li></ul><div class="section" title="17.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">17.2.23. <code class="filename">/proc/partitions</code> </h3></div></div></div><a id="id892893" 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>17.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-pci.html"><strong>Next</strong>17.2.24. /proc/pci </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-pci.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-pci.html
new file mode 100644
index 0000000..1820095
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-pci.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.2.24. /proc/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-partitions.html" title="17.2.23. /proc/partitions" /><link rel="next" href="s2-proc-slabinfo.html" title="17.2.25. /proc/slabinfo" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or ena
ble iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-slabinfo.html"><strong>Next</strong></a></li></ul><div class="section" title="17.2.24. /proc/pci" id="s2-proc-pci"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-pci">17.2.24. <code class="filename">/proc/pci</code> </h3></div></div></div><a id="id964308" class="indexterm"></a><a id="id964339" class="indexterm"></a><div class="para">
+ This file contains a full listing of every PCI device on the system. Depending on the number of PCI devices, <code class="filename">/proc/pci</code> can be rather long. A sampling of this file from a basic system looks similar to the following:
+ </div><pre class="screen">
+Bus 0, device 0, function 0: Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 3). Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe4000000 [0xe7ffffff].
+Bus 0, device 1, function 0: PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 3). Master Capable. Latency=64. Min Gnt=128.
+Bus 0, device 4, function 0: ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 2).
+Bus 0, device 4, function 1: IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 1). Master Capable. Latency=32. I/O at 0xd800 [0xd80f].
+Bus 0, device 4, function 2: USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 1). IRQ 5. Master Capable. Latency=32. I/O at 0xd400 [0xd41f].
+Bus 0, device 4, function 3: Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 2). IRQ 9.
+Bus 0, device 9, function 0: Ethernet controller: Lite-On Communications Inc LNE100TX (rev 33). IRQ 5. Master Capable. Latency=32. I/O at 0xd000 [0xd0ff].
+Bus 0, device 12, function 0: VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 1). IRQ 11. Master Capable. Latency=32. Min Gnt=4.Max Lat=255.
+</pre><div class="para">
+ This output shows a list of all PCI devices, sorted in the order of bus, device, and function. 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 class="note"><h2>Tip</h2><div class="para">
+ To get a more readable version of this information, type:
+ </div><pre class="screen">
+/sbin/lspci -vb
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-partitions.html"><strong>Prev</strong>17.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-slabinfo.html"><strong>Next</strong>17.2.25. /proc/slabinfo </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-pid.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-pid.html
new file mode 100644
index 0000000..7b735b8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-pid.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>17.3.11. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="prev" href="s2-proc-tty.html" title="17.3.10. /proc/tty/" /><link rel="next" href="s1-proc-sysctl.html" title="17.4. Using the sysctl Command" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</if
rame></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-sysctl.html"><strong>Next</strong></a></li></ul><div class="section" title="17.3.11. /proc/PID/" id="s2-proc-pid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-pid">17.3.11. <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> </h3></div></div></div><a id="id886872" 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>17.3.10. /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>17.4. Using the sysctl Command</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-slabinfo.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-slabinfo.html
new file mode 100644
index 0000000..59ec081
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-slabinfo.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.25. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-pci.html" title="17.2.24. /proc/pci" /><link rel="next" href="s2-proc-stat.html" title="17.2.26. /proc/stat" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe displa
y.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-stat.html"><strong>Next</strong></a></li></ul><div class="section" title="17.2.25. /proc/slabinfo" id="s2-proc-slabinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-slabinfo">17.2.25. <code class="filename">/proc/slabinfo</code> </h3></div></div></div><a id="id964413" class="indexterm"></a><a id="id643924" 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-pci.html"><strong>Prev</strong>17.2.24. /proc/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-stat.html"><strong>Next</strong>17.2.26. /proc/stat </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-stat.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-stat.html
new file mode 100644
index 0000000..c814581
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-stat.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>17.2.26. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-slabinfo.html" title="17.2.25. /proc/slabinfo" /><link rel="next" href="s2-proc-swaps.html" title="17.2.27. /proc/swaps" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifram
e display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.2.26. /proc/stat" id="s2-proc-stat"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-stat">17.2.26. <code class="filename">/proc/stat</code> </h3></div></div></div><a id="id842831" class="indexterm"></a><a id="id842853" class="indexterm"></a><a id="id756253" 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>17.2.25. /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>17.2.27. /proc/swaps </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-swaps.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-swaps.html
new file mode 100644
index 0000000..0cc3d38
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-swaps.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>17.2.27. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-stat.html" title="17.2.26. /proc/stat" /><link rel="next" href="s2-proc-sysrq-trigger.html" title="17.2.28. /proc/sysrq-trigger" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or ena
ble iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.2.27. /proc/swaps" id="s2-proc-swaps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-swaps">17.2.27. <code class="filename">/proc/swaps</code> </h3></div></div></div><a id="id768904" 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>17.2.26. /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>17.2.28. /proc/sysrq-trigger </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-sysrq-trigger.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-sysrq-trigger.html
new file mode 100644
index 0000000..861d69f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-sysrq-trigger.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.28. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-swaps.html" title="17.2.27. /proc/swaps" /><link rel="next" href="s2-proc-uptime.html" title="17.2.29. /proc/uptime" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable
iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="17.2.28. /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">17.2.28. <code class="filename">/proc/sysrq-trigger</code> </h3></div></div></div><a id="id768970" 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="17.3.8.3. /proc/sys/kernel/">Section 17.3.8.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>17.2.27. /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>17.2.29. /proc/uptime </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-tty.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-tty.html
new file mode 100644
index 0000000..a698b3e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-tty.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>17.3.10. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-sysvipc.html" title="17.3.9. /proc/sysvipc/" /><link rel="next" href="s2-proc-pid.html" title="17.3.11. /proc/PID/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</ifra
me></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-proc-pid.html"><strong>Next</strong></a></li></ul><div class="section" title="17.3.10. /proc/tty/" id="s2-proc-tty"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-tty">17.3.10. <code class="filename">/proc/tty/</code> </h3></div></div></div><a id="id717192" 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>17.3.9. /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>17.3.11. /proc/PID/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-uptime.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-uptime.html
new file mode 100644
index 0000000..94f9279
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-uptime.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.29. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-sysrq-trigger.html" title="17.2.28. /proc/sysrq-trigger" /><link rel="next" href="s2-proc-version.html" title="17.2.30. /proc/version" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="next"><a accesskey="n" href="s2-proc-version.html"><strong>Next</strong></a></li></ul><div class="section" title="17.2.29. /proc/uptime" id="s2-proc-uptime"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-uptime">17.2.29. <code class="filename">/proc/uptime</code> </h3></div></div></div><a id="id969525" 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>17.2.28. /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>17.2.30. /proc/version </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-version.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-version.html
new file mode 100644
index 0000000..42ad05c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-proc-version.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.30. /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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="17.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-uptime.html" title="17.2.29. /proc/uptime" /><link rel="next" href="s1-proc-directories.html" title="17.3. Directories within /proc/" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser
or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s1-proc-directories.html"><strong>Next</strong></a></li></ul><div class="section" title="17.2.30. /proc/version" id="s2-proc-version"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-version">17.2.30. <code class="filename">/proc/version</code> </h3></div></div></div><a id="id969580" 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>17.2.29. /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>17.3. Directories within /proc/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-redhat-config-users-process.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-redhat-config-users-process.html
new file mode 100644
index 0000000..967d1aa
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-redhat-config-users-process.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>22.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-users-tools.html" title="22.2. User and Group Management Tools" /><link rel="prev" href="s1-users-tools.html" title="22.2. User and Group Management Tools" /><link rel="next" href="s1-users-groups-standard-users.html" title="22.3. Standard Users" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your
browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s1-users-groups-standard-users.html"><strong>Next</strong></a></li></ul><div class="section" title="22.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">22.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"><h2>Note</h2><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></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="ers_and_Groups.html#s2-redhat-config-users-user-new" title="22.1.1. Adding a New User">Section 22.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>22.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>22.3. Standard Users</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-freshening.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-freshening.html
new file mode 100644
index 0000000..40b82c1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-freshening.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class=
"left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id792356" class="indexterm"></a><a id="id614571" 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.fc13.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_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-querying.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-querying.html
new file mode 100644
index 0000000..1508fff
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-querying.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="lef
t" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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</strong></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="id753351" class="indexterm"></a><a id="id753363" 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.fc13.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_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-related-books.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-related-books.html
new file mode 100644
index 0000000..9d32b55
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-related-books.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your br
owser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="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="id618584" class="indexterm"></a><a id="id618596" class="indexterm"></a><div class="variablelist"><dl><dt><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><span class="term"> <em class="citetitle">Red Hat RPM Guide</em> — <a href="http://docs.fedoraproject.org/drafts/rpm-guide-en/">http://docs.fedoraproject.org/drafts/rpm-guide-en/</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_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-uninstalling.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-uninstalling.html
new file mode 100644
index 0000000..54979e6
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-uninstalling.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</ifram
e></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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" href="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="id757577" class="indexterm"></a><a id="id757589" class="indexterm"></a><a id="id841874" class="indexterm"></a><a id="id841890" 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"><h2>Note</h2><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.fc13.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 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.fc13.x86_64
+ libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc13.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc13.x86_64
+ ghostscript is needed by (installed) printer-filters-1.1-4.fc13.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.fc13.x86_64</pre><div class="warning"><h2>Warning: Forcing Package Installation</h2><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><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_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-useful-websites.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-useful-websites.html
new file mode 100644
index 0000000..7b69122
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-useful-websites.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enabl
e iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id952870" 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_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-verifying.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-verifying.html
new file mode 100644
index 0000000..15aea0c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-rpm-verifying.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="titl
e"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>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="id750107" class="indexterm"></a><a id="id750119" 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.fc13.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_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-configuring-cmdline.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-configuring-cmdline.html
new file mode 100644
index 0000000..f77e20b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-configuring-cmdline.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>9.4.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-samba-configuring.html" title="9.4. Configuring a Samba Server" /><link rel="prev" href="s1-samba-configuring.html" title="9.4. Configuring a Samba Server" /><link rel="next" href="s2-samba-encrypted-passwords.html" title="9.4.3. Encrypted Passwords" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrad
e your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-configuring.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-samba-encrypted-passwords.html"><strong>Next</strong></a></li></ul><div class="section" title="9.4.2. Command Line Configuration" id="s2-samba-configuring-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-configuring-cmdline">9.4.2. Command Line Configuration</h3></div></div></div><a id="id957869" class="indexterm"></a><div class="para">
+ Samba uses <code class="filename">/etc/samba/smb.conf</code> as its configuration file. If you change this configuration file, the changes do not take effect until you restart the Samba daemon with the command <code class="command">service smb restart</code>.
+ </div><div class="para">
+ To specify the Windows workgroup and a brief description of the Samba server, edit the following lines in your <code class="filename">smb.conf</code> file:
+ </div><pre class="screen">
+workgroup = <em class="replaceable"><code>WORKGROUPNAME</code></em>
+server string = <em class="replaceable"><code>BRIEF COMMENT ABOUT SERVER</code></em>
+</pre><div class="para">
+ Replace <em class="replaceable"><code>WORKGROUPNAME</code></em> with the name of the Windows workgroup to which this machine should belong. The <em class="replaceable"><code>BRIEF COMMENT ABOUT SERVER</code></em> is optional and is used as the Windows comment about the Samba system.
+ </div><div class="para">
+ To create a Samba share directory on your Linux system, add the following section to your <code class="command">smb.conf</code> file (after modifying it to reflect your needs and your system):
+ </div><pre class="screen">
+[<em class="replaceable"><code>sharename</code></em>]
+comment = <em class="replaceable"><code>Insert a comment here</code></em>
+path = <em class="replaceable"><code>/home/share/</code></em>
+valid users = <em class="replaceable"><code>tfox carole</code></em>
+public = no
+writable = yes
+printable = no
+create mask = 0765
+</pre><div class="para">
+ The above example allows the users <code class="command">tfox</code> and <code class="command">carole</code> to read and write to the directory <code class="filename">/home/share</code>, on the Samba server, from a Samba client.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-configuring.html"><strong>Prev</strong>9.4. Configuring a Samba 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-samba-encrypted-passwords.html"><strong>Next</strong>9.4.3. Encrypted Passwords</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-domain-controller.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-domain-controller.html
new file mode 100644
index 0000000..dcf22b3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-domain-controller.html
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.6.3. Domain Controller</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-samba-servers.html" title="9.6. Samba Server Types and the smb.conf File" /><link rel="prev" href="s2-samba-domain-member.html" title="9.6.2. Domain Member Server" /><link rel="next" href="s1-samba-security-modes.html" title="9.7. Samba Security Modes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your
browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-domain-member.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-security-modes.html"><strong>Next</strong></a></li></ul><div class="section" title="9.6.3. Domain Controller" id="s2-samba-domain-controller"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-domain-controller">9.6.3. Domain Controller</h3></div></div></div><a id="id740359" class="indexterm"></a><div class="para">
+ A domain controller in Windows NT is functionally similar to a Network Information Service (NIS) server in a Linux environment. Domain controllers and NIS servers both host user/group information databases as well as related services. Domain controllers are mainly used for security, including the authentication of users accessing domain resources. The service that maintains the user/group database integrity is called the <em class="firstterm">Security Account Manager</em> (SAM). The SAM database is stored differently between Windows and Linux Samba-based systems, therefore SAM replication cannot be achieved and platforms cannot be mixed in a PDC/BDC environment.
+ </div><div class="para">
+ In a Samba environment, there can be only one PDC and zero or more BDCs.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Samba cannot exist in a mixed Samba/Windows domain controller environment (Samba cannot be a BDC of a Windows PDC or vice versa). Alternatively, Samba PDCs and BDCs <span class="emphasis"><em>can</em></span> coexist.
+ </div></div><div class="section" title="9.6.3.1. Primary Domain Controller (PDC) using tdbsam" id="s3-samba-pdc-tdbsam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-pdc-tdbsam">9.6.3.1. Primary Domain Controller (PDC) using <code class="command">tdbsam</code> </h4></div></div></div><a id="id833926" class="indexterm"></a><div class="para">
+ The simplest and most common implementation of a Samba PDC uses the <code class="command">tdbsam</code> password database backend. Planned to replace the aging <code class="command">smbpasswd</code> backend, <code class="command">tdbsam</code> has numerous improvements that are explained in more detail in <a class="xref" href="s1-samba-account-info-dbs.html" title="9.8. Samba Account Information Databases">Section 9.8, “Samba Account Information Databases”</a>. The <code class="command">passdb backend</code> directive controls which backend is to be used for the PDC.
+ </div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+passdb backend = tdbsam
+security = user
+add user script = /usr/sbin/useradd -m %u
+delete user script = /usr/sbin/userdel -r %u
+add group script = /usr/sbin/groupadd %g
+delete group script = /usr/sbin/groupdel %g
+add user to group script = /usr/sbin/usermod -G %g %u
+add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null -g machines %u
+# The following specifies the default logon script
+# Per user logon scripts can be specified in the user
+# account using pdbedit logon script = logon.bat
+# This sets the default profile path.
+# Set per user paths with pdbedit
+logon drive = H:
+domain logons = Yes
+os level = 35
+preferred master = Yes
+domain master = Yes
+[homes]
+ comment = Home Directories
+ valid users = %S
+ read only = No
+[netlogon]
+ comment = Network Logon Service
+ path = /var/lib/samba/netlogon/scripts
+ browseable = No
+ read only = No
+# For profiles to work, create a user directory under the
+# path shown.
+<code class="command">mkdir -p /var/lib/samba/profiles/john</code>
+[Profiles]
+ comment = Roaming Profile Share
+ path = /var/lib/samba/profiles
+ read only = No
+ browseable = No
+ guest ok = Yes
+ profile acls = Yes
+# Other resource shares ... ...
+</pre><div class="note"><h2>Note</h2><div class="para">
+ If you need more than one domain controller or have more than 250 users, do <span class="emphasis"><em>not</em></span> use a <code class="command">tdbsam</code> authentication backend. LDAP is recommended in these cases.
+ </div></div></div><div class="section" title="9.6.3.2. Primary Domain Controller (PDC) with Active Directory" id="samba-rgs-pdc-ads"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="samba-rgs-pdc-ads">9.6.3.2. Primary Domain Controller (PDC) with Active Directory</h4></div></div></div><a id="id834025" class="indexterm"></a><div class="para">
+ Although it is possible for Samba to be a member of an Active Directory, it is not possible for Samba to operate as an Active Directory domain controller.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-samba-domain-member.html"><strong>Prev</strong>9.6.2. Domain Member 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-samba-security-modes.html"><strong>Next</strong>9.7. Samba Security Modes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-domain-member.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-domain-member.html
new file mode 100644
index 0000000..ba963cd
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-domain-member.html
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.6.2. Domain Member 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-samba-servers.html" title="9.6. Samba Server Types and the smb.conf File" /><link rel="prev" href="s1-samba-servers.html" title="9.6. Samba Server Types and the smb.conf File" /><link rel="next" href="s2-samba-domain-controller.html" title="9.6.3. Domain Controller" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-servers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-samba-domain-controller.html"><strong>Next</strong></a></li></ul><div class="section" title="9.6.2. Domain Member Server" id="s2-samba-domain-member"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-domain-member">9.6.2. Domain Member Server</h3></div></div></div><a id="id662765" class="indexterm"></a><div class="para">
+ A domain member, while similar to a stand-alone server, is logged into a domain controller (either Windows or Samba) and is subject to the domain's security rules. An example of a domain member server would be a departmental server running Samba that has a machine account on the Primary Domain Controller (PDC). All of the department's clients still authenticate with the PDC, and desktop profiles and all network policy files are included. The difference is that the departmental server has the ability to control printer and network shares.
+ </div><div class="section" title="9.6.2.1. Active Directory Domain Member Server" id="s3-samba-domain-member-ads"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-domain-member-ads">9.6.2.1. Active Directory Domain Member Server</h4></div></div></div><a id="id902413" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement an Active Directory domain member server. In this example, Samba authenticates users for services being run locally but is also a client of the Active Directory. Ensure that your kerberos <code class="command">realm</code> parameter is shown in all caps (for example <code class="command">realm = EXAMPLE.COM</code>). Since Windows 2000/2003 requires Kerberos for Active Directory authentication, the <code class="command">realm</code> directive is required. If Active Directory and Kerberos are running on different servers, the <code class="command">password server</code> directive may be required to help the distinction.
+ </div><pre class="screen">
+[global]
+realm = EXAMPLE.COM
+security = ADS
+encrypt passwords = yes
+# Optional. Use only if Samba cannot determine the Kerberos server automatically.
+password server = kerberos.example.com
+</pre><div class="para">
+ In order to join a member server to an Active Directory domain, the following steps must be completed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Configuration of the <code class="filename">smb.conf</code> file on the member server
+ </div></li><li class="listitem"><div class="para">
+ Configuration of Kerberos, including the <code class="filename">/etc/krb5.conf</code> file, on the member server
+ </div></li><li class="listitem"><div class="para">
+ Creation of the machine account on the Active Directory domain server
+ </div></li><li class="listitem"><div class="para">
+ Association of the member server to the Active Directory domain
+ </div></li></ul></div><div class="para">
+ To create the machine account and join the Windows 2000/2003 Active Directory, Kerberos must first be initialized for the member server wishing to join the Active Directory domain. To create an administrative Kerberos ticket, type the following command as root on the member server:
+ </div><pre class="screen">
+<strong class="userinput"><code>kinit administrator at EXAMPLE.COM</code></strong></pre><div class="para">
+ The <code class="command">kinit</code> command is a Kerberos initialization script that references the Active Directory administrator account and Kerberos realm. Since Active Directory requires Kerberos tickets, <code class="command">kinit</code> obtains and caches a Kerberos ticket-granting ticket for client/server authentication. For more information on Kerberos, the <code class="command">/etc/krb5.conf</code> file, and the <code class="command">kinit</code> command, refer to .
+ </div><div class="para">
+ To join an Active Directory server (windows1.example.com), type the following command as root on the member server:
+ </div><pre class="screen">
+<strong class="userinput"><code>net ads join -S windows1.example.com -U administrator%password</code></strong></pre><div class="para">
+ Since the machine <code class="command">windows1</code> was automatically found in the corresponding Kerberos realm (the <code class="command">kinit</code> command succeeded), the <code class="command">net</code> command connects to the Active Directory server using its required administrator account and password. This creates the appropriate machine account on the Active Directory and grants permissions to the Samba domain member server to join the domain.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ Since <code class="command">security = ads</code> and not <code class="command">security = user</code> is used, a local password backend such as <code class="filename">smbpasswd</code> is not needed. Older clients that do not support <code class="command">security = ads</code> are authenticated as if <code class="command">security = domain</code> had been set. This change does not affect functionality and allows local users not previously in the domain.
+ </div></div></div><div class="section" title="9.6.2.2. Windows NT4-based Domain Member Server" id="s3-samba-domain-member-nt4"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-samba-domain-member-nt4">9.6.2.2. Windows NT4-based Domain Member Server</h4></div></div></div><a id="id598929" class="indexterm"></a><div class="para">
+ The following <code class="command">smb.conf</code> file shows a sample configuration needed to implement a Windows NT4-based domain member server. Becoming a member server of an NT4-based domain is similar to connecting to an Active Directory. The main difference is NT4-based domains do not use Kerberos in their authentication method, making the <code class="command">smb.conf</code> file simpler. In this instance, the Samba member server functions as a pass through to the NT4-based domain server.
+ </div><pre class="screen">
+[global]
+workgroup = DOCS
+netbios name = DOCS_SRV
+security = domain
+[homes]
+comment = Home Directories
+valid users = %S
+read only = No
+browseable = No
+[public]
+comment = Data
+path = /export
+force user = docsbot
+force group = users
+guest ok = Yes
+</pre><div class="para">
+ Having Samba as a domain member server can be useful in many situations. There are times where the Samba server can have other uses besides file and printer sharing. It may be beneficial to make Samba a domain member server in instances where Linux-only applications are required for use in the domain environment. Administrators appreciate keeping track of all machines in the domain, even if not Windows-based. In the event the Windows-based server hardware is deprecated, it is quite easy to modify the <code class="command">smb.conf</code> file to convert the server to a Samba-based PDC. If Windows NT-based servers are upgraded to Windows 2000/2003, the <code class="command">smb.conf</code> file is easily modifiable to incorporate the infrastructure change to Active Directory if needed.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ After configuring the <code class="command">smb.conf</code> file, join the domain <span class="emphasis"><em>before</em></span> starting Samba by typing the following command as root:
+ </div><pre class="screen">
+<strong class="userinput"><code>net rpc join -U administrator%password</code></strong></pre></div><div class="para">
+ Note that the <code class="option">-S</code> option, which specifies the domain server hostname, does not need to be stated in the <code class="command">net rpc join</code> command. Samba uses the hostname specified by the <code class="command">workgroup</code> directive in the <code class="filename">smb.conf</code> file instead of it being stated explicitly.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-servers.html"><strong>Prev</strong>9.6. Samba Server Types and the smb.conf 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="s2-samba-domain-controller.html"><strong>Next</strong>9.6.3. Domain Controller</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-encrypted-passwords.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-encrypted-passwords.html
new file mode 100644
index 0000000..c2e5ab3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-encrypted-passwords.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.3. Encrypted 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-samba-configuring.html" title="9.4. Configuring a Samba Server" /><link rel="prev" href="s2-samba-configuring-cmdline.html" title="9.4.2. Command Line Configuration" /><link rel="next" href="s1-samba-startstop.html" title="9.5. Starting and Stopping Samba" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade
your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-configuring-cmdline.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-startstop.html"><strong>Next</strong></a></li></ul><div class="section" title="9.4.3. Encrypted Passwords" id="s2-samba-encrypted-passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-encrypted-passwords">9.4.3. Encrypted Passwords</h3></div></div></div><div class="para">
+ Encrypted passwords are enabled by default because it is more secure to do so. To create a user with an encrypted password, use the command <code class="command">smbpasswd -a <em class="replaceable"><code><username></code></em> </code>.
+ </div><a id="id938484" class="indexterm"></a><a id="id938498" class="indexterm"></a><a id="id938512" class="indexterm"></a><a id="id605583" class="indexterm"></a><a id="id605597" class="indexterm"></a><a id="id605611" class="indexterm"></a><a id="id605641" class="indexterm"></a></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-samba-configuring-cmdline.html"><strong>Prev</strong>9.4.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="s1-samba-startstop.html"><strong>Next</strong>9.5. Starting and Stopping Samba</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-resources-community.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-resources-community.html
new file mode 100644
index 0000000..5f519cd
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-resources-community.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.12.3. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-samba-resources.html" title="9.12. Additional Resources" /><link rel="prev" href="s2-samba-resources-published.html" title="9.12.2. Related Books" /><link rel="next" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 10. Dynamic Host Configuration Protocol (DHCP)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an
iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-resources-published.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="9.12.3. Useful Websites" id="s2-samba-resources-community"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-resources-community">9.12.3. Useful Websites</h3></div></div></div><a id="id692245" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.samba.org/">http://www.samba.org/</a> — Homepage for the Samba distribution and all official documentation created by the Samba development team. Many resources are available in HTML and PDF formats, while others are only available for purchase. Although many of these links are not Fedora specific, some concepts may apply.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://us1.samba.org/samba/archives.html">http://samba.org/samba/archives.html </a> — Active email lists for the Samba community. Enabling digest mode is recommended due to high levels of list activity.
+ </div></li><li class="listitem"><div class="para">
+ Samba newsgroups — Samba threaded newsgroups, such as gmane.org, that use the NNTP protocol are also available. This an alternative to receiving mailing list emails.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://sourceforge.net/projects/smbldap-tools/">hhttp://sourceforge.net/projects/smbldap-tools/</a> — These are highly recommended for assisting in managing LDAP related resources. The scripts can be found at <code class="command">/usr/share/doc/samba-<em class="replaceable"><code>version_number</code></em>/LDAP/smbldap-tools</code> or can be downloaded from Sourceforge.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-samba-resources-published.html"><strong>Prev</strong>9.12.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="ch-Dynamic_Host_Configuration_Protocol_DHCP.html"><strong>Next</strong>Chapter 10. Dynamic Host Configuration Protocol (...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-resources-published.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-resources-published.html
new file mode 100644
index 0000000..293d3dd
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-resources-published.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.12.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-samba-resources.html" title="9.12. Additional Resources" /><link rel="prev" href="s1-samba-resources.html" title="9.12. Additional Resources" /><link rel="next" href="s2-samba-resources-community.html" title="9.12.3. Useful Websites" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifra
me display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-samba-resources-community.html"><strong>Next</strong></a></li></ul><div class="section" title="9.12.2. Related Books" id="s2-samba-resources-published"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-resources-published">9.12.2. Related Books</h3></div></div></div><a id="id692171" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">The Official Samba-3 HOWTO-Collection</em> by John H. Terpstra and Jelmer R. Vernooij; Prentice Hall — The official Samba-3 documentation as issued by the Samba development team. This is more of a reference guide than a step-by-step guide.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Samba-3 by Example</em> by John H. Terpstra; Prentice Hall — This is another official release issued by the Samba development team which discusses detailed examples of OpenLDAP, DNS, DHCP, and printing configuration files. This has step-by-step related information that helps in real-world implementations.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Using Samba, 2nd Edition</em> by Jay T's, Robert Eckstein, and David Collier-Brown; O'Reilly — A good resource for novice to advanced users, which includes comprehensive reference material.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-resources.html"><strong>Prev</strong>9.12. 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-samba-resources-community.html"><strong>Next</strong>9.12.3. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-share-level.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-share-level.html
new file mode 100644
index 0000000..a13de7d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-share-level.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>9.7.2. Share-Level Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-samba-security-modes.html" title="9.7. Samba Security Modes" /><link rel="prev" href="s1-samba-security-modes.html" title="9.7. Samba Security Modes" /><link rel="next" href="s1-samba-account-info-dbs.html" title="9.8. Samba Account Information Databases" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade
your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-security-modes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-account-info-dbs.html"><strong>Next</strong></a></li></ul><div class="section" title="9.7.2. Share-Level Security" id="s2-samba-share-level"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-share-level">9.7.2. Share-Level Security</h3></div></div></div><a id="id906739" class="indexterm"></a><div class="para">
+ With share-level security, the server accepts only a password without an explicit username from the client. The server expects a password for each share, independent of the username. There have been recent reports that Microsoft Windows clients have compatibility issues with share-level security servers. Samba developers strongly discourage use of share-level security.
+ </div><div class="para">
+ In <code class="filename">smb.conf</code>, the <code class="command">security = share</code> directive that sets share-level security is:
+ </div><pre class="screen">
+[GLOBAL]
+...
+security = share
+...
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-security-modes.html"><strong>Prev</strong>9.7. Samba Security Modes</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-account-info-dbs.html"><strong>Next</strong>9.8. Samba Account Information Databases</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-wins.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-wins.html
new file mode 100644
index 0000000..552300a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-samba-wins.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>9.9.2. WINS (Windows Internetworking Name 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-samba-network-browsing.html" title="9.9. Samba Network Browsing" /><link rel="prev" href="s1-samba-network-browsing.html" title="9.9. Samba Network Browsing" /><link rel="next" href="s1-samba-cups.html" title="9.10. Samba with CUPS Printing Support" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to
view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-samba-network-browsing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-samba-cups.html"><strong>Next</strong></a></li></ul><div class="section" title="9.9.2. WINS (Windows Internetworking Name Server)" id="s2-samba-wins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-samba-wins">9.9.2. WINS (Windows Internetworking Name Server)</h3></div></div></div><a id="id881813" class="indexterm"></a><a id="id881828" class="indexterm"></a><div class="para">
+ Either a Samba server or a Windows NT server can function as a WINS server. When a WINS server is used with NetBIOS enabled, UDP unicasts can be routed which allows name resolution across networks. Without a WINS server, the UDP broadcast is limited to the local subnet and therefore cannot be routed to other subnets, workgroups, or domains. If WINS replication is necessary, do not use Samba as your primary WINS server, as Samba does not currently support WINS replication.
+ </div><div class="para">
+ In a mixed NT/2000/2003 server and Samba environment, it is recommended that you use the Microsoft WINS capabilities. In a Samba-only environment, it is recommended that you use <span class="emphasis"><em>only one</em></span> Samba server for WINS.
+ </div><div class="para">
+ The following is an example of the <code class="filename">smb.conf</code> file in which the Samba server is serving as a WINS server:
+ </div><pre class="screen">
+[global]
+wins support = Yes
+</pre><div class="note"><h2>Tip</h2><div class="para">
+ All servers (including Samba) should connect to a WINS server to resolve NetBIOS names. Without WINS, browsing only occurs on the local subnet. Furthermore, even if a domain-wide list is somehow obtained, hosts cannot be resolved for the client without WINS.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-samba-network-browsing.html"><strong>Prev</strong>9.9. Samba Network Browsing</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-samba-cups.html"><strong>Next</strong>9.10. Samba with CUPS Printing Support</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-secureserver-certs.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-secureserver-certs.html
new file mode 100644
index 0000000..e19ce48
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-secureserver-certs.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>11.8.4. Types of Certificates</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-httpd-secure-server.html" title="11.8. Apache HTTP Secure Server Configuration" /><link rel="prev" href="s1-secureserver-oldcert.html" title="11.8.3. Using Pre-Existing Keys and Certificates" /><link rel="next" href="s2-secureserver-generatingkey.html" title="11.8.5. Generating a Key" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-secureserver-oldcert.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-secureserver-generatingkey.html"><strong>Next</strong></a></li></ul><div class="section" title="11.8.4. Types of Certificates" id="s2-secureserver-certs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-secureserver-certs">11.8.4. Types of Certificates</h3></div></div></div><a id="id790468" class="indexterm"></a><div class="para">
+ If you installed your secure server from the RPM package provided by Red Hat, a randomly generated private key and a test certificate are generated and put into the appropriate directories. Before you begin using your secure server, however, you must generate your own key and obtain a certificate which correctly identifies your server.
+ </div><div class="para">
+ You need a key and a certificate to operate your secure server — which means that you can either generate a self-signed certificate or purchase a CA-signed certificate from a CA. What are the differences between the two?
+ </div><div class="para">
+ A CA-signed certificate provides two important capabilities for your server:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Browsers (usually) automatically recognize the certificate and allow a secure connection to be made, without prompting the user.
+ </div></li><li class="listitem"><div class="para">
+ When a CA issues a signed certificate, they are guaranteeing the identity of the organization that is providing the webpages to the browser.
+ </div></li></ul></div><div class="para">
+ If your secure server is being accessed by the public at large, your secure server needs a certificate signed by a CA so that people who visit your website know that the website is owned by the organization who claims to own it. Before signing a certificate, a CA verifies that the organization requesting the certificate was actually who they claimed to be.
+ </div><div class="para">
+ Most Web browsers that support SSL have a list of CAs whose certificates they automatically accept. If a browser encounters a certificate whose authorizing CA is not in the list, the browser asks the user to either accept or decline the connection.
+ </div><div class="para">
+ You can generate a self-signed certificate for your secure server, but be aware that a self-signed certificate does not provide the same functionality as a CA-signed certificate. A self-signed certificate is not automatically recognized by most Web browsers and does not provide any guarantee concerning the identity of the organization that is providing the website. A CA-signed certificate provides both of these important capabilities for a secure server. If your secure server is to be used in a production environment, a CA-signed certificate is recommended.
+ </div><div class="para">
+ The process of getting a certificate from a CA is fairly easy. A quick overview is as follows:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Create an encryption private and public key pair.
+ </div></li><li class="listitem"><div class="para">
+ Create a certificate request based on the public key. The certificate request contains information about your server and the company hosting it.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id853969" class="indexterm"></a>
+ <a id="id853988" class="indexterm"></a>
+ <a id="id854002" class="indexterm"></a>
+ Send the certificate request, along with documents proving your identity, to a CA. Red Hat does not make recommendations on which certificate authority to choose. Your decision may be based on your past experiences, on the experiences of your friends or colleagues, or purely on monetary factors.
+ </div><div class="para">
+ Once you have decided upon a CA, you need to follow the instructions they provide on how to obtain a certificate from them.
+ </div></li><li class="listitem"><div class="para">
+ When the CA is satisfied that you are indeed who you claim to be, they provide you with a digital certificate.
+ </div></li><li class="listitem"><div class="para">
+ Install this certificate on your secure server and begin handling secure transactions.
+ </div></li></ol></div><div class="para">
+ Whether you are getting a certificate from a CA or generating your own self-signed certificate, the first step is to generate a key. Refer to <a class="xref" href="s2-secureserver-generatingkey.html" title="11.8.5. Generating a Key">Section 11.8.5, “Generating a Key”</a> for instructions.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-secureserver-oldcert.html"><strong>Prev</strong>11.8.3. Using Pre-Existing Keys and Certificates</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-secureserver-generatingkey.html"><strong>Next</strong>11.8.5. Generating a Key</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-secureserver-generatingkey.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-secureserver-generatingkey.html
new file mode 100644
index 0000000..039c65d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-secureserver-generatingkey.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>11.8.5. Generating a Key</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-httpd-secure-server.html" title="11.8. Apache HTTP Secure Server Configuration" /><link rel="prev" href="s2-secureserver-certs.html" title="11.8.4. Types of Certificates" /><link rel="next" href="s1-use-new-key.html" title="11.8.6. How to configure the server to use the new key" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifram
e, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-secureserver-certs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-use-new-key.html"><strong>Next</strong></a></li></ul><div class="section" title="11.8.5. Generating a Key" id="s2-secureserver-generatingkey"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-secureserver-generatingkey">11.8.5. Generating a Key</h3></div></div></div><a id="id647553" class="indexterm"></a><div class="para">
+ You must be root to generate a key.
+ </div><div class="para">
+ First, use the <code class="command">cd</code> command to change to the <code class="filename">/etc/httpd/conf/</code> directory. Remove the fake key and certificate that were generated during the installation with the following commands:
+ </div><pre class="screen">
+<code class="command">rm ssl.key/server.key</code>
+ <code class="command">rm ssl.crt/server.crt</code>
+</pre><div class="para">
+ The <code class="filename">crypto-utils</code> package contains the <code class="command">genkey</code> utility which you can use to generate keys as the name implies. To create your own private key, please ensure the <code class="filename">crypto-utils</code> package is installed. You can view more options by typing <code class="command">man genkey</code> in your terminal. Assuming you wish to generate keys for www.example.com using the <code class="command">genkey</code> utility, type in the following command in your terminal:
+ </div><pre class="screen">
+<code class="command">genkey www.example.com</code>
+</pre><div class="para">
+ Please note that the <code class="command">make</code> based process is no longer shipped with RHEL 5. This will start the <code class="command">genkey</code> graphical user interface. The figure below illustrates the first screen. To navigate, use the keyboard arrow and tab keys. This windows indicates where your key will be stored and prompts you to proceed or cancel the operation. To proceed to the next step, select <span class="guilabel"><strong>Next</strong></span> and press the Return (Enter) key.
+ </div><div class="figure" title="Figure 11.11. Keypair generation" id="keypair-gen"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey1.png" width="444" alt="Keypair generation" /><div class="longdesc"><div class="para">
+ Keypair generation
+ </div></div></div></div><h6>Figure 11.11. Keypair generation</h6></div><br class="figure-break" /><div class="para">
+ The next screen prompts you to choose the size of your key. As indicated, the smaller the size of your key, the faster will the response from your server be and the lesser your level of security. On selecting your preferred, key size using the arrow keys, select <span class="guilabel"><strong>Next</strong></span> to proceed to the next step. The figure below illustrates the key size selection screen.
+ </div><div class="figure" title="Figure 11.12. Choose key size" id="keysize-choose"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey2.png" width="444" alt="Choose key size" /><div class="longdesc"><div class="para">
+ Choose key size
+ </div></div></div></div><h6>Figure 11.12. Choose key size</h6></div><br class="figure-break" /><div class="para">
+ Selecting the next step will initiate the random bits generation process which may take some time depending on the size of your selected key. The larger the size of your key, the longer it will take to generate it.
+ </div><div class="figure" title="Figure 11.13. Generating random bits" id="random-bits"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey3.png" width="444" alt="Generating random bits" /><div class="longdesc"><div class="para">
+ Generating random bits
+ </div></div></div></div><h6>Figure 11.13. Generating random bits</h6></div><br class="figure-break" /><div class="para">
+ On generating your key, you will be prompted to send a Certificate Request (CSR) to a Certificate Authority (CA).
+ </div><div class="figure" title="Figure 11.14. Generate CSR" id="generate-csr"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey4.png" width="444" alt="Generate CSR" /><div class="longdesc"><div class="para">
+ Generate CSR
+ </div></div></div></div><h6>Figure 11.14. Generate CSR</h6></div><br class="figure-break" /><div class="para">
+ Selecting <span class="guilabel"><strong>Yes</strong></span> will prompt you to select the Certificate Authority you wish to send your request to. Selecting <span class="guilabel"><strong>No</strong></span> will allow you to generate a self-signed certificate. The next step for this is illustrated in <a class="xref" href="s2-secureserver-generatingkey.html#private-signed-cert" title="Figure 11.17. Generating a self signed certificate for your server">Figure 11.17, “Generating a self signed certificate for your server”</a>.
+ </div><div class="figure" title="Figure 11.15. Choose Certificate Authority (CA)" id="choose-cert-auth"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey5.png" width="444" alt="Choose Certificate Authority (CA)" /><div class="longdesc"><div class="para">
+ Choose Certificate Authority (CA)
+ </div></div></div></div><h6>Figure 11.15. Choose Certificate Authority (CA)</h6></div><br class="figure-break" /><div class="para">
+ On Selecting your preferred option, select <span class="guilabel"><strong>Next</strong></span> to proceed to the next step. The next screen allows you to enter the details of your certificate.
+ </div><div class="figure" title="Figure 11.16. Enter details for your certificate" id="enter-cert-details"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey6.png" width="444" alt="Enter details for your certificate" /><div class="longdesc"><div class="para">
+ Enter details for your certificate
+ </div></div></div></div><h6>Figure 11.16. Enter details for your certificate</h6></div><br class="figure-break" /><div class="para">
+ If you prefer to generate a self signed cert key pair, you should not generate a CSR. To do this, select <span class="guilabel"><strong>No</strong></span> as your preferred option in the Generate CSR screen. This will display the figure below from which you can enter your certificate details. Entering your certificate details and pressing the return key will display the <a class="xref" href="s2-secureserver-generatingkey.html#protect-private-key" title="Figure 11.19. Protecting your private key">Figure 11.19, “Protecting your private key”</a> from which you can choose to encrypt your private key or not.
+ </div><div class="figure" title="Figure 11.17. Generating a self signed certificate for your server" id="private-signed-cert"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey8.png" width="444" alt="Generating a self signed certificate for your server" /><div class="longdesc"><div class="para">
+ Generating a self signed certificate for your server
+ </div></div></div></div><h6>Figure 11.17. Generating a self signed certificate for your server</h6></div><br class="figure-break" /><div class="para">
+ On entering the details of your certificate, select <span class="guilabel"><strong>Next</strong></span> to proceed. The figure below illustrates an example of a the next screen displayed after completing the details for a certificate to be sent to Equifax. Please note that if you are generating a self signed key, for your server, this screen is not displayed.
+ </div><div class="figure" title="Figure 11.18. Begin certificate request" id="begin-cert-request"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey7.png" width="444" alt="Begin certificate request" /><div class="longdesc"><div class="para">
+ Begin certificate request
+ </div></div></div></div><h6>Figure 11.18. Begin certificate request</h6></div><br class="figure-break" /><div class="para">
+ Pressing the return key, will display the next screen from which you can enable or disable the encryption of the private key. Use the spacebar to enable or disable this. When enabled, a [*] character will be displayed. On selecting your preferred option, select <span class="guilabel"><strong>Next</strong></span> to proceed to the next step.
+ </div><div class="figure" title="Figure 11.19. Protecting your private key" id="protect-private-key"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey9.png" width="444" alt="Protecting your private key" /><div class="longdesc"><div class="para">
+ Protecting your private key
+ </div></div></div></div><h6>Figure 11.19. Protecting your private key</h6></div><br class="figure-break" /><div class="para">
+ The next screen allows you to set your key passphase. Please do not lose this pass phase as you will not be able to run the server without it. You will need to regenerate a new private or public key pair and request a new certificate from your CA as indicated. For security, the passphase is not displayed as you type. On typing your preferred passphase, select <span class="guilabel"><strong>Next</strong></span> to go back to your terminal.
+ </div><div class="figure" title="Figure 11.20. Set passphase" id="set-passphase"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey10.png" width="444" alt="Set passphase" /><div class="longdesc"><div class="para">
+ Set passphase
+ </div></div></div></div><h6>Figure 11.20. Set passphase</h6></div><br class="figure-break" /><div class="para">
+ If you attempt to run <code class="command">genkey makeca</code> on a server that has an existing key pair, an error message will be displayed as illustrated below. You need to delete your existing key file as indicated to generate a new key pair.
+ </div><div class="figure" title="Figure 11.21. genkey error" id="genkey-error"><div class="figure-contents"><div class="mediaobject"><img src="images/genkey11.png" width="444" alt="genkey error" /><div class="longdesc"><div class="para">
+ genkey error
+ </div></div></div></div><h6>Figure 11.21. genkey error</h6></div><br class="figure-break" /><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs/2.2/ssl/">http://httpd.apache.org/docs/2.2/ssl/</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs/2.2/vhosts/">http://httpd.apache.org/docs/2.2/vhosts/</a>
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-secureserver-certs.html"><strong>Prev</strong>11.8.4. Types of Certificates</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-use-new-key.html"><strong>Next</strong>11.8.6. How to configure the server to use the ne...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-secureserver-overview-certs.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-secureserver-overview-certs.html
new file mode 100644
index 0000000..c04df68
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-secureserver-overview-certs.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.8.2. An Overview of Certificates and Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-httpd-secure-server.html" title="11.8. Apache HTTP Secure Server Configuration" /><link rel="prev" href="s1-httpd-secure-server.html" title="11.8. Apache HTTP Secure Server Configuration" /><link rel="next" href="s1-secureserver-oldcert.html" title="11.8.3. Using Pre-Existing Keys and Certificates" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-httpd-secure-server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-secureserver-oldcert.html"><strong>Next</strong></a></li></ul><div class="section" title="11.8.2. An Overview of Certificates and Security" id="s2-secureserver-overview-certs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-secureserver-overview-certs">11.8.2. An Overview of Certificates and Security</h3></div></div></div><a id="id665083" class="indexterm"></a><a id="id665098"
class="indexterm"></a><a id="id665112" class="indexterm"></a><a id="id665127" class="indexterm"></a><div class="para">
+ Your secure server provides security using a combination of the Secure Sockets Layer (SSL) protocol and (in most cases) a digital certificate from a Certificate Authority (CA). SSL handles the encrypted communications as well as the mutual authentication between browsers and your secure server. The CA-approved digital certificate provides authentication for your secure server (the CA puts its reputation behind its certification of your organization's identity). When your browser is communicating using SSL encryption, the <code class="computeroutput">https://</code> prefix is used at the beginning of the Uniform Resource Locator (URL) in the navigation bar.
+ </div><div class="para">
+ Encryption depends upon the use of keys (think of them as secret encoder/decoder rings in data format). In conventional or symmetric cryptography, both ends of the transaction have the same key, which they use to decode each other's transmissions. In public or asymmetric cryptography, two keys co-exist: a public key and a private key. A person or an organization keeps their private key a secret and publishes their public key. Data encoded with the public key can only be decoded with the private key; data encoded with the private key can only be decoded with the public key.
+ </div><div class="para">
+ To set up your secure server, use public cryptography to create a public and private key pair. In most cases, you send your certificate request (including your public key), proof of your company's identity, and payment to a CA. The CA verifies the certificate request and your identity, and then sends back a certificate for your secure server.
+ </div><div class="para">
+ A secure server uses a certificate to identify itself to Web browsers. You can generate your own certificate (called a "self-signed" certificate), or you can get a certificate from a CA. A certificate from a reputable CA guarantees that a website is associated with a particular company or organization.
+ </div><div class="para">
+ Alternatively, you can create your own self-signed certificate. Note, however, that self-signed certificates should not be used in most production environments. Self-signed certificates are not automatically accepted by a user's browser — users are prompted by the browser to accept the certificate and create the secure connection. Refer to <a class="xref" href="s2-secureserver-certs.html" title="11.8.4. Types of Certificates">Section 11.8.4, “Types of Certificates”</a> for more information on the differences between self-signed and CA-signed certificates.
+ </div><div class="para">
+ Once you have a self-signed certificate or a signed certificate from the CA of your choice, you must install it on your secure server.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-httpd-secure-server.html"><strong>Prev</strong>11.8. Apache HTTP Secure Server 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-secureserver-oldcert.html"><strong>Next</strong>11.8.3. Using Pre-Existing Keys and Certificates</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-services-additional-resources-books.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-services-additional-resources-books.html
new file mode 100644
index 0000000..df176db
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-services-additional-resources-books.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-services-additional-resources.html" title="6.4. Additional Resources" /><link rel="prev" href="s1-services-additional-resources.html" title="6.4. Additional Resources" /><link rel="next" href="ch-The_BIND_DNS_Server.html" title="Chapter 7. The BIND DNS Server" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade
your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-The_BIND_DNS_Server.html"><strong>Next</strong></a></li></ul><div class="section" title="6.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">6.4.2. Related Books</h3></div></div></div><div class="variablelist"><dl><dt><span class="term"> <em class="citetitle">Security Guide</em> </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>6.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-The_BIND_DNS_Server.html"><strong>Next</strong>Chapter 7. The BIND DNS Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-services-chkconfig.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-services-chkconfig.html
new file mode 100644
index 0000000..cab61c3
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-services-chkconfig.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-services-configuring.html" title="6.2. Configuring the Services" /><link rel="prev" href="s2-services-ntsysv.html" title="6.2.2. Using the ntsysv Utility" /><link rel="next" href="s1-services-running.html" title="6.3. Running the Services" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your bro
wser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s1-services-running.html"><strong>Next</strong></a></li></ul><div class="section" title="6.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">6.2.3. Using the <code class="command">chkconfig</code> Utility</h3></div></div></div><a id="id653969" class="indexterm"></a><a id="id653987" 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="6.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">6.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 6.1. Listing the services" id="ex-services-chkconfig-listing-all"><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><h6>Example 6.1. Listing the services</h6></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 6.2. Listing a single service" id="ex-services-chkconfig-listing-single"><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><h6>Example 6.2. Listing a single service</h6></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 6.3. Listing a service that is managed by xinetd" id="ex-services-chkconfig-listing-xinetd"><div class="example-contents"><pre class="screen">~]# <code class="command">chkconfig --list rsync</code>
+rsync off</pre></div><h6>Example 6.3. Listing a service that is managed by <span class="application">xinetd</span></h6></div><br class="example-break" /></div><div class="section" title="6.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">6.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="6.3.1.1. Running the Service">Section 6.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="6.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">6.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 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="6.3.1.2. Stopping the Service">Section 6.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>6.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>6.3. Running the Services</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-services-ntsysv.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-services-ntsysv.html
new file mode 100644
index 0000000..92dbe58
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-services-ntsysv.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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-services-configuring.html" title="6.2. Configuring the Services" /><link rel="prev" href="s1-services-configuring.html" title="6.2. Configuring the Services" /><link rel="next" href="s2-services-chkconfig.html" title="6.2.3. Using the chkconfig Utility" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgra
de your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="next"><a accesskey="n" href="s2-services-chkconfig.html"><strong>Next</strong></a></li></ul><div class="section" title="6.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">6.2.2. Using the <span class="application"><strong>ntsysv</strong></span> Utility</h3></div></div></div><a id="id949075" class="indexterm"></a><a id="id949092" 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 6.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 6.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 6.3. Possible Service States">Table 6.3, “Possible Service States”</a> for a list of used symbols and an explanation of their meaning.
+ </div><div class="table" title="Table 6.3. Possible Service States" id="tab-services-ntsysv-states"><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><h6>Table 6.3. Possible Service States</h6></div><br class="table-break" /><div class="section" title="6.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">6.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="6.3.1.1. Running the Service">Section 6.3.1.1, “Running the Service”</a>.
+ </div></div><div class="section" title="6.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">6.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="6.3.1.2. Stopping the Service">Section 6.3.1.2, “Stopping the Service”</a>.
+ </div></div><div class="section" title="6.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">6.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>6.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>6.2.3. Using the chkconfig Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-beyondshell-tcpip.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-beyondshell-tcpip.html
new file mode 100644
index 0000000..0d09343
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-beyondshell-tcpip.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>8.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-beyondshell.html" title="8.4. More Than a Secure Shell" /><link rel="prev" href="s1-ssh-beyondshell.html" title="8.4. More Than a Secure Shell" /><link rel="next" href="s1-openssh-additional-resources.html" title="8.5. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or
enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="8.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">8.4.2. Port Forwarding</h3></div></div></div><a id="id927124" 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"><h2>Note: Using Reserved Port Numbers</h2><div class="para">
+ Setting up port forwarding to listen on ports below 1024 requires root level access.
+ </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"><h2>Important: A Connection Is Only as Secure as a Client System</h2><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ssh-beyondshell.html"><strong>Prev</strong>8.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>8.5. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-clients-scp.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-clients-scp.html
new file mode 100644
index 0000000..117b8f4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-clients-scp.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>8.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-clients.html" title="8.3. OpenSSH Clients" /><link rel="prev" href="s1-ssh-clients.html" title="8.3. OpenSSH Clients" /><link rel="next" href="s2-ssh-clients-sftp.html" title="8.3.3. Using the sftp Utility" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</ifr
ame></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-sftp.html"><strong>Next</strong></a></li></ul><div class="section" title="8.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">8.3.2. Using the <code class="command">scp</code> Utility</h3></div></div></div><a id="id1003913" class="indexterm"></a><a id="id1003929" class="indexterm"></a><a id="id649264" 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>8.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>8.3.3. Using the sftp Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-clients-sftp.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-clients-sftp.html
new file mode 100644
index 0000000..96329b5
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-clients-sftp.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>8.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-clients.html" title="8.3. OpenSSH Clients" /><link rel="prev" href="s2-ssh-clients-scp.html" title="8.3.2. Using the scp Utility" /><link rel="next" href="s1-ssh-beyondshell.html" title="8.4. More Than a Secure Shell" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe d
isplay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="8.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">8.3.3. Using the <code class="command">sftp</code> Utility</h3></div></div></div><a id="id939876" class="indexterm"></a><a id="id939892" 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 8.3. A selection of available sftp commands">Table 8.3, “A selection of available <code class="command">sftp</code> commands”</a>).
+ </div><div class="table" title="Table 8.3. A selection of available sftp commands" id="table-ssh-clients-sftp"><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><h6>Table 8.3. A selection of available <code class="command">sftp</code> commands</h6></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>8.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>8.4. More Than a Secure Shell</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-configuration-keypairs.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-configuration-keypairs.html
new file mode 100644
index 0000000..b0b04d4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-configuration-keypairs.html
@@ -0,0 +1,143 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-configuration.html" title="8.2. An OpenSSH Configuration" /><link rel="prev" href="s2-ssh-configuration-requiring.html" title="8.2.3. Requiring SSH for Remote Connections" /><link rel="next" href="s1-ssh-clients.html" title="8.3. OpenSSH Clients" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it
upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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><li class="next"><a accesskey="n" href="s1-ssh-clients.html"><strong>Next</strong></a></li></ul><div class="section" title="8.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">8.2.4. Using a Key-Based Authentication</h3></div></div></div><a id="id867464" 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 13 uses SSH Protocol 2 and RSA keys by default (see <a class="xref" href="ch-OpenSSH.html#s2-ssh-versions" title="8.1.3. Protocol Versions">Section 8.1.3, “Protocol Versions”</a> for more information).
+ </div><div class="important"><h2>Important: Do Not Generate Key Pairs as root</h2><div class="para">
+ If you complete the steps as root, only root will be able to use the keys.
+ </div></div><div class="note"><h2>Tip: Backup Your <code class="filename">~/.ssh/</code> Directory</h2><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 class="section" title="8.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">8.2.4.1. Generating Key Pairs</h4></div></div></div><a id="id935469" class="indexterm"></a><a id="id935481" 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="id935501" 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="id760115" class="indexterm"></a><a id="id760127" 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="id760146" 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="id726602" class="indexterm"></a><a id="id726614" 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="id726634" 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="8.2.4.2. Configuring ssh-agent">Section 8.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"><h2>Important: Never Share Your Private Key</h2><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 class="section" title="8.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">8.2.4.2. Configuring <code class="command">ssh-agent</code></h4></div></div></div><a id="id961319" class="indexterm"></a><a id="id961335" 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 8.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 8.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 left, 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="id905677" class="indexterm"></a><a id="id905693" class="indexterm"></a><div class="figure" title="Figure 8.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 8.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 8.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 8.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 8.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 8.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>8.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>8.3. OpenSSH Clients</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-configuration-requiring.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-configuration-requiring.html
new file mode 100644
index 0000000..eb985a9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-configuration-requiring.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>8.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-configuration.html" title="8.2. An OpenSSH Configuration" /><link rel="prev" href="s2-ssh-configuration-sshd.html" title="8.2.2. Starting an OpenSSH Server" /><link rel="next" href="s2-ssh-configuration-keypairs.html" title="8.2.4. Using a Key-Based Authentication" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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</strong></a></li><li class="next"><a accesskey="n" href="s2-ssh-configuration-keypairs.html"><strong>Next</strong></a></li></ul><div class="section" title="8.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">8.2.3. Requiring SSH for Remote Connections</h3></div></div></div><a id="id867379" class="indexterm"></a><a id="id867391" class="indexterm"></a><div class="p
ara">
+ 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 6. Controlling Access to Services">Chapter 6, <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>8.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>8.2.4. Using a Key-Based Authentication</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-configuration-sshd.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-configuration-sshd.html
new file mode 100644
index 0000000..516685d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-ssh-configuration-sshd.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>8.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-configuration.html" title="8.2. An OpenSSH Configuration" /><link rel="prev" href="s1-ssh-configuration.html" title="8.2. An OpenSSH Configuration" /><link rel="next" href="s2-ssh-configuration-requiring.html" title="8.2.3. Requiring SSH for Remote Connections" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to
view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="8.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">8.2.2. Starting an OpenSSH Server</h3></div></div></div><a id="id643319" class="indexterm"></a><div class="note"><h2>Note: Make Sure You Have Relevant Packages Installed</h2><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><a id="id1004720" 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="id1004750" 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 6. Controlling Access to Services">Chapter 6, <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 8.1. System-wide configuration files">Table 8.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>8.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>8.2.3. Requiring SSH for Remote Connections</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-clients-winmanagers.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-clients-winmanagers.html
new file mode 100644
index 0000000..9f79d07
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-clients-winmanagers.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>21.2.2. Window Managers</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-x-clients.html" title="21.2. Desktop Environments and Window Managers" /><link rel="prev" href="s1-x-clients.html" title="21.2. Desktop Environments and Window Managers" /><link rel="next" href="s1-x-server-configuration.html" title="21.3. X Server Configuration Files" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-clients.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-x-server-configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="21.2.2. Window Managers" id="s2-x-clients-winmanagers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-clients-winmanagers">21.2.2. Window Managers</h3></div></div></div><a id="id757850" class="indexterm"></a><a id="id757864" class="indexterm"></a><a id="id757882" class="indexterm"></a><a id="id757903" class="indexterm"></a><a id="id757925" class="
indexterm"></a><a id="id757946" class="indexterm"></a><a id="id757968" class="indexterm"></a><a id="id660556" class="indexterm"></a><a id="id660573" class="indexterm"></a><a id="id660591" class="indexterm"></a><div class="para">
+ <em class="firstterm">Window managers</em> are X client programs which are either part of a desktop environment or, in some cases, stand-alone. Their primary purpose is to control the way graphical windows are positioned, resized, or moved. Window managers also control title bars, window focus behavior, and user-specified key and mouse button bindings.
+ </div><div class="para">
+ Four window managers are included with Fedora:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">kwin</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">KWin</em> window manager is the default window manager for KDE. It is an efficient window manager which supports custom themes.
+ </div></dd><dt><span class="term"> <code class="command">metacity</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Metacity</em> window manager is the default window manager for GNOME. It is a simple and efficient window manager which also supports custom themes. To run this window manager, you need to install the <code class="filename">metacity</code> package.
+ </div></dd><dt><span class="term"> <code class="command">mwm</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Motif Window Manager</em> (<code class="command">mwm</code>) is a basic, stand-alone window manager. Since it is designed to be a stand-alone window manager, it should not be used in conjunction with GNOME or KDE. To run this window manager, you need to install the <code class="filename">openmotif</code> package.
+ </div></dd><dt><span class="term"> <code class="command">twm</code> </span></dt><dd><div class="para">
+ The minimalist <em class="firstterm">Tab Window Manager</em> (<code class="command">twm</code>, which provides the most basic tool set of any of the window managers, can be used either as a stand-alone or with a desktop environment. It is installed as part of the X11R7.1 release.
+ </div></dd></dl></div><div class="para">
+ To run any of the aforementioned window managers, you will first need to boot into Runlevel 3. For instructions on how to do this, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html#s1-services-runlevels" title="6.1. Configuring the Default Runlevel">Section 6.1, “Configuring the Default Runlevel”</a>.
+ </div><div class="para">
+ Once you are logged in to Runlevel 3, you will be presented with a terminal prompt, not a graphical environment. To start a window manager, type <code class="command">xinit -e <em class="replaceable"><code><path-to-window-manager></code></em> </code> at the prompt.
+ </div><div class="para">
+ <code class="command"> <em class="replaceable"><code><path-to-window-manager></code></em> </code> is the location of the window manager binary file. The binary file can be located by typing <code class="command">which <em class="replaceable"><code>window-manager-name</code></em> </code>, where <code class="command"><em class="replaceable"><code>window-manager-name</code></em> </code> is the name of the window manager you want to run.
+ </div><div class="para">
+ For example:
+ </div><pre class="screen">~]# <code class="command">which twm</code>
+/usr/bin/twm
+~]# <code class="command">xinit -e /usr/bin/twm</code></pre><div class="para">
+ The first command above returns the absolute path to the <code class="command">twm</code> window manager, the second command starts <code class="command">twm</code>.
+ </div><div class="para">
+ To exit a window manager, close the last window or press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Backspace</strong></span>. Once you have exited the window manager, you can log back into Runlevel 5 by typing <code class="command">startx</code> at the prompt.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x-clients.html"><strong>Prev</strong>21.2. Desktop Environments and Window Managers</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-x-server-configuration.html"><strong>Next</strong>21.3. X Server Configuration Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-fonts-core.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-fonts-core.html
new file mode 100644
index 0000000..2c7a1f7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-fonts-core.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>21.4.2. Core X Font 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-x-fonts.html" title="21.4. Fonts" /><link rel="prev" href="s1-x-fonts.html" title="21.4. Fonts" /><link rel="next" href="s1-x-runlevels.html" title="21.5. Runlevels and X" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" h
ref="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-fonts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-x-runlevels.html"><strong>Next</strong></a></li></ul><div class="section" title="21.4.2. Core X Font System" id="s2-x-fonts-core"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-fonts-core">21.4.2. Core X Font System</h3></div></div></div><a id="id754177" class="indexterm"></a><a id="id754200" class="indexterm"></a><a id="id754218" class="indexterm"></a><div class="para">
+ For compatibility, Fedora provides the core X font subsystem, which uses the X Font Server (<code class="command">xfs</code>) to provide fonts to X client applications.
+ </div><div class="para">
+ The X server looks for a font server specified in the <code class="command">FontPath</code> directive within the <code class="command">Files</code> section of the <code class="filename">/etc/X11/xorg.conf</code> configuration file. Refer to <a class="xref" href="s1-x-server-configuration.html#s3-x-server-config-xorg.conf-files" title="21.3.1.4. Files">Section 21.3.1.4, “ <code class="command">Files</code> ”</a> for more information about the <code class="command">FontPath</code> entry.
+ </div><div class="para">
+ The X server connects to the <code class="command">xfs</code> server on a specified port to acquire font information. For this reason, the <code class="command">xfs</code> service must be running for X to start. For more about configuring services for a particular runlevel, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a>.
+ </div><div class="section" title="21.4.2.1. xfs Configuration" id="s3-x-fonts-xfs-config"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-x-fonts-xfs-config">21.4.2.1. <code class="command">xfs</code> Configuration</h4></div></div></div><a id="id754301" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/rc.d/init.d/xfs</code> script starts the <code class="command">xfs</code> server. Several options can be configured within its configuration file, <code class="filename">/etc/X11/fs/config</code>.
+ </div><div class="para">
+ The following lists common options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">alternate-servers</code> — Specifies a list of alternate font servers to be used if this font server is not available. A comma must separate each font server in a list.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">catalogue</code> — Specifies an ordered list of font paths to use. A comma must separate each font path in a list.
+ </div><div class="para">
+ Use the string <code class="command">:unscaled</code> immediately after the font path to make the unscaled fonts in that path load first. Then specify the entire path again, so that other scaled fonts are also loaded.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">client-limit</code> — Specifies the maximum number of clients the font server services. The default is <code class="command">10</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">clone-self</code> — Allows the font server to clone a new version of itself when the <code class="command">client-limit</code> is hit. By default, this option is <code class="command">on</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">default-point-size</code> — Specifies the default point size for any font that does not specify this value. The value for this option is set in decipoints. The default of <code class="command">120</code> corresponds to a 12 point font.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">default-resolutions</code> — Specifies a list of resolutions supported by the X server. Each resolution in the list must be separated by a comma.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">deferglyphs</code> — Specifies whether to defer loading <em class="firstterm">glyphs</em> (the graphic used to visually represent a font). To disable this feature use <code class="command">none</code>, to enable this feature for all fonts use <code class="command">all</code>, or to turn this feature on only for 16-bit fonts use <code class="command">16</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">error-file</code> — Specifies the path and file name of a location where <code class="command">xfs</code> errors are logged.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no-listen</code> — Prevents <code class="command">xfs</code> from listening to particular protocols. By default, this option is set to <code class="command">tcp</code> to prevent <code class="command">xfs</code> from listening on TCP ports for security reasons.
+ </div><div class="note"><h2>Tip</h2><div class="para">
+ If <code class="command">xfs</code> is used to serve fonts over the network, remove this line.
+ </div></div></li><li class="listitem"><div class="para">
+ <code class="command">port</code> — Specifies the TCP port that <code class="command">xfs</code> listens on if <code class="command">no-listen</code> does not exist or is commented out.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">use-syslog</code> — Specifies whether to use the system error log.
+ </div></li></ul></div></div><div class="section" title="21.4.2.2. Adding Fonts to xfs" id="s2-x-fonts-xfs-add"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-x-fonts-xfs-add">21.4.2.2. Adding Fonts to <code class="command">xfs</code> </h4></div></div></div><a id="id804622" class="indexterm"></a><div class="para">
+ To add fonts to the core X font subsystem (<code class="command">xfs</code>), follow these steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ If it does not already exist, create a directory called <code class="filename">/usr/share/fonts/local/</code> using the following command as root:
+ </div><pre class="screen">~]# <code class="command">mkdir /usr/share/fonts/local/</code></pre><div class="para">
+ If creating the <code class="filename">/usr/share/fonts/local/</code> directory is necessary, it must be added to the <code class="command">xfs</code> path using the following command as root:
+ </div><pre class="screen">~]# <code class="command">chkfontpath --add /usr/share/fonts/local/</code></pre></li><li class="listitem"><div class="para">
+ Copy the new font file into the <code class="filename">/usr/share/fonts/local/</code> directory
+ </div></li><li class="listitem"><div class="para">
+ Update the font information by issuing the following command as root:
+ </div><pre class="screen">~]# <code class="command">ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale</code></pre></li><li class="listitem"><div class="para">
+ Reload the <code class="command">xfs</code> font server configuration file by issuing the following command as root:
+ </div><pre class="screen">~]# <code class="command">service xfs reload</code></pre></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x-fonts.html"><strong>Prev</strong>21.4. Fonts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-x-runlevels.html"><strong>Next</strong>21.5. Runlevels and X</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-runlevels-5.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-runlevels-5.html
new file mode 100644
index 0000000..cbe5d46
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-runlevels-5.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>21.5.2. Runlevel 5</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-x-runlevels.html" title="21.5. Runlevels and X" /><link rel="prev" href="s1-x-runlevels.html" title="21.5. Runlevels and X" /><link rel="next" href="s1-x-additional-resources.html" title="21.6. Additional Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe><
/div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-runlevels.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-x-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="21.5.2. Runlevel 5" id="s2-x-runlevels-5"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-runlevels-5">21.5.2. Runlevel 5</h3></div></div></div><a id="id855708" class="indexterm"></a><a id="id855727" class="indexterm"></a><a id="id947094" class="indexterm"></a><a id="id947112" class="indexterm"></a><a id="id947135" class="indexterm"></a><a id="id947157" class="indexterm"></a><a id="id947180" class="index
term"></a><a id="id947198" class="indexterm"></a><a id="id947221" class="indexterm"></a><div class="para">
+ When the system boots into runlevel 5, a special X client application called a <em class="firstterm">display manager</em> is launched. A user must authenticate using the display manager before any desktop environment or window managers are launched.
+ </div><div class="para">
+ Depending on the desktop environments installed on the system, three different display managers are available to handle user authentication.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">GNOME</code> — The default display manager for Fedora, <code class="command">GNOME</code> allows the user to configure language settings, shutdown, restart or log in to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">KDE</code> — KDE's display manager which allows the user to shutdown, restart or log in to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">xdm</code> — A very basic display manager which only lets the user log in to the system.
+ </div></li></ul></div><div class="para">
+ When booting into runlevel 5, the <code class="command">prefdm</code> script determines the preferred display manager by referencing the <code class="filename">/etc/sysconfig/desktop</code> file. A list of options for this file is available in this file:
+ </div><pre class="screen"><code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code><version-number></code></em>/sysconfig.txt</code></pre><div class="para">
+ where <em class="replaceable"><code><version-number></code></em> is the version number of the <code class="filename">initscripts</code> package.
+ </div><div class="para">
+ Each of the display managers reference the <code class="filename">/etc/X11/xdm/Xsetup_0</code> file to set up the login screen. Once the user logs into the system, the <code class="filename">/etc/X11/xdm/GiveConsole</code> script runs to assign ownership of the console to the user. Then, the <code class="filename">/etc/X11/xdm/Xsession</code> script runs to accomplish many of the tasks normally performed by the <code class="command">xinitrc</code> script when starting X from runlevel 3, including setting system and user resources, as well as running the scripts in the <code class="filename">/etc/X11/xinit/xinitrc.d/</code> directory.
+ </div><div class="para">
+ Users can specify which desktop environment they want to utilize when they authenticate using the <code class="command">GNOME</code> or <code class="command">KDE</code> display managers by selecting it from the <span class="guimenu"><strong>Sessions</strong></span> menu item (accessed by selecting System (on the panel) > <span class="guimenuitem"><strong>Preferences</strong></span> > <span class="guimenuitem"><strong>More Preferences</strong></span> > <span class="guimenuitem"><strong>Sessions</strong></span>). If the desktop environment is not specified in the display manager, the <code class="filename">/etc/X11/xdm/Xsession</code> script checks the <code class="filename">.xsession</code> and <code class="filename">.Xclients</code> files in the user's home directory to decide which desktop environment to load. As a last resort, the <code class="filename">/etc/X11/xinit/Xclients</code> file is used to select a desktop environment or window manager to use in the
same way as runlevel 3.
+ </div><div class="para">
+ When the user finishes an X session on the default display (<code class="computeroutput">:0</code>) and logs out, the <code class="filename">/etc/X11/xdm/TakeConsole</code> script runs and reassigns ownership of the console to the root user. The original display manager, which continues running after the user logged in, takes control by spawning a new display manager. This restarts the X server, displays a new login window, and starts the entire process over again.
+ </div><div class="para">
+ The user is returned to the display manager after logging out of X from runlevel 5.
+ </div><div class="para">
+ For more information on how display managers control user authentication, refer to the <code class="filename">/usr/share/doc/gdm-<em class="replaceable"><code><version-number></code></em>/README</code> (where <em class="replaceable"><code><version-number></code></em> is the version number for the <code class="filename">gdm</code> package installed) and the <code class="command">xdm</code> man page.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x-runlevels.html"><strong>Prev</strong>21.5. Runlevels and X</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-x-additional-resources.html"><strong>Next</strong>21.6. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-useful-websites.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-useful-websites.html
new file mode 100644
index 0000000..d68653b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s2-x-useful-websites.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-x-additional-resources.html" title="21.6. Additional Resources" /><link rel="prev" href="s1-x-additional-resources.html" title="21.6. Additional Resources" /><link rel="next" href="ers_and_Groups.html" title="Chapter 22. Users and Groups" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or ena
ble iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-x-additional-resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ers_and_Groups.html"><strong>Next</strong></a></li></ul><div class="section" title="21.6.2. Useful Websites" id="s2-x-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-x-useful-websites">21.6.2. Useful Websites</h3></div></div></div><a id="id853724" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.X.org/">http://www.X.org/</a> — Home page of the X.Org Foundation, which produces the X11R7.1 release of the X Window System. The X11R7.1 release is bundled with Fedora to control the necessary hardware and provide a GUI environment.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://dri.sourceforge.net/">http://dri.sourceforge.net/</a> — Home page of the DRI (Direct Rendering Infrastructure) project. The DRI is the core hardware 3D acceleration component of X.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.gnome.org">http://www.gnome.org/</a> — Home of the GNOME project.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.kde.org">http://www.kde.org/</a> — Home of the KDE desktop environment.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-x-additional-resources.html"><strong>Prev</strong>21.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="ers_and_Groups.html"><strong>Next</strong>Chapter 22. Users and Groups</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s3-bind-zone-rr.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s3-bind-zone-rr.html
new file mode 100644
index 0000000..444b1ca
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s3-bind-zone-rr.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>7.3.2. Zone File 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-zone.html" title="7.3. Zone Files" /><link rel="prev" href="s1-bind-zone.html" title="7.3. Zone Files" /><link rel="next" href="s2-bind-zone-examples.html" title="7.3.3. Example Zone File" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p
id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-examples.html"><strong>Next</strong></a></li></ul><div class="section" title="7.3.2. Zone File 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">7.3.2. Zone File Resource Records</h3></div></div></div><a id="id596784" class="indexterm"></a><div class="para">
+ The primary component of a zone file is its resource records.
+ </div><div class="para">
+ There are many types of zone file resource records. The following are used most frequently:
+ </div><div class="variablelist"><dl><dt><span class="term"> <code class="command">A</code> </span></dt><dd><div class="para">
+ This refers to the Address record, which specifies an IP address to assign to a name, as in this example:
+ </div><pre class="screen">
+ <em class="replaceable"><code><host></code></em> IN A <em class="replaceable"><code><IP-address></code></em>
+</pre><div class="para">
+ If the <em class="replaceable"><code><host></code></em> value is omitted, then an <code class="command">A</code> record points to a default IP address for the top of the namespace. This system is the target for all non-FQDN requests.
+ </div><div class="para">
+ Consider the following <code class="command">A</code> record examples for the <code class="command">example.com</code> zone file:
+ </div><pre class="screen">
+server1 IN A 10.0.1.3
+ IN A 10.0.1.5
+</pre><div class="para">
+ Requests for <code class="command">example.com</code> are pointed to 10.0.1.3 or 10.0.1.5.
+ </div></dd><dt><span class="term"> <code class="command">CNAME</code> </span></dt><dd><div class="para">
+ This refers to the Canonical Name record, which maps one name to another. This type of record can also be referred to as an <em class="firstterm">alias record</em>.
+ </div><div class="para">
+ The next example tells <code class="command">named</code> that any requests sent to the <em class="replaceable"><code><alias-name></code></em> should point to the host, <em class="replaceable"><code><real-name></code></em>. <code class="command">CNAME</code> records are most commonly used to point to services that use a common naming scheme, such as <code class="command">www</code> for Web servers.
+ </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">
+ In the following example, an <code class="command">A</code> record binds a hostname to an IP address, while a <code class="command">CNAME</code> record points the commonly used <code class="command">www</code> hostname to it.
+ </div><pre class="screen">server1 IN A 10.0.1.5
+www IN CNAME server1</pre></dd><dt><span class="term"> <code class="command">MX</code> </span></dt><dd><div class="para">
+ This refers to the Mhail eXchange record, which tells where mail sent to a particular namespace controlled by this zone should go.
+ </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">
+ Here, 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">
+ The <em class="replaceable"><code><email-server-name></code></em> may be a hostname or FQDN.
+ </div><pre class="screen">IN MX 10 mail.example.com.
+IN MX 20 mail2.example.com.</pre><div class="para">
+ In this example, the first <code class="command">mail.example.com</code> email server is preferred to the <code class="command">mail2.example.com</code> email server when receiving email destined for the <code class="command">example.com</code> domain.
+ </div></dd><dt><span class="term"> <code class="command">NS</code> </span></dt><dd><div class="para">
+ This refers to the NameServer record, which announces the authoritative nameservers for a particular zone.
+ </div><div class="para">
+ The following illustrates the layout of an <code class="command">NS</code> record:
+ </div><pre class="screen"> IN NS <em class="replaceable"><code><nameserver-name></code></em>
+</pre><div class="para">
+ Here, <em class="replaceable"><code><nameserver-name></code></em> should be an FQDN.
+ </div><div class="para">
+ Next, two nameservers are listed as authoritative for the domain. It is not important whether these nameservers are slaves or if one is a master; they are both still considered authoritative.
+ </div><pre class="screen">IN NS dns1.example.com.
+IN NS dns2.example.com.</pre></dd><dt><span class="term"> <code class="command">PTR</code> </span></dt><dd><div class="para">
+ This refers to the PoinTeR record, which is designed to point to another part of the namespace.
+ </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.html" title="7.3.4. Reverse Name Resolution Zone Files">Section 7.3.4, “Reverse Name Resolution Zone Files”</a> for more examples of <code class="command">PTR</code> records in use.
+ </div></dd><dt><span class="term"> <code class="command">SOA</code> </span></dt><dd><div class="para">
+ This refers to the Start Of Authority resource record, which proclaims important authoritative information about a namespace to the nameserver.
+ </div><div class="para">
+ Located after the directives, an <code class="command">SOA</code> resource record is the first resource record in a zone file.
+ </div><div class="para">
+ The following shows the basic structure of an <code class="command">SOA</code> resource record:
+ </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 <code class="command">@</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. The hostname of the primary nameserver that is authoritative for this domain is the <em class="replaceable"><code><primary-name-server></code></em> directive, and the email of the person to contact about this namespace is the <em class="replaceable"><code><hostmaster-email></code></em> directive.
+ </div><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 <code class="command">named</code> to reload the zone. The <em class="replaceable"><code><time-to-refresh></code></em> directive is the numerical value slave servers use to determine how long to wait before asking the master nameserver if any changes have been made to the zone. The <em class="replaceable"><code><serial-number></code></em> directive is a numerical value used by the slave servers to determine if it is using outdated zone data and should therefore refresh it.
+ </div><div class="para">
+ The <em class="replaceable"><code><time-to-retry></code></em> directive is a numerical value used by slave servers to determine the length of time to wait before issuing a refresh request in the event that the master nameserver is not answering. If the master 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 slave servers stop responding as an authority for requests concerning that namespace.
+ </div><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. However, in BIND 9, the <em class="replaceable"><code><minimum-TTL></code></em> directive defines how long negative answers are cached for. Caching of negative answers can be set to a maximum of 3 hours (<code class="option">3H</code>).
+ </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="command">M</code>), hours (<code class="command">H</code>), days (<code class="command">D</code>), and weeks (<code class="command">W</code>). The table in <a class="xref" href="s3-bind-zone-rr.html#tb-bind-seconds" title="Table 7.1. Seconds compared to other time units">Table 7.1, “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 7.1. Seconds compared to other time units" id="tb-bind-seconds"><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>
+ <code class="command">60</code>
+ </td><td>
+ <code class="command">1M</code>
+ </td></tr><tr><td>
+ <code class="command">1800</code>
+ </td><td>
+ <code class="command">30M</code>
+ </td></tr><tr><td>
+ <code class="command">3600</code>
+ </td><td>
+ <code class="command">1H</code>
+ </td></tr><tr><td>
+ <code class="command">10800</code>
+ </td><td>
+ <code class="command">3H</code>
+ </td></tr><tr><td>
+ <code class="command">21600</code>
+ </td><td>
+ <code class="command">6H</code>
+ </td></tr><tr><td>
+ <code class="command">43200</code>
+ </td><td>
+ <code class="command">12H</code>
+ </td></tr><tr><td>
+ <code class="command">86400</code>
+ </td><td>
+ <code class="command">1D</code>
+ </td></tr><tr><td>
+ <code class="command">259200</code>
+ </td><td>
+ <code class="command">3D</code>
+ </td></tr><tr><td>
+ <code class="command">604800</code>
+ </td><td>
+ <code class="command">1W</code>
+ </td></tr><tr><td>
+ <code class="command">31536000</code>
+ </td><td>
+ <code class="command">365D</code>
+ </td></tr></tbody></table></div><h6>Table 7.1. Seconds compared to other time units</h6></div><br class="table-break" /><div class="para">
+ The following example illustrates the form an <code class="command">SOA</code> resource record might take when it is populated with real values.
+ </div><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></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-zone.html"><strong>Prev</strong>7.3. 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-examples.html"><strong>Next</strong>7.3.3. Example Zone File</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s3-httpd-v2-mig.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s3-httpd-v2-mig.html
new file mode 100644
index 0000000..9c4a4f9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/s3-httpd-v2-mig.html
@@ -0,0 +1,343 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-httpd-mig.html" title="11.2. Migrating Apache HTTP Server Configuration Files" /><link rel="prev" href="s1-httpd-mig.html" title="11.2. Migrating Apache HTTP Server Configuration Files" /><link rel="next" href="s1-apache-startstop.html" title="11.3. Starting and Stopping httpd" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" s
rc="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-httpd-mig.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-startstop.html"><strong>Next</strong></a></li></ul><div class="section" title="11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0" id="s3-httpd-v2-mig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s3-httpd-v2-mig">11.2.2. Migrating Apache HTTP Server 1.3 Configuration Files to 2.0</h3></div></div></div><a id="id878869" class="indexterm"></a><a id="id878887" class="
indexterm"></a><a id="id878905" class="indexterm"></a><div class="para">
+ This section details migrating an Apache HTTP Server 1.3 configuration file to be utilized by Apache HTTP Server 2.0.
+ </div><div class="para">
+ If the <code class="filename">/etc/httpd/conf/httpd.conf</code> file is a modified version of the newly installed default and a saved a copy of the original configuration file is available, it may be easiest to invoke the <code class="command">diff</code> command, as in the following example (logged in as root):
+ </div><pre class="screen">
+<code class="command">diff -u httpd.conf.orig httpd.conf | less</code>
+</pre><div class="para">
+ This command highlights any modifications made. If a copy of the original file is not available, extract it from an RPM package using the <code class="command">rpm2cpio</code> and <code class="command">cpio</code> commands, as in the following example:
+ </div><pre class="screen">
+<code class="command">rpm2cpio apache-<em class="replaceable"><code><version-number></code></em>.i386.rpm | cpio -i --make</code>
+</pre><div class="para">
+ In the above command, replace <em class="replaceable"><code><version-number></code></em> with the version number for the <code class="filename">apache</code> package.
+ </div><div class="para">
+ Finally, it is useful to know that the Apache HTTP Server has a testing mode to check for configuration errors. To use access it, type the following command:
+ </div><pre class="screen">
+<code class="command">apachectl configtest</code>
+</pre><div class="section" title="11.2.2.1. Global Environment Configuration" id="s2-httpd-mig-global"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-httpd-mig-global">11.2.2.1. Global Environment Configuration</h4></div></div></div><div class="para">
+ The global environment section of the configuration file contains directives which affect the overall operation of the Apache HTTP Server, such as the number of concurrent requests it can handle and the locations of the various files. This section requires a large number of changes and should be based on the Apache HTTP Server 2.0 configuration file, while migrating the old settings into it.
+ </div><div class="section" title="11.2.2.1.1. Interface and Port Binding" id="s3-httpd-v2-mig-port"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-port">11.2.2.1.1. Interface and Port Binding</h5></div></div></div><a id="id844408" class="indexterm"></a><div class="para">
+ The <code class="command">BindAddress</code> and <code class="command">Port</code> directives no longer exist; their functionality is now provided by a more flexible <code class="command">Listen</code> directive.
+ </div><div class="para">
+ If <code class="command">Port 80</code> was set in the 1.3 version configuration file, change it to <code class="command">Listen 80</code> in the 2.0 configuration file. If <code class="command">Port</code> was set to some value <span class="emphasis"><em>other than 80</em></span>, then append the port number to the contents of the <code class="command">ServerName</code> directive.
+ </div><div class="para">
+ For example, the following is a sample Apache HTTP Server 1.3 directive:
+ </div><pre class="screen">
+<code class="command">Port 123 ServerName www.example.com</code>
+</pre><div class="para">
+ To migrate this setting to Apache HTTP Server 2.0, use the following structure:
+ </div><pre class="screen">
+<code class="command"><strong class="userinput"><code>Listen</code></strong> 123 ServerName www.example.com:<strong class="userinput"><code>123</code></strong> </code>
+</pre><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mpm_common.html#listen"> <code class="command">http://httpd.apache.org/docs-2.0/mod/mpm_common.html#listen</code> </a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/core.html#servername"> <code class="command">http://httpd.apache.org/docs-2.0/mod/core.html#servername</code> </a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.1.2. Server-Pool Size Regulation" id="s3-httpd-v2-mig-pool"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-pool">11.2.2.1.2. Server-Pool Size Regulation</h5></div></div></div><a id="id720033" class="indexterm"></a><a id="id720055" class="indexterm"></a><a id="id720076" class="indexterm"></a><a id="id720097" class="indexterm"></a><div class="para">
+ When the Apache HTTP Server accepts requests, it dispatches child processes or threads to handle them. This group of child processes or threads is known as a <em class="firstterm">server-pool</em>. Under Apache HTTP Server 2.0, the responsibility for creating and maintaining these server-pools has been abstracted to a group of modules called <em class="firstterm">Multi-Processing Modules</em> (<em class="firstterm">MPMs</em>). Unlike other modules, only one module from the MPM group can be loaded by the Apache HTTP Server. There are three MPM modules that ship with 2.0: <code class="command">prefork</code>, <code class="command">worker</code>, and <code class="command">perchild</code>. Currently only the <code class="command">prefork</code> and <code class="command">worker</code> MPMs are available, although the <code class="command">perchild</code> MPM may be available at a later date.
+ </div><div class="para">
+ The original Apache HTTP Server 1.3 behavior has been moved into the <code class="command">prefork</code> MPM. The <code class="command">prefork</code> MPM accepts the same directives as Apache HTTP Server 1.3, so the following directives may be migrated directly:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">StartServers</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MinSpareServers</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MaxSpareServers</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MaxClients</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MaxRequestsPerChild</code>
+ </div></li></ul></div><div class="para">
+ The <code class="command">worker</code> MPM implements a multi-process, multi-threaded server providing greater scalability. When using this MPM, requests are handled by threads, conserving system resources and allowing large numbers of requests to be served efficiently. Although some of the directives accepted by the <code class="command">worker</code> MPM are the same as those accepted by the <code class="command">prefork</code> MPM, the values for those directives should not be transfered directly from an Apache HTTP Server 1.3 installation. It is best to instead use the default values as a guide, then experiment to determine what values work best.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ To use the <code class="command">worker</code> MPM, create the file <code class="filename">/etc/sysconfig/httpd</code> and add the following directive:
+ </div><pre class="screen">
+<code class="command">HTTPD=/usr/sbin/httpd.worker</code>
+</pre></div><div class="para">
+ For more on the topic of MPMs, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mpm.html">http://httpd.apache.org/docs-2.0/mpm.html</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support" id="s3-httpd-v2-mig-dso"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-dso">11.2.2.1.3. Dynamic Shared Object (DSO) Support</h5></div></div></div><a id="id909757" class="indexterm"></a><div class="para">
+ There are many changes required here, and it is highly recommended that anyone trying to modify an Apache HTTP Server 1.3 configuration to suit version 2.0 (as opposed to migrating the changes into the version 2.0 configuration) copy this section from the stock Apache HTTP Server 2.0 configuration file.
+ </div><div class="para">
+ Those who do not want to copy the section from the stock Apache HTTP Server 2.0 configuration should note the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="command">AddModule</code> and <code class="command">ClearModuleList</code> directives no longer exist. These directives where used to ensure that modules could be enabled in the correct order. The Apache HTTP Server 2.0 API allows modules to specify their ordering, eliminating the need for these two directives.
+ </div></li><li class="listitem"><div class="para">
+ The order of the <code class="command">LoadModule</code> lines are no longer relevant in most cases.
+ </div></li><li class="listitem"><div class="para">
+ Many modules have been added, removed, renamed, split up, or incorporated into others.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">LoadModule</code> lines for modules packaged in their own RPMs (<code class="filename">mod_ssl</code>, <code class="filename">php</code>, <code class="filename">mod_perl</code>, and the like) are no longer necessary as they can be found in their relevant files within the <code class="filename">/etc/httpd/conf.d/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ The various <code class="command">HAVE_XXX</code> definitions are no longer defined.
+ </div></li></ul></div><div class="important"><h2>Important</h2><div class="para">
+ If modifying the original file, note that it is of paramount importance that the <code class="filename">httpd.conf</code> contains the following directive:
+ </div><pre class="screen">
+<code class="command">Include conf.d/*.conf</code>
+</pre><div class="para">
+ Omission of this directive results in the failure of all modules packaged in their own RPMs (such as <code class="filename">mod_perl</code>, <code class="filename">php</code>, and <code class="filename">mod_ssl</code>).
+ </div></div></div><div class="section" title="11.2.2.1.4. Other Global Environment Changes" id="s3-httpd-v2-mig-other"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-other">11.2.2.1.4. Other Global Environment Changes</h5></div></div></div><a id="id701504" class="indexterm"></a><div class="para">
+ The following directives have been removed from Apache HTTP Server 2.0's configuration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em> <code class="command">ServerType</code> </em></span> — The Apache HTTP Server can only be run as <code class="command">ServerType standalone</code> making this directive irrelevant.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em> <code class="command">AccessConfig</code> </em></span> and <span class="emphasis"><em><code class="command">ResourceConfig</code> </em></span> — These directives have been removed as they mirror the functionality of the <code class="command">Include</code> directive. If the <code class="command">AccessConfig</code> and <code class="command">ResourceConfig</code> directives are set, replace them with <code class="command">Include</code> directives.
+ </div><div class="para">
+ To ensure that the files are read in the order implied by the older directives, the <code class="command">Include</code> directives should be placed at the end of the <code class="filename">httpd.conf</code>, with the one corresponding to <code class="command">ResourceConfig</code> preceding the one corresponding to <code class="command">AccessConfig</code>. If using the default values, include them explicitly as <code class="filename">conf/srm.conf</code> and <code class="filename">conf/access.conf</code> files.
+ </div></li></ul></div></div></div><div class="section" title="11.2.2.2. Main Server Configuration" id="s2-httpd-v2-mig-main"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-httpd-v2-mig-main">11.2.2.2. Main Server Configuration</h4></div></div></div><div class="para">
+ The main server configuration section of the configuration file sets up the main server, which responds to any requests that are not handled by a virtual host defined within a <code class="command"><VirtualHost></code> container. Values here also provide defaults for any <code class="command"><VirtualHost></code> containers defined.
+ </div><div class="para">
+ The directives used in this section have changed little between Apache HTTP Server 1.3 and version 2.0. If the main server configuration is heavily customized, it may be easier to modify the existing configuration file to suit Apache HTTP Server 2.0. Users with only lightly customized main server sections should migrate their changes into the default 2.0 configuration.
+ </div><div class="section" title="11.2.2.2.1. UserDir Mapping" id="s3-httpd-mig-main-map"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-mig-main-map">11.2.2.2.1. <code class="command">UserDir</code> Mapping</h5></div></div></div><a id="id961475" class="indexterm"></a><div class="para">
+ The <code class="command">UserDir</code> directive is used to enable URLs such as <code class="filename">http://example.com/~bob/</code> to map to a subdirectory within the home directory of the user <code class="command">bob</code>, such as <code class="filename">/home/bob/public_html/</code>. A side-effect of this feature allows a potential attacker to determine whether a given username is present on the system. For this reason, the default configuration for Apache HTTP Server 2.0 disables this directive.
+ </div><div class="para">
+ To enable <code class="command">UserDir</code> mapping, change the directive in <code class="filename">httpd.conf</code> from:
+ </div><pre class="screen">
+<code class="command">UserDir disable</code>
+</pre><div class="para">
+ to the following:
+ </div><pre class="screen">
+<code class="command">UserDir <strong class="userinput"><code>public_html</code></strong> </code>
+</pre><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_userdir.html#userdir">http://httpd.apache.org/docs-2.0/mod/mod_userdir.html#userdir</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.2.2. Logging" id="s3-httpd-mig-main-log"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-mig-main-log">11.2.2.2.2. Logging</h5></div></div></div><a id="id961587" class="indexterm"></a><div class="para">
+ The following logging directives have been removed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">AgentLog</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">RefererLog</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">RefererIgnore</code>
+ </div></li></ul></div><div class="para">
+ However, agent and referrer logs are still available using the <code class="command">CustomLog</code> and <code class="command">LogFormat</code> directives.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#customlog">http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#customlog</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#logformat">http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#logformat</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.2.3. Directory Indexing" id="s3-httpd-mig-main-dirindex"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-mig-main-dirindex">11.2.2.2.3. Directory Indexing</h5></div></div></div><a id="id648581" class="indexterm"></a><div class="para">
+ The deprecated <code class="command">FancyIndexing</code> directive has now been removed. The same functionality is available through the <code class="command">FancyIndexing</code> <span class="emphasis"><em>option</em></span> within the <code class="command">IndexOptions</code> directive.
+ </div><div class="para">
+ The <code class="command">VersionSort</code> option to the <code class="command">IndexOptions</code> directive causes files containing version numbers to be sorted in a more natural way. For example, <code class="filename">httpd-2.0.6.tar</code> appears before <code class="filename">httpd-2.0.36.tar</code> in a directory index page.
+ </div><div class="para">
+ The defaults for the <code class="command">ReadmeName</code> and <code class="command">HeaderName</code> directives have changed from <code class="filename">README</code> and <code class="filename">HEADER</code> to <code class="filename">README.html</code> and <code class="filename">HEADER.html</code>.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#indexoptions">http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#indexoptions</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#readmename">http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#readmename</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#headername">http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#headername</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.2.4. Content Negotiation" id="s3-httpd-mig-main-cont"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-mig-main-cont">11.2.2.2.4. Content Negotiation</h5></div></div></div><a id="id893648" class="indexterm"></a><div class="para">
+ The <code class="command">CacheNegotiatedDocs</code> directive now takes the argument <code class="option">on</code> or <code class="option">off</code>. Existing instances of <code class="command">CacheNegotiatedDocs</code> should be replaced with <code class="command">CacheNegotiatedDocs on</code>.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_negotiation.html#cachenegotiateddocs">http://httpd.apache.org/docs-2.0/mod/mod_negotiation.html#cachenegotiateddocs</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.2.5. Error Documents" id="s3-httpd-mig-main-error"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-mig-main-error">11.2.2.2.5. Error Documents</h5></div></div></div><a id="id640275" class="indexterm"></a><div class="para">
+ To use a hard-coded message with the <code class="command">ErrorDocument</code> directive, the message should be enclosed in a pair of double quotation marks <code class="command">"</code>, rather than just preceded by a double quotation mark as required in Apache HTTP Server 1.3.
+ </div><div class="para">
+ For example, the following is a sample Apache HTTP Server 1.3 directive:
+ </div><pre class="screen">
+<code class="command">ErrorDocument 404 "The document was not found</code>
+</pre><div class="para">
+ To migrate an <code class="command">ErrorDocument</code> setting to Apache HTTP Server 2.0, use the following structure:
+ </div><pre class="screen">
+<code class="command">ErrorDocument 404 "The document was not found"</code>
+</pre><div class="para">
+ Note the trailing double quote in the previous <code class="command">ErrorDocument</code> directive example.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/core.html#errordocument">http://httpd.apache.org/docs-2.0/mod/core.html#errordocument</a>
+ </div></li></ul></div></div></div><div class="section" title="11.2.2.3. Virtual Host Configuration" id="s2-httpd-v2-mig-virtual"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-httpd-v2-mig-virtual">11.2.2.3. Virtual Host Configuration</h4></div></div></div><a id="id640377" class="indexterm"></a><div class="para">
+ The contents of all <code class="command"><VirtualHost></code> containers should be migrated in the same way as the main server section as described in <a class="xref" href="s3-httpd-v2-mig.html#s2-httpd-v2-mig-main" title="11.2.2.2. Main Server Configuration">Section 11.2.2.2, “Main Server Configuration”</a>.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ Note that SSL/TLS virtual host configuration has been moved out of the main server configuration file and into <code class="filename">/etc/httpd/conf.d/ssl.conf</code>.
+ </div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/vhosts/">http://httpd.apache.org/docs-2.0/vhosts/</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4. Modules and Apache HTTP Server 2.0" id="s2-httpd-v2-mig-mod"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-httpd-v2-mig-mod">11.2.2.4. Modules and Apache HTTP Server 2.0</h4></div></div></div><a id="id954792" class="indexterm"></a><div class="para">
+ In Apache HTTP Server 2.0, the module system has been changed to allow modules to be chained together or combined in new and interesting ways. <em class="firstterm">Common Gateway Interface</em> (<em class="firstterm">CGI</em>) scripts, for example, can generate server-parsed HTML documents which can then be processed by <code class="filename">mod_include</code>. This opens up a tremendous number of possibilities with regards to how modules can be combined to achieve a specific goal.
+ </div><div class="para">
+ The way this works is that each request is served by exactly one <em class="firstterm">handler</em> module followed by zero or more <em class="firstterm">filter</em> modules.
+ </div><div class="para">
+ Under Apache HTTP Server 1.3, for example, a Perl script would be handled in its entirety by the Perl module (<code class="filename">mod_perl</code>). Under Apache HTTP Server 2.0, the request is initially <span class="emphasis"><em>handled</em></span> by the core module — which serves static files — and is then <span class="emphasis"><em>filtered</em></span> by <code class="filename">mod_perl</code>.
+ </div><div class="para">
+ Exactly how to use this, and all other new features of Apache HTTP Server 2.0, is beyond the scope of this document; however, the change has ramifications if the <code class="command">PATH_INFO</code> directive is used for a document which is handled by a module that is now implemented as a filter, as each contains trailing path information after the true file name. The core module, which initially handles the request, does not by default understand <code class="command">PATH_INFO</code> and returns <code class="computeroutput">404 Not Found</code> errors for requests that contain such information. As an alternative, use the <code class="command">AcceptPathInfo</code> directive to coerce the core module into accepting requests with <code class="command">PATH_INFO</code>.
+ </div><div class="para">
+ The following is an example of this directive:
+ </div><pre class="screen">
+<code class="command">AcceptPathInfo on</code>
+</pre><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/core.html#acceptpathinfo">http://httpd.apache.org/docs-2.0/mod/core.html#acceptpathinfo</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/handler.html">http://httpd.apache.org/docs-2.0/handler.html</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/filter.html">http://httpd.apache.org/docs-2.0/filter.html</a>
+ </div></li></ul></div><div class="section" title="11.2.2.4.1. The suexec Module" id="s3-httpd-v2-mig-mod-suexec"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-suexec">11.2.2.4.1. The <code class="filename">suexec</code> Module</h5></div></div></div><a id="id1027444" class="indexterm"></a><a id="id1027466" class="indexterm"></a><a id="id1027484" class="indexterm"></a><div class="para">
+ In Apache HTTP Server 2.0, the <code class="filename">mod_suexec</code> module uses the <code class="filename">SuexecUserGroup</code> directive, rather than the <code class="filename">User</code> and <code class="filename">Group</code> directives, which is used for configuring virtual hosts. The <code class="filename">User</code> and <code class="filename">Group</code> directives can still be used in general, but are deprecated for configuring virtual hosts.
+ </div><div class="para">
+ For example, the following is a sample Apache HTTP Server 1.3 directive:
+ </div><pre class="screen">
+<code class="command"><VirtualHost vhost.example.com:80> User someone Group somegroup </VirtualHost></code>
+</pre><div class="para">
+ To migrate this setting to Apache HTTP Server 2.0, use the following structure:
+ </div><pre class="screen">
+<code class="command"><VirtualHost vhost.example.com:80> SuexecUserGroup someone somegroup </VirtualHost></code>
+</pre></div><div class="section" title="11.2.2.4.2. The mod_ssl Module" id="s3-httpd-v2-mig-mod-ssl"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-ssl">11.2.2.4.2. The <code class="filename">mod_ssl</code> Module</h5></div></div></div><a id="id1027570" class="indexterm"></a><div class="para">
+ The configuration for <code class="filename">mod_ssl</code> has been moved from the <code class="filename">httpd.conf</code> file into the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file. For this file to be loaded, and for <code class="filename">mod_ssl</code> to work, the statement <code class="command">Include conf.d/*.conf</code> must be in the <code class="filename">httpd.conf</code> file as described in <a class="xref" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-dso" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support">Section 11.2.2.1.3, “Dynamic Shared Object (DSO) Support”</a>.
+ </div><div class="para">
+ <code class="command">ServerName</code> directives in SSL virtual hosts must explicitly specify the port number.
+ </div><div class="para">
+ For example, the following is a sample Apache HTTP Server 1.3 directive:
+ </div><pre class="screen">
+<code class="command"><VirtualHost _default_:443> # General setup for the virtual host ServerName ssl.example.name ... </VirtualHost></code>
+</pre><div class="para">
+ To migrate this setting to Apache HTTP Server 2.0, use the following structure:
+ </div><pre class="screen">
+<code class="command"><VirtualHost _default_:443> # General setup for the virtual host ServerName ssl.host.name<strong class="userinput"><code>:443</code></strong> ... </VirtualHost></code>
+</pre><div class="para">
+ It is also important to note that both the <code class="command">SSLLog</code> and <code class="command">SSLLogLevel</code> directives have been removed. The <code class="filename">mod_ssl</code> module now obeys the <code class="command">ErrorLog</code> and <code class="command">LogLevel</code> directives. Refer to <a class="xref" href="s1-apache-config.html#s2-apache-errorlog" title="ErrorLog">ErrorLog</a> and <a class="xref" href="s1-apache-config.html#s2-apache-loglevel" title="LogLevel">LogLevel</a> for more information about these directives.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_ssl.html">http://httpd.apache.org/docs-2.0/mod/mod_ssl.html</a>
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/vhosts/">http://httpd.apache.org/docs-2.0/vhosts/</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4.3. The mod_proxy Module" id="s3-httpd-v2-mig-mod-proxy"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-proxy">11.2.2.4.3. The <code class="filename">mod_proxy</code> Module</h5></div></div></div><a id="id1012204" class="indexterm"></a><div class="para">
+ Proxy access control statements are now placed inside a <code class="command"><Proxy></code> block rather than a <code class="command"><Directory proxy:></code>.
+ </div><div class="para">
+ The caching functionality of the old <code class="filename">mod_proxy</code> has been split out into the following three modules:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">mod_cache</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">mod_disk_cache</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">mod_mem_cache</code>
+ </div></li></ul></div><div class="para">
+ These generally use directives similar to the older versions of the <code class="filename">mod_proxy</code> module, but it is advisable to verify each directive before migrating any cache settings.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_proxy.html">http://httpd.apache.org/docs-2.0/mod/mod_proxy.html</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4.4. The mod_include Module" id="s3-httpd-v2-mig-mod-include"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-include">11.2.2.4.4. The <code class="filename">mod_include</code> Module</h5></div></div></div><a id="id1012332" class="indexterm"></a><div class="para">
+ The <code class="filename">mod_include</code> module is now implemented as a filter and is therefore enabled differently. Refer to <a class="xref" href="s3-httpd-v2-mig.html#s2-httpd-v2-mig-mod" title="11.2.2.4. Modules and Apache HTTP Server 2.0">Section 11.2.2.4, “Modules and Apache HTTP Server 2.0”</a> for more about filters.
+ </div><div class="para">
+ For example, the following is a sample Apache HTTP Server 1.3 directive:
+ </div><pre class="screen">
+<code class="command">AddType text/html .shtml AddHandler server-parsed .shtml</code>
+</pre><div class="para">
+ To migrate this setting to Apache HTTP Server 2.0, use the following structure:
+ </div><pre class="screen">
+<code class="command">AddType text/html .shtml <strong class="userinput"><code>AddOutputFilter INCLUDES</code></strong> .shtml</code>
+</pre><div class="para">
+ Note that the <code class="command">Options +Includes</code> directive is still required for the <code class="command"><Directory></code> container or in a <code class="filename">.htaccess</code> file.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_include.html">http://httpd.apache.org/docs-2.0/mod/mod_include.html</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4.5. The mod_auth_dbm and mod_auth_db Modules" id="s3-httpd-v2-mig-mod-dbm"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-dbm">11.2.2.4.5. The <code class="filename">mod_auth_dbm</code> and <code class="filename">mod_auth_db</code> Modules</h5></div></div></div><a id="id999904" class="indexterm"></a><a id="id999926" class="indexterm"></a><div class="para">
+ Apache HTTP Server 1.3 supported two authentication modules, <code class="filename">mod_auth_db</code> and <code class="filename">mod_auth_dbm</code>, which used Berkeley Databases and DBM databases respectively. These modules have been combined into a single module named <code class="filename">mod_auth_dbm</code> in Apache HTTP Server 2.0, which can access several different database formats. To migrate from <code class="filename">mod_auth_db</code>, configuration files should be adjusted by replacing <code class="command">AuthDBUserFile</code> and <code class="command">AuthDBGroupFile</code> with the <code class="filename">mod_auth_dbm</code> equivalents, <code class="command">AuthDBMUserFile</code> and <code class="command">AuthDBMGroupFile</code>. Also, the directive <code class="command">AuthDBMType DB</code> must be added to indicate the type of database file in use.
+ </div><div class="para">
+ The following example shows a sample <code class="filename">mod_auth_db</code> configuration for Apache HTTP Server 1.3:
+ </div><pre class="screen">
+<code class="command"><Location /private/> AuthType Basic AuthName "My Private Files" AuthDBUserFile /var/www/authdb require valid-user </Location></code>
+</pre><div class="para">
+ To migrate this setting to version 2.0 of Apache HTTP Server, use the following structure:
+ </div><pre class="screen">
+<code class="command"><Location /private/> AuthType Basic AuthName "My Private Files" <strong class="userinput"><code>AuthDBMUserFile</code></strong> /var/www/authdb <strong class="userinput"><code>AuthDBMType DB</code></strong> require valid-user </Location></code>
+</pre><div class="para">
+ Note that the <code class="command">AuthDBMUserFile</code> directive can also be used in <code class="filename">.htaccess</code> files.
+ </div><div class="para">
+ The <code class="command">dbmmanage</code> Perl script, used to manipulate username and password databases, has been replaced by <code class="command">htdbm</code> in Apache HTTP Server 2.0. The <code class="command">htdbm</code> program offers equivalent functionality and, like <code class="filename">mod_auth_dbm</code>, can operate a variety of database formats; the <code class="option">-T</code> option can be used on the command line to specify the format to use.
+ </div><div class="para">
+ <a class="xref" href="s3-httpd-v2-mig.html#table-htdbm" title="Table 11.1. Migrating from dbmmanage to htdbm">Table 11.1, “Migrating from <code class="command">dbmmanage</code> to <code class="command">htdbm</code> ”</a> shows how to migrate from a DBM-format database to <code class="command">htdbm</code> format using <code class="command">dbmmanage</code>.
+ </div><div class="table" title="Table 11.1. Migrating from dbmmanage to htdbm" id="table-htdbm"><div class="table-contents"><table summary="Migrating from dbmmanage to htdbm " border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th>
+ Action
+ </th><th>
+ dbmmanage command (1.3)
+ </th><th>
+ Equivalent htdbm command (2.0)
+ </th></tr></thead><tbody><tr><td>
+ Add user to database (using given password)
+ </td><td>
+ <code class="command">dbmmanage authdb add username password</code>
+ </td><td>
+ <code class="command">htdbm -b -TDB authdb username password</code>
+ </td></tr><tr><td>
+ Add user to database (prompts for password)
+ </td><td>
+ <code class="command">dbmmanage authdb adduser username</code>
+ </td><td>
+ <code class="command">htdbm -TDB authdb username</code>
+ </td></tr><tr><td>
+ Remove user from database
+ </td><td>
+ <code class="command">dbmmanage authdb delete username</code>
+ </td><td>
+ <code class="command">htdbm -x -TDB authdb username</code>
+ </td></tr><tr><td>
+ List users in database
+ </td><td>
+ <code class="command">dbmmanage authdb view</code>
+ </td><td>
+ <code class="command">htdbm -l -TDB authdb</code>
+ </td></tr><tr><td>
+ Verify a password
+ </td><td>
+ <code class="command">dbmmanage authdb check username</code>
+ </td><td>
+ <code class="command">htdbm -v -TDB authdb username</code>
+ </td></tr></tbody></table></div><h6>Table 11.1. Migrating from <code class="command">dbmmanage</code> to <code class="command">htdbm</code> </h6></div><br class="table-break" /><div class="para">
+ The <code class="option">-m</code> and <code class="option">-s</code> options work with both <code class="command">dbmmanage</code> and <code class="command">htdbm</code>, enabling the use of the MD5 or SHA1 algorithms for hashing passwords, respectively.
+ </div><div class="para">
+ When creating a new database with <code class="command">htdbm</code>, the <code class="command">-c</code> option must be used.
+ </div><div class="para">
+ For more on this topic, refer to the following documentation on the Apache Software Foundation's website:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://httpd.apache.org/docs-2.0/mod/mod_auth_dbm.html">http://httpd.apache.org/docs-2.0/mod/mod_auth_dbm.html</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4.6. The mod_perl Module" id="s3-httpd-v2-mig-mod-perl"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-perl">11.2.2.4.6. The <code class="filename">mod_perl</code> Module</h5></div></div></div><a id="id900823" class="indexterm"></a><div class="para">
+ The configuration for <code class="filename">mod_perl</code> has been moved from <code class="filename">httpd.conf</code> into the file <code class="filename">/etc/httpd/conf.d/perl.conf</code>. For this file to be loaded, and hence for <code class="filename">mod_perl</code> to work, the statement <code class="command">Include conf.d/*.conf</code> must be included in <code class="filename">httpd.conf</code> as described in <a class="xref" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-dso" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support">Section 11.2.2.1.3, “Dynamic Shared Object (DSO) Support”</a>.
+ </div><div class="para">
+ Occurrences of <code class="command">Apache::</code> in <code class="filename">httpd.conf</code> must be replaced with <code class="command">ModPerl::</code>. Additionally, the manner in which handlers are registered has been changed.
+ </div><div class="para">
+ This is a sample Apache HTTP Server 1.3 <code class="filename">mod_perl</code> configuration:
+ </div><pre class="screen">
+<code class="command"><Directory /var/www/perl> SetHandler perl-script PerlHandler Apache::Registry Options +ExecCGI </Directory></code>
+</pre><div class="para">
+ This is the equivalent <code class="filename">mod_perl</code> for Apache HTTP Server 2.0:
+ </div><pre class="screen">
+<code class="command"><Directory /var/www/perl> SetHandler perl-script <strong class="userinput"><code>PerlResponseHandler ModPerl::Registry</code></strong> Options +ExecCGI </Directory></code>
+</pre><div class="para">
+ Most modules for <code class="filename">mod_perl</code> 1.x should work without modification with <code class="filename">mod_perl</code> 2.x. XS modules require recompilation and may require minor Makefile modifications.
+ </div></div><div class="section" title="11.2.2.4.7. The mod_python Module" id="s3-httpd-v2-mig-mod-python"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-python">11.2.2.4.7. The <code class="filename">mod_python</code> Module</h5></div></div></div><div class="para">
+ Configuration for <code class="filename">mod_python</code> has moved from <code class="filename">httpd.conf</code> to the <code class="filename">/etc/httpd/conf.d/python.conf</code> file. For this file to be loaded, and hence for <code class="filename">mod_python</code> to work, the statement <code class="command">Include conf.d/*.conf</code> must be in <code class="filename">httpd.conf</code> as described in <a class="xref" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-dso" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support">Section 11.2.2.1.3, “Dynamic Shared Object (DSO) Support”</a>.
+ </div></div><div class="section" title="11.2.2.4.8. PHP" id="s3-httpd-v2-mig-mod-php"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-php">11.2.2.4.8. PHP</h5></div></div></div><a id="id851371" class="indexterm"></a><div class="para">
+ The configuration for PHP has been moved from <code class="filename">httpd.conf</code> into the file <code class="filename">/etc/httpd/conf.d/php.conf</code>. For this file to be loaded, the statement <code class="command">Include conf.d/*.conf</code> must be in <code class="filename">httpd.conf</code> as described in <a class="xref" href="s3-httpd-v2-mig.html#s3-httpd-v2-mig-dso" title="11.2.2.1.3. Dynamic Shared Object (DSO) Support">Section 11.2.2.1.3, “Dynamic Shared Object (DSO) Support”</a>.
+ </div><div class="note"><h2>Note</h2><div class="para">
+ Any PHP configuration directives used in Apache HTTP Server 1.3 are now fully compatible, when migrating to Apache HTTP Server 2.0 on Fedora 13.
+ </div></div><div class="para">
+ In PHP version 4.2.0 and later the default set of predefined variables which are available in the global scope has changed. Individual input and server variables are, by default, no longer placed directly into the global scope. This change may cause scripts to break. Revert to the old behavior by setting <code class="command">register_globals</code> to <code class="command">On</code> in the file <code class="filename">/etc/php.ini</code>.
+ </div><div class="para">
+ For more on this topic, refer to the following URL for details concerning the global scope changes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.php.net/release_4_1_0.php">http://www.php.net/release_4_1_0.php</a>
+ </div></li></ul></div></div><div class="section" title="11.2.2.4.9. The mod_authz_ldap Module" id="s3-httpd-v2-mig-mod-ldapz"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-httpd-v2-mig-mod-ldapz">11.2.2.4.9. The <code class="filename">mod_authz_ldap</code> Module</h5></div></div></div><a id="id851483" class="indexterm"></a><div class="para">
+ Fedora ships with the <code class="filename">mod_authz_ldap</code> module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. The <code class="filename">mod_ssl</code> module is required when using the <code class="filename">mod_authz_ldap</code> module.
+ </div><div class="important"><h2>Important</h2><div class="para">
+ The <code class="filename">mod_authz_ldap</code> module does not authenticate a user to an LDAP directory using an encrypted password hash. This functionality is provided by the experimental <code class="filename">mod_auth_ldap</code> module. Refer to the <code class="filename">mod_auth_ldap</code> module documentation online at <a href="http://httpd.apache.org/docs-2.0/mod/mod_auth_ldap.html">http://httpd.apache.org/docs-2.0/mod/mod_auth_ldap.html</a> for details on the status of this module.
+ </div></div><div class="para">
+ The <code class="filename">/etc/httpd/conf.d/authz_ldap.conf</code> file configures the <code class="filename">mod_authz_ldap</code> module.
+ </div><div class="para">
+ Refer to <code class="filename">/usr/share/doc/mod_authz_ldap-<em class="replaceable"><code><version></code></em>/index.html</code> (replacing <em class="replaceable"><code><version></code></em> with the version number of the package) or <a href="http://authzldap.othello.ch/">http://authzldap.othello.ch/</a> for more information on configuring the <code class="filename">mod_authz_ldap</code> third party module.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-httpd-mig.html"><strong>Prev</strong>11.2. Migrating Apache HTTP Server 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-apache-startstop.html"><strong>Next</strong>11.3. Starting and Stopping httpd </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Additional_Resources.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Additional_Resources.html
new file mode 100644
index 0000000..3711280
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Additional_Resources.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p i
d="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id651272" class="indexterm"></a><div class="variablelist"><dl><dt><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/wik
i/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><span class="term"> Managing Software with <span class="application"><strong>Yum</strong></span> — <a href="http://docs.fedoraproject.org/yum/en/index.html">http://docs.fedoraproject.org/yum/en/index.html</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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuration_File_Changes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuration_File_Changes.html
new file mode 100644
index 0000000..c4323e9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuration_File_Changes.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe d
isplay.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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" href="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="id925782" class="indexterm"></a><a id="id926116" class="indexterm"></a><div class="para">
+ Because RPM performs intelligent upgrading of packages with configuration files
+ <a id="id926134" 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.fc13.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.fc13.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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_Connection_Settings.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_Connection_Settings.html
new file mode 100644
index 0000000..9805eba
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_Connection_Settings.html
@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.4. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-Establishing_Routes.html" title="5.3.6. Establishing Routes" /><link rel="next" href="sec-Configuring_Wireless_Security.html" title="5.4.2. Configuring Wireless Security" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifr
ame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_Routes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Wireless_Security.html"><strong>Next</strong></a></li></ul><div class="section" title="5.4. 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.4. Configuring Connection Settings</h2></div></div></div><div class="section" title="5.4.1. Configuring 802.1x Security" id="sec-Configuring_802.1x_Security
"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_802.1x_Security">5.4.1. Configuring 802.1x Security</h3></div></div></div><div class="para">
+ 802.1x security is the name of the IEEE standard for port-based Network Access Control (PNAC). Simply put, 802.1x security is a way of defining a <em class="firstterm">logical network</em> out of a physical one. All clients who want to join the logical network must authenticate with the server (a router, for example) using the correct 802.1x authentication method.
+ </div><div class="para">
+ 802.1x security is most often associated with securing wireless networks (WLANs), but can also be used to prevent intruders with physical access to the network (LAN) from gaining entry. In the past, DHCP servers were configured not to lease IP addresses to unauthorized users, but but for various reasons this practice is both impractical and insecure, and thus is no longer recommended. Instead, 802.1x security is used to ensure a logically-secure network through port-based authentication.
+ </div><div class="para">
+ 802.1x provides a framework for WLAN and LAN access control and serves as an envelope for carrying one of the Extensible Authentication Protocol (EAP) types. An EAP type is a protocol that defines how WLAN security is achieved on the network.
+ </div><div class="para">
+ You can configure 802.1x security for a wired or wireless connection type by opening the <span class="guilabel"><strong>Network Connections</strong></span> window (refer to <a class="xref" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>) and following the applicable procedure:
+ </div><div class="procedure"><h6>Procedure 5.5. For a wired connection...</h6><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Select the <span class="guilabel"><strong>Wired</strong></span> tab.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Either click on <span class="guibutton"><strong>Add</strong></span> to add a new network connection for which you want to configure 802.1x security, or select an existing connection and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Then select the <span class="guilabel"><strong>802.1x Security</strong></span> tab and check the <span class="guilabel"><strong>Use 802.1x security for this connection</strong></span> checkbox to enable settings configuration.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ Proceed to
+ </div></li></ol></div><div class="procedure"><h6>Procedure 5.6. For a wireless connection...</h6><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Select the <span class="guilabel"><strong>Wireless</strong></span> tab.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Either click on <span class="guibutton"><strong>Add</strong></span> to add a new network connection for which you want to configure 802.1x security, or select an existing connection and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Then click the <span class="guilabel"><strong>Security</strong></span> dropdown and choose one of the following security methods: <span class="guimenuitem"><strong>LEAP</strong></span>, <span class="guimenuitem"><strong>Dynamic WEP (802.1x)</strong></span>, or <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span>.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ Refer to for descriptions of which EAP types correspond to your selection in the <span class="guilabel"><strong>Security</strong></span> dropdown.
+ </div></li></ol></div><div class="section" title="5.4.1.1. Configuring TLS (Transport Level Security) Settings" id="sec-Configuring_TLS_Transport_Level_Security_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sec-Configuring_TLS_Transport_Level_Security_Settings">5.4.1.1. Configuring TLS (Transport Level Security) Settings</h4></div></div></div><div class="para">
+ With Transport Level Security, the client and server mutually authenticate using the TLS protocol. The server demonstrates that it holds a digital certificate, the client proves its own identity using its client-side certificate, and key information is exchanged. Once authentication is complete, the TLS tunnel is no longer used. Instead, the client and server use the exchanged keys to encrypt data using AES, TKIP or WEP.
+ </div><div class="para">
+ The fact that certificates must be distributed to all clients who want to authenticate means that the the EAP-TLS authentication method is very strong, but also more complicated to set up. Using TLS security requires the overhead of a public key infrastructure (PKI) to manage certificates. The benefit to TLS security is that a compromised password does not allow access to the (W)LAN: an intruder must also have access to the authenticating client's private key.
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Identity</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>User certificate</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Private key</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Private key password</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div><div class="section" title="5.4.1.2. Configuring Tunneled TLS Settings" id="sec-Configuring_Tunneled_TLS_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sec-Configuring_Tunneled_TLS_Settings">5.4.1.2. Configuring Tunneled TLS Settings</h4></div></div></div><div class="para">
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Anonymous identity</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>PAP</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAP</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>CHAP</strong></span> —
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div><div class="section" title="5.4.1.3. Configuring Protected EAP (PEAP) Settings" id="sec-Configuring_Protected_EAP_PEAP_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sec-Configuring_Protected_EAP_PEAP_Settings">5.4.1.3. Configuring Protected EAP (PEAP) Settings</h4></div></div></div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Anonymous Identity</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>CA certificate</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>PEAP version</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Inner authentication</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>MSCHAPv2</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>MD5</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>GTC</strong></span> —
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_Routes.html"><strong>Prev</strong>5.3.6. Establishing 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="sec-Configuring_Wireless_Security.html"><strong>Next</strong>5.4.2. Configuring Wireless Security</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_IPv4_Settings.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_IPv4_Settings.html
new file mode 100644
index 0000000..f262548
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_IPv4_Settings.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.4.4. Configuring IPv4 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Configuring_Connection_Settings.html" title="5.4. Configuring Connection Settings" /><link rel="prev" href="sec-Configuring_PPP_Point-to-Point_Settings.html" title="5.4.3. Configuring PPP (Point-to-Point) Settings" /><link rel="next" href="sec-Configuring_IPv6_Settings.html" title="5.4.5. Configuring IPv6 Settings" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="to
c" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_PPP_Point-to-Point_Settings.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_IPv6_Settings.html"><strong>Next</strong></a></li></ul><div class="section" title="5.4.4. 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.4.4. Configuring IPv4 Settings</h3></div></div></div><div class="mediaobject" align="center"><img src="images/Net
work_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. If you need to configure IPv6 addresses, refer to ???. If you need to configure static routes, which can be done by clicking on the <span class="guibutton"><strong>Routes</strong></span> button, refer to ???.
+ </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><h4>Setting the Method</h4><div class="variablelist" title="Available IPv4 Methods by Connection Type" id="varlist-Available_IPv4_Methods_by_Connection_Type"><h6>Available IPv4 Methods by Connection Type</h6><div class="para">
+ When you click the <span class="guilabel"><strong>Method</strong></span> dropdown menu, depending on the type of connection you are configuring, you are able to select one of the following IPv4 connection methods. All of the methods are listed here according to which connection type or types they are associated with.
+ </div><dl><dt><span class="term"> <span class="guilabel"><strong>Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span> — Choose this option if the network you are connecting to uses a DHCP server to assign IP addresses. You do not need to fill in the <span class="guilabel"><strong>DHCP client ID</strong></span> field.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (DHCP) addresses only</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Shared to other computers</strong></span> —
+ </div></dd><dt><span class="term">Wired, Wireless and DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> —
+ </div></dd><dt><span class="term">Mobile Broadband Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPP) addresses only</strong></span> —
+ </div></dd><dt><span class="term">VPN Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (VPN) addresses only</strong></span> —
+ </div></dd><dt><span class="term">DSL Connection Methods</span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic (PPPoE) addresses only</strong></span> —
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_PPP_Point-to-Point_Settings.html"><strong>Prev</strong>5.4.3. Configuring PPP (Point-to-Point) 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="sec-Configuring_IPv6_Settings.html"><strong>Next</strong>5.4.5. Configuring IPv6 Settings</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_IPv6_Settings.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_IPv6_Settings.html
new file mode 100644
index 0000000..dd42045
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_IPv6_Settings.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>5.4.5. Configuring IPv6 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Configuring_Connection_Settings.html" title="5.4. Configuring Connection Settings" /><link rel="prev" href="sec-Configuring_IPv4_Settings.html" title="5.4.4. Configuring IPv4 Settings" /><link rel="next" href="sec-NetworkManager_Architecture.html" title="5.5. NetworkManager Architecture" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html
">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_IPv4_Settings.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-NetworkManager_Architecture.html"><strong>Next</strong></a></li></ul><div class="section" title="5.4.5. Configuring IPv6 Settings" id="sec-Configuring_IPv6_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_IPv6_Settings">5.4.5. Configuring IPv6 Settings</h3></div></div></div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Method</strong>
</span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Ignore</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Automatic, addresses only</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Manual</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Link-Local Only</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Shared to other computers</strong></span> —
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Addresses</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>DNS servers</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Search domains</strong></span> —
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_IPv4_Settings.html"><strong>Prev</strong>5.4.4. Configuring IPv4 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="sec-NetworkManager_Architecture.html"><strong>Next</strong>5.5. NetworkManager Architecture</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_New_and_Editing_Existing_Connections.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_New_and_Editing_Existing_Connections.html
new file mode 100644
index 0000000..989c714
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_New_and_Editing_Existing_Connections.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><ifr
ame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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. Configur
ing 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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_PPP_Point-to-Point_Settings.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_PPP_Point-to-Point_Settings.html
new file mode 100644
index 0000000..53b8705
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_PPP_Point-to-Point_Settings.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>5.4.3. Configuring PPP (Point-to-Point) 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Configuring_Connection_Settings.html" title="5.4. Configuring Connection Settings" /><link rel="prev" href="sec-Configuring_Wireless_Security.html" title="5.4.2. Configuring Wireless Security" /><link rel="next" href="sec-Configuring_IPv4_Settings.html" title="5.4.4. Configuring IPv4 Settings" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src
="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_Wireless_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_IPv4_Settings.html"><strong>Next</strong></a></li></ul><div class="section" title="5.4.3. Configuring PPP (Point-to-Point) Settings" id="sec-Configuring_PPP_Point-to-Point_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_PPP_Point-to-Point_Settings">5.4.3. Configuring PPP (Point-to-Point) Settings</h3></div></div></div><div class="para
">
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Configure Methods</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Use point-to-point encryption (MPPE)</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Allow BSD data compression</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Allow Deflate data compression</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Use TCP header compression</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Send PPP echo packets</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Wireless_Security.html"><strong>Prev</strong>5.4.2. Configuring Wireless Security</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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_IPv4_Settings.html"><strong>Next</strong>5.4.4. Configuring IPv4 Settings</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_Wireless_Security.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_Wireless_Security.html
new file mode 100644
index 0000000..c58c87c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_Wireless_Security.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>5.4.2. Configuring Wireless Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Configuring_Connection_Settings.html" title="5.4. Configuring Connection Settings" /><link rel="prev" href="sec-Configuring_Connection_Settings.html" title="5.4. Configuring Connection Settings" /><link rel="next" href="sec-Configuring_PPP_Point-to-Point_Settings.html" title="5.4.3. Configuring PPP (Point-to-Point) Settings" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfr
ame" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_Settings.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_PPP_Point-to-Point_Settings.html"><strong>Next</strong></a></li></ul><div class="section" title="5.4.2. Configuring Wireless Security" id="sec-Configuring_Wireless_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_Wireless_Security">5.4.2. Configuring Wireless Security</h3></div></div></div><div class="variablelist
"><dl><dt><span class="term"> <span class="guilabel"><strong>Security</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>None</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 40/128-bit Key</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WEP 128-bit Passphrase</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>LEAP</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Dynamic WEP (802.1x)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Personal</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>WPA & WPA2 Enterprise</strong></span> —
+ </div></dd><dt><span class="term">Password</span></dt><dd><div class="para">
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Connection_Settings.html"><strong>Prev</strong>5.4. 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="sec-Configuring_PPP_Point-to-Point_Settings.html"><strong>Next</strong>5.4.3. Configuring PPP (Point-to-Point) Settings</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.html
new file mode 100644
index 0000000..6c8b820
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe dis
play.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id719238" class="indexterm"></a><a id="id719250" 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="id1005931" 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><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><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><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><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><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><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><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><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>.
+ </div></dd><dt><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 is therefore <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><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><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><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><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="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><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><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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Connecting_to_a_Network_Automatically.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Connecting_to_a_Network_Automatically.html
new file mode 100644
index 0000000..6bf5234
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Connecting_to_a_Network_Automatically.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"
><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_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 Autom
atically</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"><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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Creating_a_Yum_Repository.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Creating_a_Yum_Repository.html
new file mode 100644
index 0000000..a2c2bb4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Creating_a_Yum_Repository.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it up
grade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id612683" 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"><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></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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_Connections.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_Connections.html
new file mode 100644
index 0000000..05bded0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_Connections.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>5.3. Establishing 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="sec-Establishing_a_Wireless_Connection.html" title="5.3.2. Establishing a Wireless Connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.h
tml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-User_and_System_Connections.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_Wireless_Connection.html"><strong>Next</strong></a></li></ul><div class="section" title="5.3. Establishing Connections" id="sec-Establishing_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Establishing_Connections">5.3. Establishing Connections</h2></div></div></div><div class="section" title="5.3.1. Establishing a Wired (Ethernet) Connection" id="sec-Establis
hing_a_Wired_Ethernet_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_a_Wired_Ethernet_Connection">5.3.1. Establishing a Wired (Ethernet) Connection</h3></div></div></div><div class="para">
+ To establish an Ethernet connection, you need a network interface card (an NIC), a network cable (usually a Cat-5 cable), and a network to connect to (usually the Internet, through a router).
+ </div><div class="para">
+ You can configure a wired connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window and selecting the <span class="guilabel"><strong>Wired</strong></span> tab. For more information on opening the <span class="guilabel"><strong>Network Connections</strong></span> window via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet, or by running a shell command, refer to <a class="xref" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Editing_Wired_Connection_1.png" align="middle" /><div class="caption"><div class="para">
+ Editing the newly-created Wired connection 1
+ </div></div></div><div class="para">
+ The system startup scripts create and configure a single wired connection called <span class="guilabel"><strong>System eth0</strong></span> by default on all systems. Although you can edit <span class="guilabel"><strong>System eth0</strong></span>, creating a new wired connection for your custom settings is recommended. You can create a new wired connection by selecting the <span class="guilabel"><strong>Wired</strong></span> tab and clicking the <span class="guibutton"><strong>Add</strong></span> button.
+ </div><div class="note"><h2>The dialog for adding and editing connections is the same</h2><div class="para">
+ When you add a new connection by clicking the <span class="guibutton"><strong>Add</strong></span> button, <span class="application"><strong>NetworkManager</strong></span> creates a new configuration file for that connection and then opens the same dialog that is used for editing an existing connection. There is no difference between these dialogs. In effect, you are always editing a connection; the difference only lies in whether that connection previously existed or was just created by <span class="application"><strong>NetworkManager</strong></span> when you clicked <span class="guibutton"><strong>Add</strong></span>.
+ </div></div><h4>Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — You can customize the name under which this connection is listed in the <span class="guilabel"><strong>Wired</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window by entering a descriptive name in the text-entry box. For example, you could create a wired connection with custom settings for the office called <em class="replaceable"><code>Wired Office</code></em>.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the this connection when it is—or becomes—available. Refer to <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html" title="5.2.3. Connecting to a Network Automatically">Section 5.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="sec-User_and_System_Connections.html" title="5.2.4. User and System Connections">Section 5.2.4, “User and System Connections”</a> for details.
+ </div></li></ul></div><h4>Configuring the Wired Tab</h4><div class="para">
+ The final two configurable settings are located within the <span class="guilabel"><strong>Wired</strong></span> tab itself: the first is a text-entry field where you can specify a MAC (Media Access Control) address, and the second allows you to specify the MTU (Maximum Transmission Unit) value. Normally, you can leave the <span class="guilabel"><strong>MAC address</strong></span> field blank and the <span class="guilabel"><strong>MTU</strong></span> set to <strong class="userinput"><code>automatic</code></strong>. These defaults will suffice unless you are associating a wired connection with a second or specific NIC, or performing advanced networking. In such cases, refer to the following descriptions:
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>MAC Address</strong></span> </span></dt><dd><div class="para">
+ Network hardware such as a Network Interface Card (NIC) has a unique MAC address (Media Access Control; also known as a <em class="firstterm">hardware address</em>) that identifies it to the system. Running the <code class="command">ip addr</code> command will show the MAC address associated with each interface. For example, in the following <code class="command">ip addr</code> output, the MAC address for the eth0 interface (which is <code class="computeroutput"> 52:54:00:26:9e:f1</code>) immediately follows the <code class="computeroutput">link/ether</code> keyword:
+ </div><pre class="screen">~]# <code class="command">ip addr</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
+ link/ether <span class="emphasis"><em>52:54:00:26:9e:f1</em></span> brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.251/24 brd 192.168.122.255 scope global eth0
+ inet6 fe80::5054:ff:fe26:9ef1/64 scope link
+ valid_lft forever preferred_lft forever</pre><div class="para">
+ A single system can have one or more NICs installed on it. The <span class="guilabel"><strong>MAC address</strong></span> field therefore allows you to associate a specific NIC with a specific connection (or connections). As mentioned, you can determine the MAC address using the <code class="command">ip addr</code> command, and then copy and paste that value into the <span class="guilabel"><strong>MAC address</strong></span> text-entry field.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>MTU</strong></span> </span></dt><dd><div class="para">
+ The MTU (Maximum Transmission Unit) value represents the size in bytes of the largest packet that the connection will use to transmit. This value defaults to <code class="constant">1500</code> when using IPv4, or a variable number <code class="constant">1280</code> or higher for IPv6, and does not generally need to be specified or changed.
+ </div></dd></dl></div><h4>Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your new wired connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network" title="5.2.1. Connecting to a Network">Section 5.2.1, “Connecting to a Network”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ At this point, you have created a new wired connection. You can further configure your connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ port-based Network Access Control (PNAC), click the <span class="guilabel"><strong>802.1x Security</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Connection_Settings.html#sec-Configuring_802.1x_Security" title="5.4.1. Configuring 802.1x Security">Section 5.4.1, “Configuring 802.1x Security”</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv4_Settings.html" title="5.4.4. Configuring IPv4 Settings">Section 5.4.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv6_Settings.html" title="5.4.5. Configuring IPv6 Settings">Section 5.4.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></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="sec-Establishing_a_Wireless_Connection.html"><strong>Next</strong>5.3.2. Establishing a Wireless Connection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_Routes.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_Routes.html
new file mode 100644
index 0000000..1fabcc4
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_Routes.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>5.3.6. Establishing 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Establishing_Connections.html" title="5.3. Establishing Connections" /><link rel="prev" href="sec-Establishing_a_DSL_Connection.html" title="5.3.5. Establishing a DSL Connection" /><link rel="next" href="sec-Configuring_Connection_Settings.html" title="5.4. Configuring Connection Settings" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Th
is is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_a_DSL_Connection.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.3.6. Establishing Routes" id="sec-Establishing_Routes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_Routes">5.3.6. Establishing Routes</h3></div></div></div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-System_eth0-Routes.png" align="middle"
width="444" /><div class="caption"><div class="para">
+ Configuring static network routes
+ </div></div></div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Addresses</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Address</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Prefix</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Gateway</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Metric</strong></span> —
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Ignore automatically obtained routes</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Use this connection only for resources on its network</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_DSL_Connection.html"><strong>Prev</strong>5.3.5. Establishing a DSL Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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.4. Configuring Connection Settings</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_DSL_Connection.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_DSL_Connection.html
new file mode 100644
index 0000000..26629b7
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_DSL_Connection.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.5. Establishing a DSL Connection</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Establishing_Connections.html" title="5.3. Establishing Connections" /><link rel="prev" href="sec-Establishing_a_VPN_Connection.html" title="5.3.4. Establishing a VPN Connection" /><link rel="next" href="sec-Establishing_Routes.html" title="5.3.6. Establishing Routes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifr
ame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_a_VPN_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_Routes.html"><strong>Next</strong></a></li></ul><div class="section" title="5.3.5. Establishing a DSL Connection" id="sec-Establishing_a_DSL_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_a_DSL_Connection">5.3.5. Establishing a DSL Connection</h3></div></div></div><div class="para">
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Service</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_VPN_Connection.html"><strong>Prev</strong>5.3.4. Establishing a VPN Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-Establishing_Routes.html"><strong>Next</strong>5.3.6. Establishing Routes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_Mobile_Broadband_Connection.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_Mobile_Broadband_Connection.html
new file mode 100644
index 0000000..86fc1b0
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_Mobile_Broadband_Connection.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>5.3.3. Establishing a Mobile Broadband Connection</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Establishing_Connections.html" title="5.3. Establishing Connections" /><link rel="prev" href="sec-Establishing_a_Wireless_Connection.html" title="5.3.2. Establishing a Wireless Connection" /><link rel="next" href="sec-Establishing_a_VPN_Connection.html" title="5.3.4. Establishing a VPN Connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc
" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_a_Wireless_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_VPN_Connection.html"><strong>Next</strong></a></li></ul><div class="section" title="5.3.3. Establishing a Mobile Broadband Connection" id="sec-Establishing_a_Mobile_Broadband_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_a_Mobile_Broadband_Connection">5.3.3. Establishing a Mobile Broadband Connection</h3></div></div>
</div><div class="para">
+ You can use <span class="application"><strong>NetworkManager</strong></span>'s mobile broadband connection abilities to connect to the following <em class="firstterm">2G</em> and <em class="firstterm">3G</em> services:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ 2G — <em class="firstterm">GPRS</em> (<em class="firstterm">General Packet Radio Service</em>) or <em class="firstterm">EDGE</em> (<em class="firstterm">Enhanced Data Rates for GSM Evolution</em>)
+ </div></li><li class="listitem"><div class="para">
+ 3G — <em class="firstterm">UMTS</em> (<em class="firstterm">Universal Mobile Telecommunications System</em>) or <em class="firstterm">HSPA</em> (<em class="firstterm">High Speed Packet Access</em>)
+ </div></li></ul></div><div class="para">
+ Your computer must have a device capable of mobile broadband capability which the system has recognized in order to create the connection. Such a device may be built into your computer (as is the case on many notebooks and netbooks), or may be provided as external hardware (such as a PC card, USB or phone modem).
+ </div><div class="procedure"><h6>Procedure 5.3. Adding a New Mobile Broadband Connection</h6><div class="para">
+ You can configure a mobile broadband connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window and selecting the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab. For more information on opening the <span class="guilabel"><strong>Network Connections</strong></span> window via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet, or by running a shell command, refer to <a class="xref" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>.
+ </div><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button to open the <span class="guilabel"><strong>Set up a Mobile Broadband Connection</strong></span> assistant.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Under <span class="guilabel"><strong>Create a connection for this mobile broadband device</strong></span>, choose the 2G- or 3G-capable device you want to use with the connection. If the dropdown menu is inactive, this indicates that the system was unable to detect a device capable of mobile broadband. In this case, click <span class="guilabel"><strong>Cancel</strong></span>, ensure that you do have a mobile broadband-capable device attached to, and recognized by, the computer, and then retry this procedure.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ TBD
+ </div></li></ol></div><div class="procedure"><h6>Procedure 5.4. Editing an Existing Mobile Broadband Connection</h6><div class="para">
+ Follow these steps to edit an existing mobile broadband connection.
+ </div><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Open the <span class="guilabel"><strong>Network Connections</strong></span> window and select the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab. For more information on opening the <span class="guilabel"><strong>Network Connections</strong></span> window via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet, or by running a shell command, refer to <a class="xref" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Select the connection you wish to edit and click the <span class="guilabel"><strong>Edit</strong></span> button.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Configure the connection name, auto-connect behavior, and availability settings.
+ </div><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — You can customize the name under which this connection is listed in the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window by entering a descriptive name in the text-entry box.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the this connection when it is—or becomes—available. Refer to <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html" title="5.2.3. Connecting to a Network Automatically">Section 5.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="sec-User_and_System_Connections.html" title="5.2.4. User and System Connections">Section 5.2.4, “User and System Connections”</a> for details.
+ </div></li></ul></div></li><li class="step" title="Step 4"><div class="para">
+ Edit the mobile broadband-specific settings by referring to <a class="xref" href="sec-Establishing_a_Mobile_Broadband_Connection.html#bh-Configuring_the_Mobile_Broadband_Tab" title="5.3.3. Configuring the Mobile Broadband Tab">Section 5.3.3, “Configuring the Mobile Broadband Tab”</a>.
+ </div></li><li class="step" title="Step 5"><div class="para">
+ Once you have finished editing your new mobile broadband connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network" title="5.2.1. Connecting to a Network">Section 5.2.1, “Connecting to a Network”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ At this point, you have created a new mobile broadband connection. You can further configure your connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Point-to-point settings for the connection, click the <span class="guilabel"><strong>PPP Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_PPP_Point-to-Point_Settings.html" title="5.4.3. Configuring PPP (Point-to-Point) Settings">Section 5.4.3, “Configuring PPP (Point-to-Point) Settings”</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv4_Settings.html" title="5.4.4. Configuring IPv4 Settings">Section 5.4.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv6_Settings.html" title="5.4.5. Configuring IPv6 Settings">Section 5.4.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></li></ol></div><h4>Configuring the Mobile Broadband Tab</h4><div class="para">
+ If you have already added a new mobile broadband connection using the assistant (refer to <a class="xref" href="sec-Establishing_a_Mobile_Broadband_Connection.html#procedure-Adding_a_New_Mobile_Broadband_Connection" title="Procedure 5.3. Adding a New Mobile Broadband Connection">Procedure 5.3, “Adding a New Mobile Broadband Connection”</a> for instructions), you can edit the <span class="guilabel"><strong>Mobile Broadband</strong></span> tab to disable roaming if home network is not available, assign a network ID, or instruct <span class="application"><strong>NetworkManager</strong></span> to prefer a certain technology (such as 3G or 2G) when using the connection.
+ </div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Number</strong></span> </span></dt><dd><div class="para">
+ The number that is dialed to establish a PPP connection with the GSM-based mobile broadband network. You can usually leave this field blank and simply enter the <span class="guilabel"><strong>APN</strong></span> instead.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Username</strong></span> </span></dt><dd><div class="para">
+ Enter the username used to authenticate with the network. Some providers do not provide a username, or accept any username when connecting to the network.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Password</strong></span> </span></dt><dd><div class="para">
+ Enter the password used to authenticate with the network. Some providers do not provide a password, or accept any password.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>APN</strong></span> </span></dt><dd><div class="para">
+ Enter the <em class="firstterm">APN</em> (<em class="firstterm">Access Point Name</em>) used to establish a connection with the GSM-based network. Entering the correct APN for a connection is important because it often determines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ how the user is billed for their network usage; and/or
+ </div></li><li class="listitem"><div class="para">
+ whether the user has access to the Internet or to an intranet or subnetwork.
+ </div></li></ul></div></dd><dt><span class="term"> <span class="guilabel"><strong>Network ID</strong></span> </span></dt><dd><div class="para">
+ Entering a <span class="guilabel"><strong>Network ID</strong></span> causes <span class="application"><strong>NetworkManager</strong></span> to force the device to register only on a specific network. This can be used to ensure the connection does not roam when it is not possible to control roaming directly.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Type</strong></span> </span></dt><dd><div class="para">
+ <span class="guilabel"><strong>Any</strong></span> — The default value of <span class="guilabel"><strong>Any</strong></span> allows <span class="application"><strong>NetworkManager</strong></span>
+ .
+ </div><div class="para">
+ <span class="guilabel"><strong>3G (UMTS/HSPA)</strong></span> — Force the connection to use only 3G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>2G (GPRS/EDGE)</strong></span> — Force the connection to use only 2G network technologies.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 3G (UMTS/HSPA)</strong></span> — First attempt to connect using a 3G technology such as HSPA or UMTS, and fall back to GPRS or EDGE only upon failure.
+ </div><div class="para">
+ <span class="guilabel"><strong>Prefer 2G (GPRS/EDGE)</strong></span> — First attempt to connect using a 2G technology such as GPRS or EDGE, and fall back to HSPA or UMTS only upon failure.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Allow roaming if home network is not available</strong></span> </span></dt><dd><div class="para">
+ Uncheck this box if you want <span class="application"><strong>NetworkManager</strong></span> to terminate the connection if you transition from the home network to a roaming one, thereby avoiding possible roaming charges. If the box is checked, <span class="application"><strong>NetworkManager</strong></span> will maintain the connection when it transitions from the home network to a roaming one, and vice versa.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>PIN</strong></span> </span></dt><dd><div class="para">
+ If your device's <em class="firstterm">SIM</em> (<em class="firstterm">Subscriber Identity Module</em>) is locked with a <em class="firstterm">PIN</em> (<em class="firstterm">Personal Identification Number</em>), enter the PIN so that <span class="application"><strong>NetworkManager</strong></span> can unlock the device. <span class="application"><strong>NetworkManager</strong></span> must unlock the SIM if it requires a PIN in order to use the device for any purpose.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_Wireless_Connection.html"><strong>Prev</strong>5.3.2. Establishing a Wireless Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-Establishing_a_VPN_Connection.html"><strong>Next</strong>5.3.4. Establishing a VPN Connection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_VPN_Connection.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_VPN_Connection.html
new file mode 100644
index 0000000..61149f8
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_VPN_Connection.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>5.3.4. Establishing a VPN Connection</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Establishing_Connections.html" title="5.3. Establishing Connections" /><link rel="prev" href="sec-Establishing_a_Mobile_Broadband_Connection.html" title="5.3.3. Establishing a Mobile Broadband Connection" /><link rel="next" href="sec-Establishing_a_DSL_Connection.html" title="5.3.5. Establishing a DSL Connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="
toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_a_Mobile_Broadband_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_DSL_Connection.html"><strong>Next</strong></a></li></ul><div class="section" title="5.3.4. Establishing a VPN Connection" id="sec-Establishing_a_VPN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_a_VPN_Connection">5.3.4. Establishing a VPN Connection</h3></div></div></div><div class="para">
+ Connecting to a Virtual Private Network (VPN) enables you to communicate securely between your Local Area Network (LAN), and another, remote LAN. After successfully establishing a VPN connection, a VPN router or gateway performs the following actions upon the packets that you transmit:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ it adds an <em class="firstterm">Authentication Header</em> for routing and authentication purposes;
+ </div></li><li class="listitem"><div class="para">
+ it encrypts the packet data; and
+ </div></li><li class="listitem"><div class="para">
+ it encloses the data with an Encapsulating Security Payload (ESP), which constitutes the decryption and handling instructions.
+ </div></li></ol></div><div class="para">
+ The receiving VPN router strips the header information, decrypts the data, and routes it to its intended destination (either a workstation or other node on a network). Using a network-to-network connection, the receiving node on the local network receives the packets already decrypted and ready for processing. The encryption/decryption process in a network-to-network VPN connection is therefore transparent to clients.
+ </div><div class="para">
+ Because they employ several layers of authentication and encryption, VPNs are a secure and effective means of connecting multiple remote nodes to act as a unified intranet.
+ </div><div class="para">
+ You can configure a VPN connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window and selecting the <span class="guilabel"><strong>tab</strong></span> tab. For more information on opening the <span class="guilabel"><strong>Network Connections</strong></span> window via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet, or by running a shell command, refer to <a class="xref" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>.
+ </div><h4>Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — You can customize the name under which this connection is listed in the <span class="guilabel"><strong>tab</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window by entering a descriptive name in the text-entry box.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the this connection when it is—or becomes—available. Refer to <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html" title="5.2.3. Connecting to a Network Automatically">Section 5.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="sec-User_and_System_Connections.html" title="5.2.4. User and System Connections">Section 5.2.4, “User and System Connections”</a> for details.
+ </div></li></ul></div><h4>Configuring the <em class="replaceable"><code><tab></code></em> Tab</h4><h4>Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing your new VPN connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network" title="5.2.1. Connecting to a Network">Section 5.2.1, “Connecting to a Network”</a> for information on using your new or altered connection.
+ </div><div class="para">
+ At this point, you have created a new VPN connection. You can further configure your connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv4_Settings.html" title="5.4.4. Configuring IPv4 Settings">Section 5.4.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li></ul></div><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>Gateway</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Group name</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>User password</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Group password</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>User name</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Domain</strong></span> </span></dt><dd><div class="para">
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Encryption Method</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Secure (default)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Weak (use with caution)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>None (completely insecure)</strong></span> —
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>NAT traversal</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Cisco UDP (default)</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>NAT-T</strong></span> —
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Disabled</strong></span> —
+ </div><div class="para">
+ <span class="guilabel"><strong>Disable Dead Peer Detection</strong></span> —
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_a_Mobile_Broadband_Connection.html"><strong>Prev</strong>5.3.3. Establishing a Mobile Broadband Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</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-Establishing_a_DSL_Connection.html"><strong>Next</strong>5.3.5. Establishing a DSL Connection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_Wireless_Connection.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_Wireless_Connection.html
new file mode 100644
index 0000000..54a388d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Establishing_a_Wireless_Connection.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>5.3.2. Establishing a Wireless Connection</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Establishing_Connections.html" title="5.3. Establishing Connections" /><link rel="prev" href="sec-Establishing_Connections.html" title="5.3. Establishing Connections" /><link rel="next" href="sec-Establishing_a_Mobile_Broadband_Connection.html" title="5.3.3. Establishing a Mobile Broadband Connection" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" sr
c="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_Connections.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Establishing_a_Mobile_Broadband_Connection.html"><strong>Next</strong></a></li></ul><div class="section" title="5.3.2. Establishing a Wireless Connection" id="sec-Establishing_a_Wireless_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Establishing_a_Wireless_Connection">5.3.2. Establishing a Wireless Connection</h3></div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> makes configuring a wireless (also known as wi-fi or 802.1<em class="replaceable"><code>a/b/g/n</code></em>) connection quick and simple. To establish a wireless connection, you need:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ a computer capable of wi-fi connectivity (such as a laptop with an integrated 802.1<em class="replaceable"><code>x</code></em> card or chip);
+ </div></li><li class="listitem"><div class="para">
+ a wireless access point to connect to (such as a wireless router); and,
+ </div></li><li class="listitem"><div class="para">
+ if the access point is secured, an authentication secret such as a key, passphrase, or digital certificate.
+ </div></li></ul></div><div class="para">
+ To configure a mobile broadband (such as 3G) connection instead of a wireless one, refer to <a class="xref" href="sec-Establishing_a_Mobile_Broadband_Connection.html" title="5.3.3. Establishing a Mobile Broadband Connection">Section 5.3.3, “Establishing a Mobile Broadband Connection”</a>.
+ </div><h4>Quickly Connecting to an Available Access Point</h4><div class="para">
+ The easiest way to connect to an available access point is to left-click on the <span class="application"><strong>NetworkManager</strong></span> applet, locate the SSID of the access point in the list of <span class="guilabel"><strong>Available</strong></span> networks, and click on it. If the access point is secured, a dialog prompts you for authentication.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Wireless_authentication_required.png" align="middle" /><div class="caption"><div class="para">
+ Authenticating with a wireless access point
+ </div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> tries to auto-detect the type of security used by the access point. If there are multiple possibilities, <span class="application"><strong>NetworkManager</strong></span> guesses the security type and presents it in the <span class="guilabel"><strong>Wireless security</strong></span> dropdown. To see if there are multiple choices, click the <span class="guilabel"><strong>Wireless security</strong></span> dropdown menu and select the type of security the access point is using. If you are unsure, try connecting to each type in turn. Finally, enter the key or passphrase in the <span class="guilabel"><strong>Password</strong></span> field. Certain password types, such as a 40-bit WEP or 128-bit WPA key, are invalid unless they are of a requisite length. The <span class="guilabel"><strong>Connect</strong></span> button will remain inactive until you enter a key of the length required for the selected security typ
e. To learn more about wireless security, refer to <a class="xref" href="sec-Configuring_Wireless_Security.html" title="5.4.2. Configuring Wireless Security">Section 5.4.2, “Configuring Wireless Security”</a>.
+ </div><div class="para">
+ If <span class="application"><strong>NetworkManager</strong></span> connects to the access point succesfully, its applet icon will change into a graphical indicator of the wireless connection's signal strength.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM_applet-signal_strength_75.png" align="middle" /><div class="caption"><div class="para">
+ Applet icon indicating a wireless connection signal strength of 75%
+ </div></div></div><div class="para">
+ You can also edit the settings for one of these auto-created access point connections just as if you had <span class="guilabel"><strong>Add</strong></span>ded it yourself. The <span class="guilabel"><strong>Wireless</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window lists all of the connections you have ever tried to connect to: <span class="application"><strong>NetworkManager</strong></span> names each of them <code class="computeroutput">Auto <em class="replaceable"><code><SSID></code></em> </code>, where SSID is the <em class="firstterm">Service Set identifier</em> of the access point.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Wireless_Auto_Connections_List.png" align="middle" /><div class="caption"><div class="para">
+ Previous access points that have been connected to
+ </div></div></div><h4>Connecting to a Hidden Wireless Network</h4><div class="para">
+ All access points have a <em class="firstterm">Service Set identifier</em> (SSID) to identify them. However, an access point may be configured not to broadcast its SSID, in which case it is <span class="emphasis"><em>hidden</em></span>, and will not show up in <span class="application"><strong>NetworkManager</strong></span>'s list of <span class="guilabel"><strong>Available</strong></span> networks. You can still connect to a wireless access point that is hiding its SSID as long as you know its SSID, authentication method, and secrets.
+ </div><div class="para">
+ To connect to a hidden wireless network, left-click <span class="application"><strong>NetworkManager</strong></span>'s applet icon and select <span class="guilabel"><strong>Connect to Hidden Wireless Network...</strong></span> to cause a dialog to appear. If you have connected to the hidden network before, use the <span class="guilabel"><strong>Connection</strong></span> dropdown to select it, and click <span class="guibutton"><strong>Connect</strong></span>. If you have not, leave the <span class="guilabel"><strong>Connection</strong></span> dropdown as <span class="guimenuitem"><strong>New...</strong></span>, enter the SSID of the hidden network, select its <span class="guilabel"><strong>Wireless security</strong></span> method, enter the correct authentication secrets, and click <span class="guibutton"><strong>Connect</strong></span>.
+ </div><div class="para">
+ For more information on wireless security settings, refer to <a class="xref" href="sec-Configuring_Wireless_Security.html" title="5.4.2. Configuring Wireless Security">Section 5.4.2, “Configuring Wireless Security”</a>.
+ </div><h4>Editing a Connection, or Creating a Completely New One</h4><div class="para">
+ You can edit an existing connection that you have tried or succeeded in connecting to in the past by opening the <span class="guilabel"><strong>Wireless</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span>, selecting the connection by name (words which follow <code class="computeroutput">Auto</code> refer to the SSID of an access point), and clicking <span class="guilabel"><strong>Edit</strong></span>.
+ </div><div class="para">
+ You can create a new connection by opening the <span class="guilabel"><strong>Network Connections</strong></span> window, selecting the <span class="guilabel"><strong>Wireless</strong></span> tab, and clicking the <span class="guilabel"><strong>Add</strong></span> button.
+ </div><div class="para">
+ For more information on opening the <span class="guilabel"><strong>Network Connections</strong></span> window via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet, or by running a shell command, refer to <a class="xref" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="5.2.2. Configuring New and Editing Existing Connections">Section 5.2.2, “Configuring New and Editing Existing Connections”</a>.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Editing_Wireless_Connection_1.png" align="middle" /><div class="caption"><div class="para">
+ Editing the newly-created Wireless connection 1
+ </div></div></div><h4>Configuring the Connection Name, Auto-Connect Behavior, and Availability Settings</h4><div class="para">
+ Three settings in the <span class="guilabel"><strong>Editing</strong></span> dialog are common to all connection types:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connection name</strong></span> — You can customize the name under which this connection is listed in the <span class="guilabel"><strong>Wireless</strong></span> tab of the <span class="guilabel"><strong>Network Connections</strong></span> window by entering a descriptive name in the text-entry box. By default, wireless connections are named the same as the <em class="firstterm">SSID</em> of the wireless access point. You can rename the wireless connection without affecting its ability to connect, but it is recommended to retain the SSID name.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Connect automatically</strong></span> — Check this box if you want <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the this connection when it is—or becomes—available. Refer to <a class="xref" href="sec-Connecting_to_a_Network_Automatically.html" title="5.2.3. Connecting to a Network Automatically">Section 5.2.3, “Connecting to a Network Automatically”</a> for more information.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Available to all users</strong></span> — check this box to create a connection available to all users on the system. Changing this setting may require root privileges. Refer to <a class="xref" href="sec-User_and_System_Connections.html" title="5.2.4. User and System Connections">Section 5.2.4, “User and System Connections”</a> for details.
+ </div></li></ul></div><h4>Configuring the Wireless Tab</h4><div class="variablelist"><dl><dt><span class="term"> <span class="guilabel"><strong>SSID</strong></span> </span></dt><dd><div class="para">
+ All access points have a <em class="firstterm">Service Set identifier</em> to identify them. However, an access point may be configured not to broadcast its SSID, in which case it is <span class="emphasis"><em>hidden</em></span>, and will not show up in <span class="application"><strong>NetworkManager</strong></span>'s list of <span class="guilabel"><strong>Available</strong></span> networks. You can still connect to a wireless access point that is hiding its SSID as long as you know its SSID (and authentication secrets).
+ </div><div class="para">
+ For information on connecting to a hidden wireless network, refer to <a class="xref" href="sec-Establishing_a_Wireless_Connection.html#bh-Connecting_to_a_Hidden_Wireless_Network" title="5.3.2. Connecting to a Hidden Wireless Network">Section 5.3.2, “Connecting to a Hidden Wireless Network”</a>.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>Mode</strong></span> </span></dt><dd><div class="para">
+ <span class="guimenuitem"><strong>Infrastructure</strong></span> — Set <span class="guilabel"><strong>Mode</strong></span> to <span class="guimenuitem"><strong>Infrastructure</strong></span> if you are connecting to a wireless access point such as a router or a switch.
+ </div><div class="para">
+ <span class="guimenuitem"><strong>Ad-hoc</strong></span> — Set <span class="guilabel"><strong>Mode</strong></span> to <span class="guimenuitem"><strong>Ad-hoc</strong></span> if you are creating a peer-to-peer network for two or more mobile devices to communicate directly with each other. If you use <span class="guimenuitem"><strong>Ad-hoc</strong></span> mode, you must ensure that the same <span class="guilabel"><strong>SSID</strong></span> is set for all participating wireless devices, and that they are all communicating over the same channel.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>BSSID</strong></span> </span></dt><dd><div class="para">
+ The Basic Service Set Identifier (BSSID) is the MAC address of the wireless access point you are connecting to when in <span class="guilabel"><strong>Infrastructure</strong></span> mode. This field is blank by default, and you are able to connect to a wireless access point by <span class="guilabel"><strong>SSID</strong></span> without having to specify its <span class="guilabel"><strong>BSSID</strong></span>.
+ </div><div class="para">
+ For ad-hoc networks, the BSSID is generated randomly. However, <span class="application"><strong>NetworkManager</strong></span> does not have the capability to generate the BSSID for an ad-hoc network.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>MAC address</strong></span> </span></dt><dd><div class="para">
+ Like an ethernet Network Interface Card (NIC), a wireless adapter has a unique MAC address (Media Access Control; also known as a <em class="firstterm">hardware address</em>) that identifies it to the system. Running the <code class="command">ip addr</code> command will show the MAC address associated with each interface. For example, in the following <code class="command">ip addr</code> output, the MAC address for the <code class="computeroutput">wlan0</code> interface (which is <code class="computeroutput">00:1c:bf:02:f8:70</code>) immediately follows the <code class="computeroutput">link/ether</code> keyword:
+ </div><pre class="screen">~]# <code class="command">ip addr</code>
+1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ inet6 ::1/128 scope host
+ valid_lft forever preferred_lft forever
+2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
+ link/ether 52:54:00:26:9e:f1 brd ff:ff:ff:ff:ff:ff
+ inet 192.168.122.251/24 brd 192.168.122.255 scope global eth0
+ inet6 fe80::5054:ff:fe26:9ef1/64 scope link
+ valid_lft forever preferred_lft forever
+3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
+ link/ether <span class="emphasis"><em>00:1c:bf:02:f8:70</em></span> brd ff:ff:ff:ff:ff:ff
+ inet 10.200.130.67/24 brd 10.200.130.255 scope global wlan0
+ inet6 fe80::21c:bfff:fe02:f870/64 scope link
+ valid_lft forever preferred_lft forever</pre><div class="para">
+ A single system could have one or more wireless network adapters connected to it. The <span class="guilabel"><strong>MAC address</strong></span> field therefore allows you to associate a specific wireless adapter with a specific connection (or connections). As mentioned, you can determine the MAC address using the <code class="command">ip addr</code> command, and then copy and paste that value into the <span class="guilabel"><strong>MAC address</strong></span> text-entry field.
+ </div></dd><dt><span class="term"> <span class="guilabel"><strong>MTU</strong></span> </span></dt><dd><div class="para">
+ The MTU (Maximum Transmission Unit) value represents the size in bytes of the largest packet that the connection will use to transmit. If set to a non-zero number, only packets of the specified size or smaller will be transmitted. Larger packets are broken up into multiple Ethernet frames. It is recommended to leave this setting on <span class="guimenuitem"><strong>automatic</strong></span>.
+ </div></dd></dl></div><h4>Saving Your New (or Modified) Connection and Making Further Configurations</h4><div class="para">
+ Once you have finished editing the wireless connection, click the <span class="guibutton"><strong>Apply</strong></span> button and <span class="application"><strong>NetworkManager</strong></span> will immediately save your customized configuration. Given a correct configuration, you can successfully connect to your the modified connection by selecting it from the <span class="application"><strong>NetworkManager</strong></span> Notification Area applet. See <a class="xref" href="sec-Interacting_with_NetworkManager.html#sec-Connecting_to_a_Network" title="5.2.1. Connecting to a Network">Section 5.2.1, “Connecting to a Network”</a> for details on selecting and connecting to a network.
+ </div><div class="para">
+ You can further configure your connection by selecting it in the <span class="guilabel"><strong>Network Connections</strong></span> window and clicking <span class="guilabel"><strong>Edit</strong></span> to return to the <span class="guilabel"><strong>Editing</strong></span> dialog.
+ </div><div class="para">
+ Then, to configure:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ security authentication for the wireless connection, click the <span class="guilabel"><strong>Wireless Security</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_Wireless_Security.html" title="5.4.2. Configuring Wireless Security">Section 5.4.2, “Configuring Wireless Security”</a>;
+ </div></li><li class="listitem"><div class="para">
+ IPv4 settings for the connection, click the <span class="guilabel"><strong>IPv4 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv4_Settings.html" title="5.4.4. Configuring IPv4 Settings">Section 5.4.4, “Configuring IPv4 Settings”</a>; or,
+ </div></li><li class="listitem"><div class="para">
+ IPv6 settings for the connection, click the <span class="guilabel"><strong>IPv6 Settings</strong></span> tab and proceed to <a class="xref" href="sec-Configuring_IPv6_Settings.html" title="5.4.5. Configuring IPv6 Settings">Section 5.4.5, “Configuring IPv6 Settings”</a>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Establishing_Connections.html"><strong>Prev</strong>5.3. Establishing 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="sec-Establishing_a_Mobile_Broadband_Connection.html"><strong>Next</strong>5.3.3. Establishing a Mobile Broadband Connection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Finding_Packages_with_Filters.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Finding_Packages_with_Filters.html
new file mode 100644
index 0000000..4394fef
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Finding_Packages_with_Filters.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_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="id919662" 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="id751606" class="indexterm"></a>
+ <a id="id751621" class="indexterm"></a>
+ <a id="id751633" class="indexterm"></a>
+ <a id="id984076" class="indexterm"></a>
+ <a id="id984092" 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="id984147" class="indexterm"></a>
+ <a id="id984162" class="indexterm"></a>
+ <a id="id602238" 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><span class="term"> <span class="guisubmenu"><strong>Graphical</strong></span> <a id="id602317" 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><span class="term"> <span class="guisubmenu"><strong>Free</strong></span> <a id="id640012" 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><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="id640072" 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><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="id663298" 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"><h2>Important: Using the Only newest items filter</h2><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></dd><dt><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="id663357" 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 <em class="replaceable"><code>x</code></em>86 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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing.html
new file mode 100644
index 0000000..3682524
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing.html
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or e
nable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id892618" class="indexterm"></a><a id="id892630" 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">more_names</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"><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><h6>Example 1.5. Finding which package owns a file and installing it</h6></div><br class="example-break" /><div class="note"><h2>Note</h2><div class="para">
+ <code class="command">yum provides</code> is the same as <code class="command">yum whatprovides</code>.
+ </div></div><div class="note"><h2>Tip: yum provides/whatprovides and Glob Expressions</h2><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><h4>Installing a Package Group</h4><a id="id988112" class="indexterm"></a><a id="id988124" 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"><h2>Not all packages used in examples may be available on RHN</h2><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><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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_More_Yum_Plugins.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_More_Yum_Plugins.html
new file mode 100644
index 0000000..80a2389
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_More_Yum_Plugins.html
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</if
rame></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_Descriptions.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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_and_Removing_Package_Groups.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_and_Removing_Package_Groups.html
new file mode 100644
index 0000000..c1d992a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_and_Removing_Package_Groups.html
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><ifram
e id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id926547" class="indexterm"></a><a id="id866675" class="indexterm"></a><a id="id866687" class="indexterm"></a><a id="id866698" 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 <span class="guibutton"><strong>Apply</strong></span>ing.
+ </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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.html
new file mode 100644
index 0000000..0cbbf0c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="t
ocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Finding_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 an
d Removing Packages (and Dependencies)</h3></div></div></div><a id="id765110" class="indexterm"></a><a id="id765121" 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="id750307" 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 installed</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"><h2>Warning: Removing a Package when Other Packages Depend On It</h2><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 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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_and_Upgrading.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_and_Upgrading.html
new file mode 100644
index 0000000..77be005
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Installing_and_Upgrading.html
@@ -0,0 +1,83 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</i
frame></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_File_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="id886719" class="indexterm"></a><a id="id955549" class="indexterm"></a><a id="id720254" class="indexterm"></a><a id="id650508" class="indexterm"></a><div class="para">
+ RPM packages typically have file names
+ <a id="id838616" class="indexterm"></a>
+ like <code class="filename">tree-1.5.3-2.fc13.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">fc13</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.fc13.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.fc13.x86_64.rpm</code>
+</pre><div class="note"><h2>Use -Uvh for nicely-formatted RPM installs</h2><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 marks.
+ </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"><h2>Always use the -i (install) option to install new kernel packages!</h2><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 29. Manually Upgrading the Kernel">Chapter 29, <i>Manually Upgrading the Kernel</i></a>.
+ </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.fc13.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.fc13.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.fc13.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="id658717" class="indexterm"></a>
+ <a id="id658729" class="indexterm"></a>
+ , the following output is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ package tree-1.5.3-2.fc13.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.fc13.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="id1011104" 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="id935522" class="indexterm"></a>
+ <a id="id875287" class="indexterm"></a>
+ , the following is displayed:
+ </div><pre class="screen">Preparing... ##################################################
+ file /usr/bin/foobar from install of foo-1.0-1.fc13.x86_64 conflicts
+with file from package bar-3.1.1.fc13.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.fc13.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="id994785" class="indexterm"></a><a id="id592334" class="indexterm"></a><div class="para">
+ RPM packages may sometimes depend on other packages
+ <a id="id592348" class="indexterm"></a>
+ <a id="id749839" 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.fc13.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.fc13.x86_64.rpm bar-3.1.1.fc13.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.fc13.i586.rpm</pre><div class="warning"><h2>Warning: Forcing Package Installation</h2><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><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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Interacting_with_NetworkManager.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Interacting_with_NetworkManager.html
new file mode 100644
index 0000000..757a02c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Interacting_with_NetworkManager.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="
toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_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_Draft_Documentation/0.1/html/Deployment_Guide/sec-NetworkManager_Architecture.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-NetworkManager_Architecture.html
new file mode 100644
index 0000000..b680704
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-NetworkManager_Architecture.html
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.5. NetworkManager 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-Configuring_IPv6_Settings.html" title="5.4.5. Configuring IPv6 Settings" /><link rel="next" href="ch-Controlling_Access_to_Services.html" title="Chapter 6. Controlling Access to Services" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">
This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_IPv6_Settings.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="5.5. NetworkManager Architecture" id="sec-NetworkManager_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-NetworkManager_Architecture">5.5. NetworkManager Architecture</h2></div></div></div><div class="para">
+ See <a href="http://live.gnome.org/NetworkManagerConfiguration">http://live.gnome.org/NetworkManagerConfiguration</a>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_IPv6_Settings.html"><strong>Prev</strong>5.4.5. Configuring IPv6 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="ch-Controlling_Access_to_Services.html"><strong>Next</strong>Chapter 6. Controlling Access to Services</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-PackageKit_Architecture.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-PackageKit_Architecture.html
new file mode 100644
index 0000000..7518b7b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-PackageKit_Architecture.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifram
e, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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"><strong>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="id868467" 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"><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>Session and Startup</strong></span>, <span class="guilabel"><strong>Application Autostart</strong></span> tab
+ </div>
+
+ </td><td align="left">
+ gpk-update-icon
+ </td></tr></tbody></table></div><h6>Table 2.1. PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands</h6></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 6. Controlling Access to Services">Chapter 6, <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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Packages_and_Package_Groups.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Packages_and_Package_Groups.html
new file mode 100644
index 0000000..2df00de
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Packages_and_Package_Groups.html
@@ -0,0 +1,128 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left"
href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="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="id761317" class="indexterm"></a><a id="id761329" 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="id761350" class="indexterm"></a><a id="id1005122" class="indexterm"></a><a id="id1005134" class="indexterm"></a><a id="id1005146" class="indexterm"></a><a id="id1005157" class="indexterm"></a><a id="id1005169" 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="id714229" class="indexterm"></a>
+ <a id="id714245" 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="id714276" class="indexterm"></a>
+ <a id="id714291" class="indexterm"></a>
+ <code class="command">yum list</code> and related commands provide information about packages, package groups, and repositories.
+ </div><div class="note"><h2>Tip: Filtering Results with Glob Expressions</h2><a id="id714320" class="indexterm"></a><a id="id927288" 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 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><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"><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><h6>Example 1.2. Filtering results using a single glob expression with two escaped wildcard characters</h6></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"><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><h6>Example 1.3. Filtering results using a double-quoted glob expression</h6></div><br class="example-break" /></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"><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><h6>Example 1.4. Listing all ABRT addons and plugins using glob expressions</h6></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="id619223" class="indexterm"></a>
+ <a id="id619239" 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="id619270" class="indexterm"></a>
+ <a id="id619286" 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="id619315" class="indexterm"></a>
+ <a id="id762068" 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="id762097" class="indexterm"></a>
+ <a id="id762112" class="indexterm"></a>
+ List all package groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum repolist</code> —
+ <a id="id762140" class="indexterm"></a>
+ <a id="id744399" 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="id744445" class="indexterm"></a>
+ <a id="id744460" 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="id623424" class="indexterm"></a>
+ <a id="id623440" 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 13, 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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Plugin_Descriptions.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Plugin_Descriptions.html
new file mode 100644
index 0000000..98ac165
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Plugin_Descriptions.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.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or
enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="next"><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="id895777" 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 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 c
lass="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="id992118" 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>refresh-packagekit (PackageKit-yum-plugin)</h4><a id="id827687" 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="id827724" 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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Removing.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Removing.html
new file mode 100644
index 0000000..fac872a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Removing.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgra
de your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="id689518" class="indexterm"></a><a id="id689530" class="indexterm"></a><div class="para">
+ <code class="command">yum remove <package_name></code> <a id="id689548" class="indexterm"></a>
+ <a id="id689564" 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"><h2>Warning: Removing a Package when Other Packages Depend On It</h2><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><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"><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><h6>Example 1.6. Alternative but equivalent ways of removing a package group</h6></div><br class="example-break" /><div class="important"><h2>Smart package group removal</h2><a id="id719173" class="indexterm"></a><a id="id719185" 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><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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Setting_repository_Options.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Setting_repository_Options.html
new file mode 100644
index 0000000..181080a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Setting_repository_Options.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=".
./../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_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="id692120" 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><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><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><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">
+ Here is another useful-but-optional [<em class="replaceable"><code>repository</code></em>] options:
+ </div><div class="variablelist"><dl><dt><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_Draft_Documentation/0.1/html/Deployment_Guide/sec-User_and_System_Connections.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-User_and_System_Connections.html
new file mode 100644
index 0000000..112cb41
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-User_and_System_Connections.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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-Establishing_Connections.html" title="5.3. Establishing Connections" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="
../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-Establishing_Connections.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"><h2>Tip: Increase security by making VPN connections user-specific</h2><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 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"><h6>Procedure 5.2. Changing a Connection to be User-Specific instead of System-Wide, or Vice-Versa</h6><div class="note"><h2>Depending on the system's policy, root privileges may be required</h2><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><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-Establishing_Connections.html"><strong>Next</strong>5.3. Establishing Connections</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Using_Add_Remove_Software.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Using_Add_Remove_Software.html
new file mode 100644
index 0000000..6aa84b1
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Using_Add_Remove_Software.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or en
able iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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" href="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="id924404" class="indexterm"></a><a id="id924415" 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="id728499" class="indexterm"></a>
+ <a id="id728511" 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"><h2>Showing Source RPM, Test and Debuginfo Repositories</h2><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 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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Using_Yum_Variables.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Using_Yum_Variables.html
new file mode 100644
index 0000000..8facf33
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Using_Yum_Variables.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../to
c.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_repository_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="id931139" 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><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><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><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><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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
new file mode 100644
index 0000000..628544c
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.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>29.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 29. Manually Upgrading the Kernel" /><link rel="prev" href="s1-kernel-perform-upgrade.html" title="29.4. Performing the Upgrade" /><link rel="next" href="s1-kernel-boot-loader.html" title="29.6. Verifying the Boot Loader" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="29.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">29.5. Verifying the Initial RAM Disk Image</h2></div></div></div><div class="para">
+ The job of the initial RAM disk image
+ <a id="id713173" class="indexterm"></a>
+ 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 13 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="29.5. Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i">Section 29.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"><h6>Procedure 29.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 29.1. Ensuring that the kernel and initramfs versions match" id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"><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><h6>Example 29.1. Ensuring that the kernel and initramfs versions match</h6></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 29.1. Ensuring that the kernel and initramfs versions match">Example 29.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"><h2>initrd files in the /boot directory are not the same as initramfs files</h2><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></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="29.6. Verifying the Boot Loader">Section 29.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><div class="para">
+ On IBM eSeries System i machines
+ <a id="id642469" class="indexterm"></a>
+ , 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>29.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>29.6. Verifying the Boot Loader</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Viewing_the_Transaction_Log.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Viewing_the_Transaction_Log.html
new file mode 100644
index 0000000..27737fc
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Viewing_the_Transaction_Log.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../
toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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_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="id893460" class="indexterm"></a>
+ <a id="id893472" 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_Draft_Documentation/0.1/html/Deployment_Guide/sec-Yum_Plugins.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Yum_Plugins.html
new file mode 100644
index 0000000..88408fc
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sec-Yum_Plugins.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>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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable i
frame display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="next"><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="id881371" 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="id881435" class="indexterm"></a><a id="id704406" class="indexterm"></a><a id="id704418" 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="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"><div class="example-contents"><pre class="screen">
+[main]
+enabled=1
+</pre></div><h6>Example 1.7. A minimal <span class="application">Yum</span> plugin configuration file</h6></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"><div class="example-contents"><pre class="screen">~]# <code class="command">yum update --disableplugin=presto</code>
+</pre></div><h6>Example 1.8. Disabling the presto plugin while running yum update</h6></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_Draft_Documentation/0.1/html/Deployment_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html
new file mode 100644
index 0000000..0b27c7b
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html
@@ -0,0 +1,124 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 10. Dynamic Host Configuration Protocol (DHCP)" /><link rel="prev" href="s1-dhcp-configuring-client.html" title="10.3. Configuring a DHCP Client" /><link rel="next" href="s1-dhcp_for_ipv6_dhcpv6.html" title="10.5. DHCP for IPv6 (DHCPv6)" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=
"../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-client.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="10.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">10.4. Configuring a Multihomed DHCP Server</h2></div></div></div><a id="id650205" class="indexterm"></a><div cl
ass="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><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><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><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><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"><h2>Alias Interfaces</h2><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 class="section" title="10.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">10.4.1. Host Configuration</h3></div></div></div><a id="id724633" 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="id724659">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><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><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><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="id719522">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>10.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>10.5. DHCP for IPv6 (DHCPv6)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html
new file mode 100644
index 0000000..99f7ad9
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.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>19.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html" title="19.2. Command Line Configuration" /><link rel="prev" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html" title="19.2. Command Line Configuration" /><link rel="next" href="ch-Keyboard_Configuration.html" title="Chapter 20. Keyboard Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe i
d="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-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="19.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_Configuratio
n-Network_Time_Protocol">19.2.2. Network Time Protocol Setup</h3></div></div></div><a id="id921951" class="indexterm"></a><a id="id921964" class="indexterm"></a><a id="id921978" class="indexterm"></a><a id="id921994" 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 adresses:
+ </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="19.2.1. Date and Time Setup">Section 19.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 6. Controlling Access to Services">Chapter 6, <i>Controlling Access to Services</i></a>.
+ </div><div class="note"><h2>Note</h2><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></li></ol></div><a id="id660874" class="indexterm"></a><a id="id1017194" class="indexterm"></a><a id="id1017212" 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 13, 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"><h2>Tip</h2><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></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>19.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 20. Keyboard Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration.html
new file mode 100644
index 0000000..7db219a
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration.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>19.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-Date_and_Time_Configuration.html" title="Chapter 19. Date and Time Configuration" /><link rel="prev" href="chap-Date_and_Time_Configuration.html" title="Chapter 19. Date and Time Configuration" /><link rel="next" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html" title="19.2.2. Network Time Protocol Setup" /></head><body class="draft toc_embeded "><div id="tocdiv" class=
"toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="19.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-Comman
d_Line_Configuration">19.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="19.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">19.2.1. Date and Time Setup</h3></div></div></div><a id="id741279" class="indexterm"></a><a id="id741296" class="indexterm"></a><a id="id741314" 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 19.1. Displaying the current date and time" id="ex-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time"><div class="example-contents"><pre class="screen">~]$ <code class="command">date</code>
+Wed Jun 2 11:58:48 CEST 2010</pre></div><h6>Example 19.1. Displaying the current date and time</h6></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 19. 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>19.2.2. Network Time Protocol Setup</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-RedHat-We_Need_Feedback.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-RedHat-We_Need_Feedback.html
new file mode 100644
index 0000000..beb9438
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-RedHat-We_Need_Feedback.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. 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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><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="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraprojec
t.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="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="id866281" 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">13</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="id963600">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><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><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><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><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><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_Draft_Documentation/0.1/html/Deployment_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html
new file mode 100644
index 0000000..27e0d8d
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.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>15.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="15.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Configuring_Domains.html" title="15.2.5. Configuring Domains" /><link rel="next" href="chap-SSSD_User_Guide-Troubleshooting.html" title="15.2.7. Troubleshooting" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src
="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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="15.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">15.2.6. Setting
up Kerberos Authentication</h3></div></div></div><a id="id794673" 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="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_user_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>15.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>15.2.7. Troubleshooting</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.html
new file mode 100644
index 0000000..af9b63e
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.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>15.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="15.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Introduction.html" title="15.2. The System Security Services Daemon (SSSD)" /><link rel="next" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html" title="15.2.3. Setting Up SSSD" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../..
/../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-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="15.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">15.2.2. SSSD Features</h3></div></div></div><div class="section" title="15.2.2.1. Performing Offline Auth
entication" id="sect-SSSD_User_Guide-SSSD_Features-Performing_Offline_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Performing_Offline_Authentication">15.2.2.1. Performing 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="15.2.2.2. Reducing Server Load" id="sect-SSSD_User_Guide-SSSD_Features-Reducing_Server_Load"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Reducing_Server_Load">15.2.2.2. Reducing Server Load</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="15.2.2.3. Specifying Multiple Domains" id="sect-SSSD_User_Guide-SSSD_Features-Specifying_Multiple_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Specifying_Multiple_Domains">15.2.2.3. Specifying Multiple Domains</h4></div></div></div><a id="id883821" 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="id883771">Considerations Associated with Deleting Cache Files</h5><a id="id883765" 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 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><div class="section" title="15.2.2.4. 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">15.2.2.4. 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="15.2.2.5. Integrating with Other Products" id="sect-SSSD_User_Guide-SSSD_Features-Integrating_with_Other_Products"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Integrating_with_Other_Products">15.2.2.5. Integrating with Other Products</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 added functionality, including host-based access control, and password migration from an LDAP-only environment into the LDAP/Kerberos 5 environment employed by IPA.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Introduction.html"><strong>Prev</strong>15.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>15.2.3. Setting Up SSSD</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html
new file mode 100644
index 0000000..63a758f
--- /dev/null
+++ b/public_html/en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.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>15.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.1" /><meta name="package" content="Fedora_Draft_Documentation-Deployment_Guide-0.1-en-US-13.0.1-1" /><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="15.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Troubleshooting.html" title="15.2.7. Troubleshooting" /><link rel="next" href="pt-sysconfig.html" title="Part III. System Configuration" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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</strong></a></li><li class="next"><a accesskey="n" href="pt-sysconfig.html"><strong>Next</strong></a></li></ul><div class="section" title="15.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">15.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_user_search_base = ou=users,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>15.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="pt-sysconfig.html"><strong>Next</strong>Part III. System Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf b/public_html/en-US/Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf
new file mode 100644
index 0000000..09f0000
Binary files /dev/null and b/public_html/en-US/Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/en-US/toc.html b/public_html/en-US/toc.html
index 9ba5f6b..91a606a 100644
--- a/public_html/en-US/toc.html
+++ b/public_html/en-US/toc.html
@@ -1261,6 +1261,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/es-ES/Site_Statistics.html b/public_html/es-ES/Site_Statistics.html
index 8182a86..d912b11 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Idiomas totales: </b>48<br />
- <b>Paquetes totales: </b>565
+ <b>Paquetes totales: </b>566
</div>
</body>
</html>
diff --git a/public_html/es-ES/toc.html b/public_html/es-ES/toc.html
index 4584b6b..b72334f 100644
--- a/public_html/es-ES/toc.html
+++ b/public_html/es-ES/toc.html
@@ -1528,6 +1528,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/fi-FI/toc.html b/public_html/fi-FI/toc.html
index 1a98757..ee04b58 100644
--- a/public_html/fi-FI/toc.html
+++ b/public_html/fi-FI/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/fr-FR/toc.html b/public_html/fr-FR/toc.html
index 3b51efb..6b52819 100644
--- a/public_html/fr-FR/toc.html
+++ b/public_html/fr-FR/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/gu-IN/toc.html b/public_html/gu-IN/toc.html
index cad88f7..f3a3414 100644
--- a/public_html/gu-IN/toc.html
+++ b/public_html/gu-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/he-IL/toc.html b/public_html/he-IL/toc.html
index 8fa70b9..7cd3a89 100644
--- a/public_html/he-IL/toc.html
+++ b/public_html/he-IL/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/hi-IN/toc.html b/public_html/hi-IN/toc.html
index 1e7016f..75a9622 100644
--- a/public_html/hi-IN/toc.html
+++ b/public_html/hi-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/hu-HU/toc.html b/public_html/hu-HU/toc.html
index f4c685b..5bb4e79 100644
--- a/public_html/hu-HU/toc.html
+++ b/public_html/hu-HU/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/id-ID/toc.html b/public_html/id-ID/toc.html
index c243b25..004f078 100644
--- a/public_html/id-ID/toc.html
+++ b/public_html/id-ID/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/it-IT/toc.html b/public_html/it-IT/toc.html
index 9641098..43636c5 100644
--- a/public_html/it-IT/toc.html
+++ b/public_html/it-IT/toc.html
@@ -1633,6 +1633,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 93ceb94..73f21be 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>言語数の合計: </b>48<br />
- <b>パッケージ数の合計: </b>565
+ <b>パッケージ数の合計: </b>566
</div>
</body>
</html>
diff --git a/public_html/ja-JP/toc.html b/public_html/ja-JP/toc.html
index fe5b204..79c0e0f 100644
--- a/public_html/ja-JP/toc.html
+++ b/public_html/ja-JP/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/kn-IN/toc.html b/public_html/kn-IN/toc.html
index 5aaf7c9..ef484e6 100644
--- a/public_html/kn-IN/toc.html
+++ b/public_html/kn-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/ko-KR/toc.html b/public_html/ko-KR/toc.html
index a5b32b5..b97be52 100644
--- a/public_html/ko-KR/toc.html
+++ b/public_html/ko-KR/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/ml-IN/toc.html b/public_html/ml-IN/toc.html
index 55e6ede..ed768d6 100644
--- a/public_html/ml-IN/toc.html
+++ b/public_html/ml-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/mr-IN/toc.html b/public_html/mr-IN/toc.html
index 6d743f9..105ed7d 100644
--- a/public_html/mr-IN/toc.html
+++ b/public_html/mr-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/nb-NO/toc.html b/public_html/nb-NO/toc.html
index 531e29c..7232da9 100644
--- a/public_html/nb-NO/toc.html
+++ b/public_html/nb-NO/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/nl-NL/toc.html b/public_html/nl-NL/toc.html
index 005efcf..57ecc67 100644
--- a/public_html/nl-NL/toc.html
+++ b/public_html/nl-NL/toc.html
@@ -1588,6 +1588,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/or-IN/Site_Statistics.html b/public_html/or-IN/Site_Statistics.html
index 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/or-IN/toc.html b/public_html/or-IN/toc.html
index 35c411c..bd8a626 100644
--- a/public_html/or-IN/toc.html
+++ b/public_html/or-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/pa-IN/toc.html b/public_html/pa-IN/toc.html
index 7363149..44e6aba 100644
--- a/public_html/pa-IN/toc.html
+++ b/public_html/pa-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 8a265bd..6c31463 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Razem języków: </b>48<br />
- <b>Razem pakietów: </b>565
+ <b>Razem pakietów: </b>566
</div>
</body>
</html>
diff --git a/public_html/pl-PL/toc.html b/public_html/pl-PL/toc.html
index fac2c33..62a7a5b 100644
--- a/public_html/pl-PL/toc.html
+++ b/public_html/pl-PL/toc.html
@@ -1483,6 +1483,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/pt-BR/toc.html b/public_html/pt-BR/toc.html
index 62b432e..9bd8e09 100644
--- a/public_html/pt-BR/toc.html
+++ b/public_html/pt-BR/toc.html
@@ -1378,6 +1378,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/pt-PT/toc.html b/public_html/pt-PT/toc.html
index e52d4e2..5f0720f 100644
--- a/public_html/pt-PT/toc.html
+++ b/public_html/pt-PT/toc.html
@@ -1364,6 +1364,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/ru-RU/toc.html b/public_html/ru-RU/toc.html
index 1c7e826..8b3f731 100644
--- a/public_html/ru-RU/toc.html
+++ b/public_html/ru-RU/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/sk-SK/toc.html b/public_html/sk-SK/toc.html
index d435c79..5502788 100644
--- a/public_html/sk-SK/toc.html
+++ b/public_html/sk-SK/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/sr-Latn-RS/toc.html b/public_html/sr-Latn-RS/toc.html
index 6c5b51b..c21b777 100644
--- a/public_html/sr-Latn-RS/toc.html
+++ b/public_html/sr-Latn-RS/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/sr-RS/toc.html b/public_html/sr-RS/toc.html
index 490780f..a475c2b 100644
--- a/public_html/sr-RS/toc.html
+++ b/public_html/sr-RS/toc.html
@@ -1378,6 +1378,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/sv-SE/toc.html b/public_html/sv-SE/toc.html
index b8586bd..1522332 100644
--- a/public_html/sv-SE/toc.html
+++ b/public_html/sv-SE/toc.html
@@ -1438,6 +1438,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/ta-IN/toc.html b/public_html/ta-IN/toc.html
index b790924..6bb1091 100644
--- a/public_html/ta-IN/toc.html
+++ b/public_html/ta-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/te-IN/toc.html b/public_html/te-IN/toc.html
index 5664b06..8f044e0 100644
--- a/public_html/te-IN/toc.html
+++ b/public_html/te-IN/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/toc.html b/public_html/toc.html
index 365682f..72efef8 100644
--- a/public_html/toc.html
+++ b/public_html/toc.html
@@ -2281,6 +2281,21 @@
</div>
<div class="book">
+ <span id="Deployment_Guide" class="book">Deployment Guide</span>
+ <div class="types">
+
+ <a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub">epub</a>
+
+ <a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html">html</a>
+
+ <a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html">html-single</a>
+
+ <a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf">pdf</a>
+
+ </div>
+ </div>
+
+ <div class="book">
<span id="RPM_Guide" class="book">RPM Guide</span>
<div class="types">
diff --git a/public_html/uk-UA/Site_Statistics.html b/public_html/uk-UA/Site_Statistics.html
index 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/uk-UA/toc.html b/public_html/uk-UA/toc.html
index ad28348..0435fb3 100644
--- a/public_html/uk-UA/toc.html
+++ b/public_html/uk-UA/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/zh-CN/toc.html b/public_html/zh-CN/toc.html
index ba4f953..dba9805 100644
--- a/public_html/zh-CN/toc.html
+++ b/public_html/zh-CN/toc.html
@@ -1483,6 +1483,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_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 81796c1..20493ae 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>24</td>
<td>14</td>
- <td>78</td>
+ <td>79</td>
</tr>
<tr>
@@ -457,7 +457,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>48<br />
- <b>Total Packages: </b>565
+ <b>Total Packages: </b>566
</div>
</body>
</html>
diff --git a/public_html/zh-TW/toc.html b/public_html/zh-TW/toc.html
index 96f7af2..30029df 100644
--- a/public_html/zh-TW/toc.html
+++ b/public_html/zh-TW/toc.html
@@ -1363,6 +1363,21 @@
</div>
</div>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora_Draft_Documentation.0.1.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.epub" >epub</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Deployment_Guide/index.html';return false;">html</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Deployment_Guide/Fedora_Draft_Documentation-0.1-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+
+ </div>
+ </div>
+
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Draft_Documentation.0.1.RPM_Guide.types');">
<a class="type" href="../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html" onclick="window.top.location='../en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html'"><span class="book">RPM Guide</span></a>
<div id='Fedora_Draft_Documentation.0.1.RPM_Guide.types' class="types hidden" onclick="work=0;">
More information about the docs-commits
mailing list