| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778 | <?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/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"?><para>The shell program <filename>/bin/bash</filename> (hereafterreferred to as just "the shell") uses a collection of startup files tohelp create an environment to run in.  Each file has a specific use andmay affect login and interactive environments differently.  The files inthe <filename class="directory">/etc</filename> directory generally provide globalsettings. If an equivalent file exists in your home directory it mayoverride the global settings.</para><para>An interactive login shell is started after a successful login, using<filename>/bin/login</filename>, by reading the<filename>/etc/passwd</filename> file.  Aninteractive non-login shell is started at the command-line (e.g.<prompt>[prompt]$</prompt><command>/bin/bash</command>).  A non-interactive shell is usually present when a shell script is running.  It is non-interactivebecause it is processing a script and not waiting for user input betweencommands.</para><para>For more information see <command>info bash</command> -- <emphasis role="strong">Nodes: Bash Startup Files and InteractiveShells.</emphasis></para><para>The files <filename>/etc/profile</filename> and<filename>~/.bash_profile</filename> are read when the shell is invokedas an interactive login shell.</para><para>A base <filename>/etc/profile</filename> created below only sets someenvironment variables necessary for Bash to accept keystrokes properly,even in non-English locale. Replace "ll" with thetwo-letter code for your language (e.g. "en") and"CC" with the two-letter code for your country(e.g. "GB"). Also you may need to specify(and this is actually the preferred form) yourcharacter encoding (e.g. "iso8859-1") after a dot (so that the resultis "en_GB.iso8859-1").Issue the following command for more information:</para><screen><userinput>man 3 setlocale</userinput></screen><para>The list of all locales supported by glibc can be obtained by runningthe following command:</para><screen><userinput>locale -a</userinput></screen><para>Now, when you are sure about your locale settings, create the<filename>/etc/profile</filename> file:</para><screen><userinput>cat > /etc/profile << "EOF"# Begin /etc/profile# Written for Linux From Scratch# by Alexander E. Patrakovexport LC_ALL=ll_CCexport LANG=ll_CCexport INPUTRC=/etc/inputrc# End /etc/profileEOF</userinput></screen><para>Setting the keyboard layout,the screen font and the locale-related environment variablesare the only internationalization steps needed to supportlocales that use ordinary single-byte encodings and left-to-rightwriting direction. More complex cases (including UTF-8 based locales)require additional steps and additional patches because many applicationstend to break in such conditions. Because of too little educationalvalue for a typical reader, these steps and patches are not includedin the LFS book and such locales are not supported by LFS in any way.</para></sect1>
 |