NSLU2-Linux
view · edit · print · history

Optware.Bash History

Hide minor edits - Show changes to markup

October 07, 2014, at 03:03 PM by SRS -- bash_3.2.57
Changed lines 3-5 from:

October 4, 2014 The official bash_3.2.54-1_armeb.ipk feed now tested NOT-vulnerable although it does not include the 055 and 056 patches. So for that reason I'll leave link http://computerfixpro.com/shellshock-FIXed-056.zip for those who want that too. Anyone using the feed of bash_3.2.52-1_armeb.ipk or less should update. (bash_3.2.52 was compiled incorrectly and will fail all vulnerability testing!!!)

to:

October 7, 2014 The official bash_3.2.54-1_armeb.ipk feed now tested NOT-vulnerable although it does not include the 055, 056 and 057 patches. So for that reason I'll leave link http://computerfixpro.com/shellshock-FIXed-057.zip for those who want that too. Anyone using the feed of bash_3.2.52-1_armeb.ipk or less should update. (bash_3.2.52 was compiled incorrectly and will fail all vulnerability testing!!!)

October 04, 2014, at 07:23 AM by SRS -- shellshock
Changed lines 3-5 from:

October 1, 2014 The official bash_3.2.54-1_armeb.ipk feed now tested NOT-vulnerable although it does not include the parser-oob patch. So for that reason I'll leave link http://computerfixpro.com/shellshock-FIXed.zip for those who want that too. Anyone using the feed of bash_3.2.52-1_armeb.ipk or less should update. (bash_3.2.52 was compiled incorrectly and will fail all vulnerability testing!!!)

to:

October 4, 2014 The official bash_3.2.54-1_armeb.ipk feed now tested NOT-vulnerable although it does not include the 055 and 056 patches. So for that reason I'll leave link http://computerfixpro.com/shellshock-FIXed-056.zip for those who want that too. Anyone using the feed of bash_3.2.52-1_armeb.ipk or less should update. (bash_3.2.52 was compiled incorrectly and will fail all vulnerability testing!!!)

October 02, 2014, at 03:18 AM by SRS -- shellshock feed
Changed lines 3-24 from:

September 30, 2014 There seems to be bash_3.2.54-1_armeb.ipk on the official feed. I'll test it and post as soon as I can.

Here I post bash_3.2.55-1_armeb.ipk

  http://computerfixpro.com/shellshock-FIXed.zip 

The official feed is really really bad as if you check the actual binary from the bash_3.2.52-1_armeb.ipk you'll see it is EXACTLY binary equal to the old 3.2.49-1_armeb.ipk. I think what happened is that the bash32-05x patches were not copied to the ..\sources\bash\bash-3.2-patches\ directory as this has to be done manually as it is not in the bash.mk file. This was a serious mistake of the maintainer. So here you have the ipk, binary, .mk file and all the patches for shellshock.

 http://computerfixpro.com/shellshock-FIXed.zip

I have run all the shellshock vulnerability tests I could find and they all now pass. This .ipk is only for unslung so someone needs to contact the official maintainer to get the rest of optware done correctly since I have no idea who to contact.

to:

October 1, 2014 The official bash_3.2.54-1_armeb.ipk feed now tested NOT-vulnerable although it does not include the parser-oob patch. So for that reason I'll leave link http://computerfixpro.com/shellshock-FIXed.zip for those who want that too. Anyone using the feed of bash_3.2.52-1_armeb.ipk or less should update. (bash_3.2.52 was compiled incorrectly and will fail all vulnerability testing!!!)

October 01, 2014, at 12:21 AM by SRS -- shellshock
Changed line 3 from:

September 30, 2015

to:

September 30, 2014

October 01, 2014, at 12:13 AM by SRS -- shellshock
Added lines 3-5:

September 30, 2015 There seems to be bash_3.2.54-1_armeb.ipk on the official feed. I'll test it and post as soon as I can.

September 30, 2014, at 02:12 AM by SRS -- shellshock
Changed line 4 from:
  shellshock-FIXed.zip
to:
  http://computerfixpro.com/shellshock-FIXed.zip 
September 30, 2014, at 02:11 AM by SRS -- shellshock
Changed line 4 from:
  http://computerfixpro.com/shellshock-FIXed.zip
to:
  shellshock-FIXed.zip
