Changeset 384039a
- Timestamp:
- 05/22/2005 10:28:05 AM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 3ba3f58
- Parents:
- 481b3e8
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
gnome/add/gtkhtml.xml
r481b3e8 r384039a 28 28 29 29 <sect2 role="package"> 30 <title>Introduction to <application>GtkHTML</application></title>30 <title>Introduction to GtkHTML</title> 31 31 32 32 <para>The <application>GtkHTML</application> package contains a … … 68 68 69 69 <sect2 role="installation"> 70 <title>Installation of <application>GtkHTML</application></title>70 <title>Installation of GtkHTML</title> 71 71 72 72 <para>Install <application>GtkHTML</application> by running the following -
postlfs/config/profile.xml
r481b3e8 r384039a 20 20 help create an environment. Each file has a specific use and 21 21 may affect login and interactive environments differently. The files in 22 the <filename class="directory">/etc</filename> directory generally provide 22 the <filename class="directory">/etc</filename> directory generally provide 23 23 global settings. If an equivalent file exists in your home directory it may 24 24 override the global settings.</para> 25 25 26 26 <para>An interactive login shell is started after a successful login, using 27 <filename>/bin/login</filename>, by reading the <filename>/etc/passwd</filename> 28 file. This shell invocation normally reads <filename>/etc/profile</filename> 29 and its private equivalent <filename>~/.bash_profile</filename> upon 27 <filename>/bin/login</filename>, by reading the <filename>/etc/passwd</filename> 28 file. This shell invocation normally reads <filename>/etc/profile</filename> 29 and its private equivalent <filename>~/.bash_profile</filename> upon 30 30 startup.</para> 31 31 … … 48 48 interactive login shell.</para> 49 49 50 <para>To the standard files, <filename>/etc/bashrc</filename> is called from 51 the user's <filename>~/.bashrc</filename> for system wide initialization of 50 <para>To the standard files, <filename>/etc/bashrc</filename> is called from 51 the user's <filename>~/.bashrc</filename> for system wide initialization of 52 52 non-login shells.</para> 53 53 54 <para>For more information see <command>info bash</command> -- 54 <para>For more information see <command>info bash</command> -- 55 55 <emphasis role="strong">Nodes: Bash Startup Files and Interactive 56 56 Shells.</emphasis></para> … … 66 66 setting up some helper functions and some basic parameters. It specifies some 67 67 <filename>bash</filename> history parameters and, for security purposes, 68 disables keeping a permanent history file for the <systemitem 68 disables keeping a permanent history file for the <systemitem 69 69 class="username">root</systemitem> user. It also sets a 70 70 default user prompt. It then calls small, single purpose scripts in the … … 82 82 # by James Robertson <jameswrobertson@earthlink.net> 83 83 # modifications by Dagmar d'Surreal <rivyqntzne@pbzpnfg.arg> 84 84 85 85 # System wide environment variables and startup programs. 86 86 87 87 # System wide aliases and functions should go in /etc/bashrc. Personal 88 88 # environment variables and startup programs should go into 89 89 # ~/.bash_profile. Personal aliases and functions should go into 90 90 # ~/.bashrc. 91 91 92 92 # Functions to help us manage paths. Second argument is the name of the 93 93 # path variable to be modified (default: PATH) … … 104 104 export $PATHVARIABLE="$NEWPATH" 105 105 } 106 106 107 107 pathprepend () { 108 108 pathremove $1 $2 … … 110 110 export $PATHVARIABLE="$1${!PATHVARIABLE:+:${!PATHVARIABLE}}" 111 111 } 112 112 113 113 pathappend () { 114 114 pathremove $1 $2 … … 116 116 export $PATHVARIABLE="${!PATHVARIABLE:+${!PATHVARIABLE}:}$1" 117 117 } 118 118 119 119 120 120 # Set the initial path … … 125 125 unset HISTFILE 126 126 fi 127 127 128 128 # Setup some environment variables. 129 129 export HISTSIZE=1000 … … 131 131 #export PS1="[\u@\h \w]\\$ " 132 132 export PS1='\u@\h:\w\$ ' 133 133 134 134 for script in /etc/profile.d/*.sh ; do 135 135 if [ -r $script ] ; then … … 137 137 fi 138 138 done 139 139 140 140 # Now to clean up 141 unset pathremove pathprepend pathappend 141 unset pathremove pathprepend pathappend 142 142 143 143 # End /etc/profile</literal> … … 151 151 </indexterm> 152 152 153 <para>Now create the <filename class='directory'>/etc/profile.d</filename> 153 <para>Now create the <filename class='directory'>/etc/profile.d</filename> 154 154 directory, where the individual initialization scripts are placed.</para> 155 155 … … 175 175 if [ -f "/etc/dircolors" ] ; then 176 176 eval $(dircolors -b /etc/dircolors) 177 177 178 178 if [ -f "$HOME/.dircolors" ] ; then 179 179 eval $(dircolors -b $HOME/.dircolors) … … 193 193 194 194 <para>This script adds several useful paths to the <envar>PATH</envar> and 195 <envar>PKG_CONFIG_PATH</envar> environment variables. If you want, you 196 can uncomment the last section to put a dot at the end of your path. This will 197 allow executables in the current working directory to be executed without 198 specifiying a ./, however you are warned that this is generally considered a 195 <envar>PKG_CONFIG_PATH</envar> environment variables. If you want, you 196 can uncomment the last section to put a dot at the end of your path. This will 197 allow executables in the current working directory to be executed without 198 specifiying a ./, however you are warned that this is generally considered a 199 199 security hazard.</para> 200 200 201 201 <screen role="root"><userinput>cat > /etc/profile.d/extrapaths.sh << "EOF" 202 202 <literal>if [ -d /usr/local/lib/pkgconfig ] ; then … … 232 232 </indexterm> 233 233 234 <para>This script sets up the default <filename>inputrc</filename> 235 configuration file. If the user does not have individual settings, it uses the 234 <para>This script sets up the default <filename>inputrc</filename> 235 configuration file. If the user does not have individual settings, it uses the 236 236 global file.</para> 237 237 … … 253 253 </indexterm> 254 254 255 <para>Some applications need a specific <envar>TERM</envar> setting to 255 <para>Some applications need a specific <envar>TERM</envar> setting to 256 256 support color.</para> 257 257 258 258 <screen role="root"><userinput>cat > /etc/profile.d/tinker-term.sh << "EOF" 259 <literal># This will tinker with the value of TERM in order to convince certain 259 <literal># This will tinker with the value of TERM in order to convince certain 260 260 # apps that we can, indeed, display color in their window. 261 261 262 262 if [ -n "$COLORTERM" ]; then 263 263 export TERM=xterm-color 264 264 fi 265 265 266 266 if [ "$TERM" = "xterm" ]; then 267 267 export TERM=xterm-color … … 277 277 <primary sortas="e-etc-profile.d-umask.sh">/etc/profile.d/umask.sh</primary> 278 278 </indexterm> 279 280 <para>Setting the <command>umask</command> value is important for security. 281 Here the default group write permissions are turned off for system users and when 279 280 <para>Setting the <command>umask</command> value is important for security. 281 Here the default group write permissions are turned off for system users and when 282 282 the user name and group name are not the same.</para> 283 283 … … 300 300 </indexterm> 301 301 302 <para>If <application>X</application> is installed, the <envar>PATH</envar> 302 <para>If <application>X</application> is installed, the <envar>PATH</envar> 303 303 and <envar>PKG_CONFIG_PATH</envar> variables are also updated.</para> 304 304 … … 321 321 </indexterm> 322 322 323 <para>This script shows an example of a different way of setting the prompt. 324 The normal variable, <envar>PS1</envar>, is supplemented by 325 <envar>PROMPT_COMMAND</envar>. If set, the value of 326 <envar>PROMPT_COMMAND</envar> is executed as a command prior to 323 <para>This script shows an example of a different way of setting the prompt. 324 The normal variable, <envar>PS1</envar>, is supplemented by 325 <envar>PROMPT_COMMAND</envar>. If set, the value of 326 <envar>PROMPT_COMMAND</envar> is executed as a command prior to 327 327 issuing each primary prompt.</para> 328 328 329 329 <screen role="root"><userinput>cat > /etc/profile.d/xterm-titlebars.sh << "EOF" 330 330 <literal># The substring match ensures this works for "xterm" and "xterm-xfree86". … … 338 338 339 339 <sect3 id="i18n.sh"> 340 <title> <filename>/etc/profile.d/i18n.sh</filename></title>340 <title>'/etc/profile.d/i18n.sh'</title> 341 341 342 342 <indexterm zone="postlfs-config-profile i18n.sh"> … … 344 344 </indexterm> 345 345 346 <para>This script shows how to set some environment variables necessary for 347 native language support. Setting these variables properly gives you:</para> 346 <para>This script shows how to set some environment variables necessary for 347 native language support. Setting these variables properly gives you:</para> 348 348 349 349 <itemizedlist> … … 352 352 </listitem> 353 353 <listitem> 354 <para>correct classification of characters into letters, digits and 355 other classes – this is necessary for <application>Bash</application> 354 <para>correct classification of characters into letters, digits and 355 other classes – this is necessary for <application>Bash</application> 356 356 to accept keystrokes properly in non-English locales</para> 357 357 </listitem> … … 367 367 </itemizedlist> 368 368 369 <para>Replace <replaceable>[ll]</replaceable> with the two-letter code for 370 your language (e.g., <quote>en</quote>) and 371 <replaceable>[CC]</replaceable> with the two-letter code for your country 372 (e.g., <quote>GB</quote>). Also you may need to specify (and this is actually 373 the preferred form) your character encoding (e.g., <quote>iso8859-1</quote>) 374 after a dot (so that the result is <quote>en_GB.iso8859-1</quote>). Issue the 369 <para>Replace <replaceable>[ll]</replaceable> with the two-letter code for 370 your language (e.g., <quote>en</quote>) and 371 <replaceable>[CC]</replaceable> with the two-letter code for your country 372 (e.g., <quote>GB</quote>). Also you may need to specify (and this is actually 373 the preferred form) your character encoding (e.g., <quote>iso8859-1</quote>) 374 after a dot (so that the result is <quote>en_GB.iso8859-1</quote>). Issue the 375 375 following command for more information:</para> 376 376 377 377 <screen><userinput>man 3 setlocale</userinput></screen> 378 378 379 <para>The list of all locales supported by <application>Glibc</application> 379 <para>The list of all locales supported by <application>Glibc</application> 380 380 can be obtained by running the following command:</para> 381 381 382 <screen><userinput>locale -a</userinput></screen> 383 384 <para>After you are sure about your locale settings, create the 385 <filename>/etc/profile.d/i18n.sh</filename> file:</para> 386 382 <screen><userinput>locale -a</userinput></screen> 383 384 <para>After you are sure about your locale settings, create the 385 <filename>/etc/profile.d/i18n.sh</filename> file:</para> 386 387 387 <screen role="root"><userinput>cat > /etc/profile.d/i18n.sh << "EOF" 388 388 <literal># Set up i18n variables … … 392 392 EOF</userinput></screen> 393 393 394 <para>The <envar>LC_ALL</envar> variable sets the same value for all locale 395 categories. For better control, you may prefer to set values individually for 396 all categories listed in the output of the <command>locale</command> 394 <para>The <envar>LC_ALL</envar> variable sets the same value for all locale 395 categories. For better control, you may prefer to set values individually for 396 all categories listed in the output of the <command>locale</command> 397 397 command.</para> 398 398 399 399 <para>The <envar>G_FILENAME_ENCODING</envar> variable tells applications 400 such as <application>Glib</application> and <application>GTK+</application> 400 such as <application>Glib</application> and <application>GTK+</application> 401 401 that filenames are in the default locale encoding and not in UTF-8 as 402 402 assumed by default.</para> … … 407 407 <title>Other Initialization Values</title> 408 408 409 <para>Other initialization can easily be added to the 410 <filename>profile</filename> by adding additional scripts to the 409 <para>Other initialization can easily be added to the 410 <filename>profile</filename> by adding additional scripts to the 411 411 <filename class='directory'>/etc/profile.d</filename> directory.</para> 412 412 … … 426 426 427 427 <screen role="root"><userinput>cat > /etc/bashrc << "EOF" 428 <literal># Begin /etc/bashrc 429 # Written for Beyond Linux From Scratch 428 <literal># Begin /etc/bashrc 429 # Written for Beyond Linux From Scratch 430 430 # by James Robertson <jameswrobertson@earthlink.net> 431 431 # updated by Bruce Dubbs <bdubbs@linuxfromscratch.org> … … 455 455 # Provides prompt for non-login shells, specifically shells started 456 456 # in the X environment. [Review the LFS archive thread titled 457 # PS1 Environment Variable for a great case study behind this script 457 # PS1 Environment Variable for a great case study behind this script 458 458 # addendum.] 459 459 … … 478 478 permissions after the command is run. You can then copy 479 479 <filename>/etc/skel/.bash_profile</filename> to the home directories of already 480 existing users, including <systemitem class="username">root</systemitem>, 480 existing users, including <systemitem class="username">root</systemitem>, 481 481 and set the owner and group appropriately.</para> 482 482 … … 500 500 if [ "$DIR" != "$1" ]; then 501 501 NEWPATH=${NEWPATH:+$NEWPATH:}$DIR 502 fi 502 fi 503 503 done 504 504 505 505 # Then append the directory 506 506 export PATH=$NEWPATH:$1 … … 512 512 513 513 if [ -d "$HOME/bin" ] ; then 514 append $HOME/bin 514 append $HOME/bin 515 515 fi 516 516 … … 521 521 522 522 </sect2> 523 523 524 524 <sect2 id="bashrc-profile"> 525 525 <title>~/.bashrc</title> … … 544 544 # ~/.bash_profile. System wide environment variables and startup 545 545 # programs are in /etc/profile. System wide aliases and functions are 546 # in /etc/bashrc. 546 # in /etc/bashrc. 547 547 548 548 if [ -f "/etc/bashrc" ] ; then … … 554 554 555 555 </sect2> 556 557 556 557 558 558 <sect2 id="bash_logout-profile"> 559 559 <title>~/.bash_logout</title> … … 579 579 580 580 </sect2> 581 582 581 582 583 583 <sect2 id="etc-dircolors-profile"> 584 584 <title>/etc/dircolors</title> … … 595 595 run the following command. The <filename class="directory">/etc/skel</filename> 596 596 setup steps seen above also can be used here to provide a 597 <filename>~/.dircolors</filename> file when a new user is set up. As before, 597 <filename>~/.dircolors</filename> file when a new user is set up. As before, 598 598 just change the output file name on the following command and assure the 599 permissions, owner, and group are correct on the files created and/or 599 permissions, owner, and group are correct on the files created and/or 600 600 copied.</para> 601 601 … … 603 603 604 604 <para>If you wish to customize the colors used for different file types, you can 605 edit the <filename>/etc/dircolors</filename> file. The instructions for setting 605 edit the <filename>/etc/dircolors</filename> file. The instructions for setting 606 606 the colors are embedded in the file.</para> 607 607 -
xsoft/graphweb/dillo.xml
r481b3e8 r384039a 21 21 </sect1info> 22 22 23 <title> <application>Dillo</application>-&dillo-version;</title>23 <title>Dillo-&dillo-version;</title> 24 24 25 25 <indexterm zone="dillo">
Note:
See TracChangeset
for help on using the changeset viewer.