guessing that that thread name was like this one
it is a big " no-no" to use something like
"Can some1 help me ?!"
that will lead to it being removed
or moved to the "general" section
you might want to read the posting guide
-- see at the top of this page the link called " tutorials"
-- there is a section for this forum
"How To Ask a Question "
first cent dose not use "sudo"
"sudo" is NOT set up by default
so unless YOU configure it you can not use it
"sudo" if mis-configured CAN be and IS a VERY major security hole - so for that reason it is not used most of the time
( there are GOOD reasons to use it so it can be set up )
use " su " and the different command " su -" ( with a space then a dash )
also Vi is not installed by default "nano" is
for VI you might want to go to the vi web site and PRINT the "cheat sheet"
so assuming you DID set up "sudo" and did use vi to edit the NORMAL user .bashrc and royally messed it up
you edited the root file -- not good
there is NOTHING ( except a few theme settings ) that need to be touched in that folder
-- do not edit files in /root there is almost nothing there that needs editing
put this in it
# User specific aliases and functions
alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'
# Source global definitions
if [ -f /etc/bashrc ]; then
and ONLY that
there is almost NEVER any reason to login to cent AS root using the GUI
i only found one -- setting up a new install on the second reboot - on ONLY then
after that there is NO reason to login into Gnome AS ROOT --- do not do it .
if you can not become root you might have to boot into "single user mode"
during the 3 sec countdown at boot
hit "e" for edit
use the down arrow to navigate to the current boot line ( down arrow one time) and add a space and a 1 to the end of the grub kernel boot line and hit enter then "b" for boot
READ the onscreen instructions
that will be a TEXT only user less boot into root
-- text ONLY --
and next time if you need to make changes use /etc/bashrc -- that is the SYSTEM wide config file
but pay attention to the files WARNING
# System wide functions and aliases
# Environment stuff goes in /etc/profile
# It's NOT a good idea to change this file unless you know what you
# are doing. It's much better to create a custom.sh shell script in
# /etc/profile.d/ to make custom changes to your environment, as this
# will prevent the need for merging in future updates.