My preference would be for my command-line prompt to display the absolute directory path to any directory I am working in.

What I need is a $/etc/bashrc PS1 script-entry that reads ---

PS1="\h \w \$"

I can set that value at the command-prompt of any session and have what I want.
But the setting "goes away" when the session closes.
I would like to have it permanently.

To do this I understand it will be necessary to modify the /etc/bashrc script file

My reading led me to think that use of the 'export' command with root authority would make that change permanently in the bashrc script file:

CODE: #export PS1="\h \w \$"

However it did not.

I then "went" to /etc and invoked #gedit bashrc

RETURNED:
============
root@localhost etc]# gedit bashrc

(gedit:20555): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported


** (gedit:20555): WARNING **: Could not connect to session bus
[root@localhost etc]#
=============

Yet when I invoked gedit bashrc as a mere USER --- the bashrc file displays in gedit and I am able to make the desired GEDIT changes, but am prevented from saving them.

At this point I coped out...
It was all just too scary...
I'm too much of a neophyte to be flying alone in these waters.

jwsmith

How did you become root ?
"su" will cause that error , it is using your normal users $PATH
" su - " is what you need to use . It is using root's $PATH

1 members found this post helpful.

John...I became root by entering the command: $su root plus pwd ...obtaining #(root commandline)
I know no other way...am comfortable (cautious) with root authority.

You seem to be asking that I invoke gedit by first entering the command

$su -

Wow....I just did that...it asked for the pwd....and then offered me the bashrc text.

So I guess I'm on my way...

But would you comment on this:
Within the text of bashrc is explicit warning not to alter bashrc.
Suggests that instead, changes to bashrc be made by creating a "custom.sh" script file in /etc/profile.d
STATES that an additional advantage in doing this, is that the change will survive subsequent Fedora upgrades.
My fairly old documentation: (Tim Parker "Linux Unleashed" 3rd Ed.) and newer(Mark Sobell "Practical Guide to Linux Commands, Editors & Shell Programming" 2nd Ed. -2010) do not give any guidance about the format that a "custom.sh" script file should take)
Do you recommend that I just alter the PS1 description within bashrc, or should I concern myself with creation of a custom.sh script file.

jwsmith

fallow the instructions in that warning

fedora changes VERY fast
With a new and sometimes VERY different version every 6 months
a fedora 18 book will be somewhat out of date by the time it is on the book shelf

a 3 year old book would be about 6 versions of fedora out of date

Now the basics ( mostly) do not change except for system-v VS. systemd and udev


as to ps1

do you wnat this system wide ?
or for just your user ?

i would recomend just your user
then a slightly different version for root
use say RED for root prompt , that way at a very quick glance you can tell

for your normal user
edit the .bashrc file in your home folder
just add this to the file
however "\h\w\$" might not be what you want , that will remove the user name
------
PS1="\u@\h:\w>\$"
------

might be a better option

see this web page
http://bashrcgenerator.com/

then for the .bashrc in the /root folder add this

1 members found this post helpful.

-- oops ---

1 members found this post helpful.

Instead of modifying /etc/bashrc file, modify individual files i.e. ~/.bashrc or ~/.profile for individual users.
Just do:
Then restart the session to take changes into effects.

1 members found this post helpful.

John and shivaa....

Thank you both, very much.

Judd