Thank you. Last time, I added one line to ~/.bashrc. I added: “source settings32.sh” to ~/.bashrc. It went wrong (now I think that I did not give the right path for it to find the .lic file). Then, I commented that line. The catastrophe was OPENSUSE 12.3 booted, stayed my bash shell (but in purple color, not the regular black bash shell). No response to keystroke at all. The whole /home cannot be accessed. It halted there, no response to any key.
Could you tell me that I should work on this file (~/.bashrc) at what path in bash shell window? I don’t know whether it cares or not, but I do know it may be even worse than a kernel crash for an inappropriate editing on that file.
Here is the content. Could you see something relevant to the problem?
Copyright (c) 1995-2011 Xilinx, Inc. All rights reserved.
XIL_ARG_=$_
SETTINGS_FILE=.settings32.sh
XIL_SCRIPT_LOC=“/opt/Xilinx/13.2/ISE_DS”
if $# != 0 ]; then
The first argument is the location of Xilinx Installation.
Don’t detect the installation location.
XIL_SCRIPT_LOC=“$1”
else
XIL_SCRIPT_LOC should point to script location
if “$0” == “ksh” ]; then
XIL_SCRIPT_LOC_TMP_UNI=readlink -f ${XIL_ARG_}
else
XIL_SCRIPT_LOC_TMP_UNI=$BASH_SOURCE
fi
XIL_SCRIPT_LOC_TMP_UNI=${XIL_SCRIPT_LOC_TMP_UNI%/*}
if “$XIL_SCRIPT_LOC_TMP_UNI” != “” ]; then
if “$XIL_SCRIPT_LOC_TMP_UNI” == “settings32.sh” ]; then
XIL_SCRIPT_LOC_TMP_UNI=“./”
fi
XIL_SCRIPT_LOC_TMP_UNI=readlink -f ${XIL_SCRIPT_LOC_TMP_UNI}
if $? == 0 ]; then
XIL_SCRIPT_LOC=${XIL_SCRIPT_LOC_TMP_UNI}
fi
fi
unset XIL_SCRIPT_LOC_TMP_UNI
fi
common=“common”
newLst=“”
for i in /bin/ls "${XIL_SCRIPT_LOC}"
do
d=“${XIL_SCRIPT_LOC}/$i”
if -d “$d” ]; then
if $i != $common ]; then
newLst=“$newLst $i”
fi
fi
done
newLst=“$newLst $common”
XIL_SCRIPT_LOC_TMP_UNI=${XIL_SCRIPT_LOC}
for i in $newLst
do
d=“${XIL_SCRIPT_LOC_TMP_UNI}/$i”
sfn=“$d/$SETTINGS_FILE”
if -e “$sfn” ]; then
echo . “$sfn” “$d”
. “$sfn” “$d”
fi
done
And how did you add it to ~/.bashrc? Could you post that file as well, please?
lnusertmp normally only really can fail if you don’t have access rights to /tmp or /var/tmp or your / partition is full.
So please check the following:
But apparently settings32.sh sources another file called .settings32.sh, could you post that one as well?
And as Knurpht indicated, you could run the file from a different point.
I would recommend to set up KDE to run it on login:
“Configure Desktop”->“Launch and Shutdown”->Autostart. Click on “Add script…” and select that script.