September 30, 2014, at 01:45 AM by SRS -- shellshock
Changed lines 6-7 from:

binary from the bash_3.2.52-1_armeb-bkup.ipk you'll see it is EXACTLY binary equal to the old 3.2.49-1_armeb-bkup.ipk. I think what happened

to:

binary from the bash_3.2.52-1_armeb.ipk you'll see it is EXACTLY binary equal to the old 3.2.49-1_armeb.ipk. I think what happened

September 30, 2014, at 01:18 AM by SRS -- shellshock fix
Changed lines 1-2 from:

shellshock

to:

SHELLSHOCK

September 30, 2014, at 01:17 AM by SRS -- shellshock fix
Changed lines 1-2 from:

shellshock

to:

shellshock

Added lines 14-15:

I have run all the shellshock vulnerability tests I could find and they all now pass.

September 30, 2014, at 01:10 AM by SRS -- shellshock fix
Changed lines 1-3 from:

shellshock

Here I post bash_3.2.55-1_armeb.ipk http://computerfixpro.com/shellshock-FIXed.zip

to:

shellshock

Here I post bash_3.2.55-1_armeb.ipk

  http://computerfixpro.com/shellshock-FIXed.zip
Changed lines 12-13 from:

shellshock. http://computerfixpro.com/shellshock-FIXed.zip

to:

shellshock.

 http://computerfixpro.com/shellshock-FIXed.zip
September 30, 2014, at 01:09 AM by SRS -- shellshock fix
Added lines 1-17:

shellshock

Here I post bash_3.2.55-1_armeb.ipk http://computerfixpro.com/shellshock-FIXed.zip The official feed is really really bad as if you check the actual binary from the bash_3.2.52-1_armeb-bkup.ipk you'll see it is EXACTLY binary equal to the old 3.2.49-1_armeb-bkup.ipk. I think what happened is that the bash32-05x patches were not copied to the ..\sources\bash\bash-3.2-patches\ directory as this has to be done manually as it is not in the bash.mk file. This was a serious mistake of the maintainer. So here you have the ipk, binary, .mk file and all the patches for shellshock. http://computerfixpro.com/shellshock-FIXed.zip This .ipk is only for unslung so someone needs to contact the official maintainer to get the rest of optware done correctly since I have no idea who to contact.

October 23, 2008, at 03:22 PM by RalphFinch --
Added line 407:

See http://www.nslu2-linux.org/wiki/HowTo/RunAnotherShellForRootSafely for changing the root shell safely.

September 23, 2006, at 12:48 PM by Tobbe -- Moved the example .bash_profile to the Example files section and gave it the same styling as the other example files
Changed lines 25-26 from:

The .bash_profile is used during login.

to:

The .bash_profile is used during login. This file calls the .bashrc file.

Changed lines 35-40 from:
to:

Example files

