| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114 | <?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [  <!ENTITY % general-entities SYSTEM "../general.ent">  %general-entities;]><sect1 id="ch-scripts-profile"><title>The Bash Shell Startup Files</title><?dbhtml filename="profile.html"?><indexterm zone="ch-scripts-profile"><primary sortas="e-/etc/profile">/etc/profile</primary></indexterm><para>The shell program <command>/bin/bash</command> (hereafterreferred to as <quote>the shell</quote>) uses a collection of startupfiles to help create an environment to run in. Each file has aspecific use and may affect login and interactive environmentsdifferently. The files in the <filenameclass="directory">/etc</filename> directory provide global settings.If an equivalent file exists in the home directory, it may overridethe global settings.</para><para>An interactive login shell is started after a successful login,using <command>/bin/login</command>, by reading the<filename>/etc/passwd</filename> file. An interactive non-login shellis started at the command-line (e.g.,<prompt>[prompt]$</prompt><command>/bin/bash</command>). Anon-interactive shell is usually present when a shell script isrunning. It is non-interactive because it is processing a script andnot waiting for user input between commands.</para><para>For more information, see <command>info bash</command> under the<emphasis>Bash Startup Files and Interactive Shells</emphasis> section.</para><para>The files <filename>/etc/profile</filename> and<filename>~/.bash_profile</filename> are read when the shell isinvoked as an interactive login shell.</para><para>The base <filename>/etc/profile</filename> below sets someenvironment variables necessary for native language support. Settingthem properly results in:</para><itemizedlist><listitem><para>The output of programs translated into the nativelanguage</para></listitem><listitem><para>Correct classification of characters into letters, digits andother classes. This is necessary for <command>bash</command> to properly acceptnon-ASCII characters in command lines in non-English locales</para></listitem><listitem><para>The correct alphabetical sorting order for thecountry</para></listitem><listitem><para>Appropriate default paper size</para></listitem><listitem><para>Correct formatting of monetary, time, and datevalues</para></listitem></itemizedlist><para>This script also sets the <envar>INPUTRC</envar> environment variable thatmakes Bash and Readline use the <filename>/etc/inputrc</filename> file createdearlier.</para><para>Replace <replaceable>[ll]</replaceable> below with thetwo-letter code for the desired language (e.g., <quote>en</quote>) and<replaceable>[CC]</replaceable> with the two-letter code for theappropriate country (e.g., <quote>GB</quote>).<replaceable>[charmap]</replaceable> should be replaced with thecanonical charmap for your chosen locale.</para><para>The list of all locales supported by Glibc can be obtained by runningthe following command:</para><screen><userinput>locale -a</userinput></screen><para>Locales can have a number of synonyms, e.g. <quote>ISO-8859-1</quote> isalso referred to as <quote>iso8859-1</quote> and <quote>iso88591</quote>.Some applications cannot handle the various synonyms correctly, so it is safestto choose the canonical name for a particular locale.  To determine thecanonical name, run the following command, where<replaceable>[locale name]</replaceable> is the output given by<command>locale -a</command> for your preferred locale(<quote>en_GB.iso88591</quote> in our example).</para><screen><userinput>LC_ALL=<replaceable>[locale name]</replaceable> locale charmap</userinput></screen><para>For the <quote>en_GB.iso88591</quote> locale, the above commandwill print:</para><screen>ISO-8859-1</screen><para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.</para><para>Once the proper locale settings have been determined, create the<filename>/etc/profile</filename> file:</para><screen><userinput>cat > /etc/profile << "EOF"<literal># Begin /etc/profileexport LANG=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>.<replaceable>[charmap]</replaceable>export INPUTRC=/etc/inputrc# End /etc/profile</literal>EOF</userinput></screen><note><para>The <quote>C</quote> (default) and <quote>en_US</quote>(the recommended one for United States English users) locales aredifferent.</para></note><para>Setting the keyboard layout, screen font, and locale-related environment variables are the only internationalizationsteps needed to support locales that use ordinary single-byteencodings and left-to-right writing direction. More complex cases(including UTF-8 based locales) require additional steps andadditional patches because many applications tend to not work properlyunder such conditions.  These steps and patches are not included inthe LFS book and such locales are not yet supported by LFS.</para></sect1>
 |