These example files are severely cut down versions of the common standard bashrc files (http://www.tldp.org/LDP/abs/html/sample-bashrc.html#BASHRC) which work on the slug. The originals are a lot more sophisticated, but these are a pretty good starting point.

Changed lines 43-52 from:
    [ -f .bashrc ] && source .bashrc

Example files

These example files are severely cut down versions of the common standard bashrc files (http://www.tldp.org/LDP/abs/html/sample-bashrc.html#BASHRC) which work on the slug. The originals are a lot more sophisticated, but these are a pretty good starting point.

Example Global bashrc

Save this file as /opt/etc/bashrc

to:

Save this file as .bash_profile in the user's home folder (i.e. ~/)

Changed line 50 from:
  1. GLOBAL /opt/etc/bashrc FILE for bash-2.05a (or later)
to:
  1. PERSONAL $HOME/.bash_profile FILE
Deleted lines 51-54:
  1. This file is read (normally) by interactive shells only.
  2. Here is the place to define your aliases, functions and
  3. other features common to all user's bash sessions.
Changed lines 54-81 from:
to:
  1. -----------------------
  2. Load the .bashrc file
  3. -----------------------

[ -f .bashrc ] && source .bashrc

 =]

(:tableend:)

Example Global bashrc

Save this file as /opt/etc/bashrc

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 [=
  1. ===============================================================
  2. GLOBAL /opt/etc/bashrc FILE for bash-2.05a (or later)
  3. This file is read (normally) by interactive shells only.
  4. Here is the place to define your aliases, functions and
  5. other features common to all user's bash sessions.
  6. ===============================================================
September 22, 2006, at 02:12 PM by Tobbe --
Changed line 131 from:

===============================================================

to:
  1. ===============================================================
December 07, 2005, at 06:59 AM by Serge Rijkers --
Deleted line 371:
Added lines 374-380:

An issue related to no sftp login with the above ~/.bashrc file. This is caused by an interactive logon starting. My solution is to not parse the ~/.bashrc if the login is not interactive. Adding the line below to the beginning of the ~/.bashrc works for me.

# if not logging in interactively do nothing
[ -z "$PS1" ] && return

October 30, 2005, at 02:55 PM by Sebastian Meiss -- problems with line wrapping, incl. solution
Added lines 372-380:

I had some line wrapping problems with this color prompt. putting \[ and \] around the color codes within the prompt definition solved that problem:
change

PS1="${HILIT}//\h\w$NC# " ;;

to

PS1="\[${HILIT}\]//\h\w\[$NC\]# " ;;
September 17, 2005, at 11:13 PM by Chacko -- Adding solution
Added lines 369-371:

OK here is the solution: The above problem was caused by the echo statements in the ~/.bshrc file. When all of these were commented out, the sftp logon works now.

September 17, 2005, at 05:39 PM by Chacko --
Changed lines 364-368 from:

I had sftp and ssh available before installing and configuring bash for root. After install I cannot do sftp [but can ssh]. When starting my sftp client, I get the error: File transfer sercer could not be started or exited unexpectedly. Exit value 0 was returned. Most likely the sftp-server is not in the pat of the user on the server-side. I maually added the /opt/libexec to to the path, but this did not change the error. I can still sftp and ssh as another user which does not have the .bash configured.

to:

I had sftp and ssh available before installing and configuring bash for root. After install I cannot do sftp [but can ssh]. When starting my sftp client, I get the error:

File transfer server could not be started or exited unexpectedly. Exit value 0 was returned. Most likely the sftp-server is not in the pat of the user on the server-side.

Since then, I maually added the /opt/libexec to to the PATH in /etc/profile, but this did not change the error. BTW, I can still sftp and ssh as another user which does not have the .bash configured.

September 17, 2005, at 05:23 PM by Chacko -- ssh ftp not availiable after bash install
Changed lines 362-364 from:

I did a fresh install and did not get a libcurses error.

to:

I did a fresh install and did not get a libcurses error.


I had sftp and ssh available before installing and configuring bash for root. After install I cannot do sftp [but can ssh]. When starting my sftp client, I get the error: File transfer sercer could not be started or exited unexpectedly. Exit value 0 was returned. Most likely the sftp-server is not in the pat of the user on the server-side. I maually added the /opt/libexec to to the path, but this did not change the error. I can still sftp and ssh as another user which does not have the .bash configured.

August 05, 2005, at 06:01 PM by Mark -- answering questions
Changed lines 358-362 from:
to:

.bash_profile and .bashrc need to be created in a user's home directory (~/). They should be owned, readable and executable by that user.

I did a fresh install and did not get a libcurses error.

July 28, 2005, at 10:51 AM by MattMcNeill --
Changed lines 171-179 from:

echo -e "${CYAN}BASH ${RED}${BASH_VERSION%.*}$NC" echo -e "\n${RED}Machine information:$NC " ; uname -a

  1. echo -e "\n${RED}Users logged on:$NC " ; w -h

echo -e "\n${RED}Current date :$NC " ; date echo -e "\n${RED}Machine stats :$NC " ; uptime echo -e "\n${RED}Memory stats :$NC " ; free my_ip 2>&- ; echo -e "\n${RED}Free Disk Space :$NC" ; df echo

to:
  1. echo -e "${CYAN}BASH ${RED}${BASH_VERSION%.*}$NC"
July 28, 2005, at 10:40 AM by MattMcNeill -- Added sample bashrc files
Changed lines 40-123 from:
to:

Example files

These example files are severely cut down versions of the common standard bashrc files (http://www.tldp.org/LDP/abs/html/sample-bashrc.html#BASHRC) which work on the slug. The originals are a lot more sophisticated, but these are a pretty good starting point.

Example Global bashrc

Save this file as /opt/etc/bashrc

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
#===============================================================
#
# GLOBAL /opt/etc/bashrc FILE for bash-2.05a (or later)
#
# This file is read (normally) by interactive shells only.
# Here is the place to define your aliases, functions and
# other features common to all user's bash sessions.
#
#===============================================================


#-------------------------------------------------------------
# Automatic setting of $DISPLAY (if not set already)
# This works for linux - your mileage may vary....
# The problem is that different types of terminals give
# different answers to 'who am i'......
# I have not found a 'universal' method yet
#-------------------------------------------------------------

DISPLAY=${hostname}:0.0
export DISPLAY

#---------------
# Some settings
#---------------

ulimit -S -c 0          # Don't want any coredumps
set -o notify
set -o noclobber
set -o ignoreeof
set -o nounset
#set -o xtrace          # useful for debuging

# Enable options:
shopt -s cdspell
shopt -s cdable_vars
shopt -s checkhash
shopt -s checkwinsize
shopt -s mailwarn
shopt -s sourcepath
shopt -s no_empty_cmd_completion  # bash>=2.04 only
shopt -s cmdhist
shopt -s histappend histreedit histverify
shopt -s extglob        # necessary for programmable completion

# Disable options:
# shopt -u mailwarn
# unset MAILCHECK               # I don't want my shell to warn me of incoming mail


export TIMEFORMAT=$'\nreal %3R\tuser %3U\tsys %3S\tpcpu %P\n'
export HISTIGNORE="&:bg:fg:ll:h"
export HOSTFILE=$HOME/.hosts    # Put a list of remote hosts in ~/.hosts


#-----------------------
# Greeting, motd etc...
#-----------------------

# Define some colors first:
red='\e[0;31m'
RED='\e[1;31m'
blue='\e[0;34m'
BLUE='\e[1;34m'
cyan='\e[0;36m'
CYAN='\e[1;36m'
NC='\e[0m'              # No Color
# --> Nice. Has the same effect as using "ansi.sys" in DOS.

 

(:tableend:)

Changed lines 126-127 from:

See http://www.tldp.org/LDP/abs/html/sample-bashrc.html#BASHRC for a excellent example. Warning: this is not directly usable for the slug!

to:

Save this file as .bashrc in any normal user's home folder (i.e. ~/) it relies on the existence of the /opt/etc/bashrc file.

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
===============================================================
#
# PERSONAL $HOME/.bashrc FILE for bash-2.05a (or later)
#
# Last modified: Mon Jan 17 
#
# This file is read (normally) by interactive shells only.
# Here is the place to define your aliases, functions and
# other interactive features like your prompt.
#
# This file was designed (originally) for Solaris but based 
# on Redhat's default .bashrc file
# --> Modified for Linux.
# The majority of the code you'll find here is based on code found
# on Usenet (or internet).
# This bashrc file is a bit overcrowded - remember it is just
# just an example. Tailor it to your needs
# --> Tailored to be operable on the NLSU2 with Unslung 1.x 
#     onwards. It has been cut down somewhat from the original
#     sample found at:
#     http://www.tldp.org/LDP/abs/html/sample-bashrc.html#BASHRC
#
#===============================================================

#-----------------------------------
# Source global definitions (if any)
#-----------------------------------

if [ -f /opt/etc/bashrc ]; then
        . /opt/etc/bashrc   # --> Read /opt/etc/bashrc, if present.
fi


#-----------------------
# Greeting, motd etc...
#-----------------------

# Define some colors first (defined in /opt/etc/bashrc):

# Looks best on a black background.....
echo -e "${CYAN}BASH ${RED}${BASH_VERSION%.*}$NC"
echo -e "\n${RED}Machine information:$NC " ; uname -a
#echo -e "\n${RED}Users logged on:$NC " ; w -h
echo -e "\n${RED}Current date :$NC " ; date
echo -e "\n${RED}Machine stats :$NC " ; uptime
echo -e "\n${RED}Memory stats :$NC " ; free my_ip 2>&- ;
echo -e "\n${RED}Free Disk Space :$NC" ; df
echo

# function to run upon exit of shell
#function _exit()
#{
#    echo -e "${RED}Bye Bye${NC}"
#}
#trap _exit EXIT

#---------------
# Shell Prompt
#---------------

HILIT=${cyan}  # local machine: prompt will be partly cyan

#  --> Replace instances of \W with \w in prompt functions below
#  --> to get display of full path name.

function fastprompt()
{
    unset PROMPT_COMMAND
    case $TERM in
        *term | rxvt | linux )
            PS1="${HILIT}//\h\w$NC> " ;;
        *)
            PS1="//\h\w> " ;;
    esac
}

fastprompt

#-----------------------------------
# File & strings related functions:
#-----------------------------------

# Find a file with a pattern in name:
function ff() { find . -type f -iname '*'$*'*' -ls ; }
# Find a file with pattern $1 in name and Execute $2 on it:
function fe() { find . -type f -iname '*'$1'*' -exec "${2:-file}" {}\;  ; }

function ii()   # get current host related info
{
    echo -e "\nYou are logged on ${RED}$HOST"
    echo -e "\nAdditionnal information:$NC " ; uname -a
#    echo -e "\n${RED}Users logged on:$NC " ; w -h
    echo -e "\n${RED}Current date :$NC " ; date
    echo -e "\n${RED}Machine stats :$NC " ; uptime
    echo -e "\n${RED}Memory stats :$NC " ; free my_ip 2>&- ;
    echo -e "\n${RED}Local IP Address :$NC" ; echo ${MY_IP:-"Not connected"}
    echo -e "\n${RED}ISP Address :$NC" ; echo ${MY_ISP:-"Not connected"}
    echo -e "\n${RED}Free Disk Space :$NC" ; df
    echo
}


(:tableend:)

Example .bashrc for root

Save this file as .bashrc in the root user's home folder (i.e. /root/) it relies on the existence of the /opt/etc/bashrc file.

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
#===============================================================
#
# PERSONAL $HOME/.bashrc FILE for bash-2.05a (or later)
#
# Last modified: Mon Jan 17 
#
# This file is read (normally) by interactive shells only.
# Here is the place to define your aliases, functions and
# other interactive features like your prompt.
#
# This file was designed (originally) for Solaris but based 
# on Redhat's default .bashrc file
# --> Modified for Linux.
# The majority of the code you'll find here is based on code found
# on Usenet (or internet).
# This bashrc file is a bit overcrowded - remember it is just
# just an example. Tailor it to your needs
# --> Tailored to be operable on the NLSU2 with Unslung 1.x 
#     onwards. It has been cut down somewhat from the original
#     sample found at:
#     http://www.tldp.org/LDP/abs/html/sample-bashrc.html#BASHRC
#
#===============================================================

#-----------------------------------
# Source global definitions (if any)
#-----------------------------------

if [ -f /opt/etc/bashrc ]; then
        . /opt/etc/bashrc   # --> Read /opt/etc/bashrc, if present.
fi


#-----------------------
# Greeting, motd etc...
#-----------------------

# Define some colors first (defined in /opt/etc/bashrc):

# Looks best on a black background.....
echo -e "${CYAN}BASH ${RED}${BASH_VERSION%.*}$NC"
echo -e "\n${RED}Machine information:$NC " ; uname -a
#echo -e "\n${RED}Users logged on:$NC " ; w -h
echo -e "\n${RED}Current date :$NC " ; date
echo -e "\n${RED}Machine stats :$NC " ; uptime
echo -e "\n${RED}Memory stats :$NC " ; free my_ip 2>&- ;
echo -e "\n${RED}Free Disk Space :$NC" ; df
echo

# function to run upon exit of shell
#function _exit()
#{
#    echo -e "${RED}Bye Bye${NC}"
#}
#trap _exit EXIT

#---------------
# Shell Prompt
#---------------

HILIT=${RED}  # local machine: prompt will be partly red

#  --> Replace instances of \W with \w in prompt functions below
#  --> to get display of full path name.

function fastprompt()
{
    unset PROMPT_COMMAND
    case $TERM in
        *term | rxvt | linux )
            PS1="${HILIT}//\h\w$NC# " ;;
        *)
            PS1="//\h\w# " ;;
    esac
}

fastprompt

#-----------------------------------
# File & strings related functions:
#-----------------------------------

# Find a file with a pattern in name:
function ff() { find . -type f -iname '*'$*'*' -ls ; }
# Find a file with pattern $1 in name and Execute $2 on it:
function fe() { find . -type f -iname '*'$1'*' -exec "${2:-file}" {}\;  ; }

function ii()   # get current host related info
{
    echo -e "\nYou are logged on ${RED}$HOST"
    echo -e "\nAdditionnal information:$NC " ; uname -a
#    echo -e "\n${RED}Users logged on:$NC " ; w -h
    echo -e "\n${RED}Current date :$NC " ; date
    echo -e "\n${RED}Machine stats :$NC " ; uptime
    echo -e "\n${RED}Memory stats :$NC " ; free my_ip 2>&- ;
    echo -e "\n${RED}Local IP Address :$NC" ; echo ${MY_IP:-"Not connected"}
    echo -e "\n${RED}ISP Address :$NC" ; echo ${MY_ISP:-"Not connected"}
    echo -e "\n${RED}Free Disk Space :$NC" ; df
    echo
}

 

(:tableend:)

Added line 365:
June 04, 2005, at 03:02 PM by HF Manson -- link to /opt/etc/profile
Changed lines 30-35 from:
to:

This package comes with /opt/etc/profile. Use

    ln -s /opt/etc/profile /etc/profile

to activate it.

May 25, 2005, at 05:51 AM by Dietmar Zlabinger -- prompt example added
Changed lines 41-42 from:

Look at: http://www.tldp.org/HOWTO/Bash-Prompt-HOWTO

to:

A simple prompt (SuSE-style):

export PS1="\u@\h:\w/ > "
export PS2="> "

For details: look at: http://www.tldp.org/HOWTO/Bash-Prompt-HOWTO

April 18, 2005, at 12:16 PM by tman -- Split the error message so it wraps now.
Changed lines 48-50 from:

-bash: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory

to:

-bash: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory

April 17, 2005, at 07:45 PM by Dutch at nyquist-plot dot com --
Added lines 50-53:

////Note to maintainer: It might be helpful to noobies to include that the .bash_profile and .bashrc files need to be manually created and where one should create them. I found, via another page, that the .bash_profile goes in each user's home folder, but still haven't found where to put the .bashrc file. Other than that, the wiki seems pretty well thought out and is very helpful.

January 25, 2005, at 12:01 PM by perlguru --
Added lines 40-43:

The Prompt

Look at: http://www.tldp.org/HOWTO/Bash-Prompt-HOWTO


January 14, 2005, at 08:25 PM by RickardDahlstrand --
Changed lines 38-45 from:

See http://www.tldp.org/LDP/abs/html/sample-bashrc.html#BASHRC for a excellent example. Warning: this is not directly usable for the slug!

to:

See http://www.tldp.org/LDP/abs/html/sample-bashrc.html#BASHRC for a excellent example. Warning: this is not directly usable for the slug!

////Note to maintainer: It seems like bash needs curses, after installing bash and ssh on a fresh 3.17 I got this error when starting bash.

-bash: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory

January 11, 2005, at 01:06 AM by scott --
Changed line 11 from:
    echo "bash" >> /etc/shells
to:
    echo "/opt/bin/bash" >> /etc/shells
January 07, 2005, at 11:40 AM by perlguru --
Added lines 29-30:

During login the /etc/profile will also be executed (if it exists).

January 07, 2005, at 11:37 AM by perlguru --
Changed lines 1-36 from:

Describe {{Bash}} here.

to:

Installation

From the root prompt, type:

    ipkg install bash

Configuration

The /etc/shells

You can add bash to the /etc/shells file. Just simple do:

    echo "bash" >> /etc/shells

The /etc/passwd file

You can configure the default shell for a normal user: - Open the /etc/passwd file - Change the line of the normal user (myuser):

    myuser:*crypted*:2000:501:Normal User:/share/hdd/data/myuser:/opt/bin/bash

First login

Try now to login as the normal user.

The .bash_profile and .bashrc files

The .bash_profile is used during login.

The .bashrc is called when a bash process is started (not login)

Example .bash_profile

    [ -f .bashrc ] && source .bashrc

Example .bashrc

See http://www.tldp.org/LDP/abs/html/sample-bashrc.html#BASHRC for a excellent example. Warning: this is not directly usable for the slug!

Page last modified on October 07, 2014, at 03:03 PM