bash-3.00$: to rasputin~$: ?

[rabbit]

I want my term to tell me pwd in my display, not bash-3.00$ like it does.  I KNOW it's around here, but I can't find where whoever said how said it ><

[iago]

It depends how you are opening your terminal.  I think in KDE and Gnome there's an option, on the properties page for the shortcut to the terminal, or maybe on the terminal itself, to open the terminal as a "login shell".  Enable that. 

If you're directly running xterm, run it with the "-ls" parameter. 

[Ergot]

I think I fixed it by adding "source /etc/profile" to ~/.bash_profile

[iago]

I think I fixed it by adding "source /etc/profile" to ~/.bash_profile

That's not the best way to do it, /etc/profile is run when a login shell is started, and bash_profile is run when bash is started. Those aren't the same thing, technically. 

[nslay]

I want my term to tell me pwd in my display, not bash-3.00$ like it does.  I KNOW it's around here, but I can't find where whoever said how said it ><

Do
export PS1="[\u@\h \w]\$ "

EDIT: Can add it to ~/.bashrc too

[Sidoh]

I always do

echo "source /etc/profile" > ~/.bashrc

Works fine for me.

Edit: Oh, also, anyone know how to do this with redhat linux?  I was messing around with it for a while last night and got it to work, but how do you make the shell update some variable with the working directory every time you change it?  I was doing pwd, but that is a static ~, obviously.

[iago]

I always do

echo "source /etc/profile" > ~/.bashrc

Works fine for me.

Edit: Oh, also, anyone know how to do this with redhat linux?  I was messing around with it for a while last night and got it to work, but how do you make the shell update some variable with the working directory every time you change it?  I was doing pwd, but that is a static ~, obviously.

You can probably do it the way I suggested, make the shell a login shell.  Either edit the shortcut, or run xterm with -ls. 

[Sidoh]

I want this to work with ssh too.  I don't think that will work with it?  I found their login script (it's ~/.cshrc), and the variable defining the prompt syntax (set prompt=""). Do I need to fix that?

[iago]

With csh, things are different.  You should switch to bash (chsh)

[Sidoh]

With csh, things are different.  You should switch to bash (chsh)

These are public lab computers they open SSH access to.  I'd love to switch to bash, since that's what I'm familiar with.  I've tried to use for, do, etc a few times and it throws errors!  Is there a way to change it for one user?

[iago]

Generally, to change it for youself, run chsh. 

If you have admin access, you can do it yourself by editing /etc/passwd.

[Sidoh]

Generally, to change it for youself, run chsh. 

If you have admin access, you can do it yourself by editing /etc/passwd.

Where is chsh located?  I'm asuming its somewhere specified in PATH so I don't have to worry about it?

I don't have admin access.

Thanks, iago.

Just tried it.

Code: [Select]

[mullins@grays ~]$ chsh
chsh: can only change local entries; use ypchsh instead.
[mullins@grays ~]$ locate ypchsh
/usr/share/man/man1/ypchsh.1.gz
/usr/share/man/ja/man1/ypchsh.1.gz
/usr/bin/ypchsh
[mullins@grays ~]$ ypchsh
Changing NIS account information for mullins on bach.cs.colostate.edu.
Please enter password:

Changing login shell for mullins on bach.cs.colostate.edu.
To accept the default, simply press return. To use the
system's default shell, type the word "none".
Login shell [/usr/local/bin/tcsh]: /usr/bin/ypchsh
Error while changing the login shell.
The login shell has not been changed on bach.cs.colostate.edu.

Am I doint something incorrectly?

[iago]

Login shell [/usr/local/bin/tcsh]: /usr/bin/ypchsh
Error while changing the login shell.



At that point, you want to give it the path to bash.  For a list of installed shells + paths, check /etc/shells.

[Sidoh]

Oh!  Haha.

Code: [Select]

[mullins@grays ~]$ grep "bash" /etc/shells
/bin/bash
/usr/local/bin/bash
[mullins@grays ~]$ ypchsh
Changing NIS account information for mullins on bach.cs.colostate.edu.
Please enter password:

Changing login shell for mullins on bach.cs.colostate.edu.
To accept the default, simply press return. To use the
system's default shell, type the word "none".
Login shell [/usr/local/bin/tcsh]: /usr/local/bin/bash
Error while changing the login shell.
The login shell has not been changed on bach.cs.colostate.edu.

[mullins@grays ~]$ ypchsh
Changing NIS account information for mullins on bach.cs.colostate.edu.
Please enter password:

Changing login shell for mullins on bach.cs.colostate.edu.
To accept the default, simply press return. To use the
system's default shell, type the word "none".
Login shell [/usr/local/bin/tcsh]: /bin/bash
Error while changing the login shell.
The login shell has not been changed on bach.cs.colostate.edu.

Am I doing something incorrectly?

Oh, also:

Code: [Select]

[mullins@grays ~]$ /usr/local/bin/bash
cat: /etc/HOSTNAME: No such file or directory
mullins@grays:~$                   

[nslay]

Oh!  Haha.

Code: [Select]

[mullins@grays ~]$ grep "bash" /etc/shells
/bin/bash
/usr/local/bin/bash
[mullins@grays ~]$ ypchsh
Changing NIS account information for mullins on bach.cs.colostate.edu.
Please enter password:

Changing login shell for mullins on bach.cs.colostate.edu.
To accept the default, simply press return. To use the
system's default shell, type the word "none".
Login shell [/usr/local/bin/tcsh]: /usr/local/bin/bash
Error while changing the login shell.
The login shell has not been changed on bach.cs.colostate.edu.

[mullins@grays ~]$ ypchsh
Changing NIS account information for mullins on bach.cs.colostate.edu.
Please enter password:

Changing login shell for mullins on bach.cs.colostate.edu.
To accept the default, simply press return. To use the
system's default shell, type the word "none".
Login shell [/usr/local/bin/tcsh]: /bin/bash
Error while changing the login shell.
The login shell has not been changed on bach.cs.colostate.edu.

Am I doing something incorrectly?

Oh, also:

Code: [Select]

[mullins@grays ~]$ /usr/local/bin/bash
cat: /etc/HOSTNAME: No such file or directory
mullins@grays:~$                   

try executing:
which bash
or
whereis bash

Chances are, it might not have bash.

EDIT: Oh yeah, try executing ps to see if you're running bash.
It might have bash on some remote mount ... I know, for example SDF has some of their utilities mounted on NFS and that to chsh you have to ssh to their file server to do it.

[Sidoh]

No, it has bash.  Notice how I was able to launch it?  I just had ~/.bashrc containing a "link" to /etc/profile on a slackware box, so some things there weren't expected, but here's the output for you anyway:

Code: [Select]

[mullins@grays ~]$ bash
bash-3.00$ exit
exit
[mullins@grays ~]$ which bash; whereis bash
/bin/bash
bash: /bin/bash /usr/local/bin/bash.OBSOLETE /usr/local/bin/bash /usr/share/man/man1/bash.1.gz


Code: [Select]

[mullins@grays ~]$ ypchsh
Changing NIS account information for mullins on bach.cs.colostate.edu.
Please enter password:

Changing login shell for mullins on bach.cs.colostate.edu.
To accept the default, simply press return. To use the
system's default shell, type the word "none".
Login shell [/usr/local/bin/tcsh]: none
Error while changing the login shell.
The login shell has not been changed on bach.cs.colostate.edu.

I don't think I have access to change it.  Maybe I can just launch bash when I first log in?

Edit: seems to work fine doing that.  I just have to type "exit" twice. >_>

Code: [Select]

sidoh@muaddib:~$ ssh mullins@grays
mullins@grays's password:
Last login: Tue Sep  5 14:20:54 2006 from inge068209.halls.colostate.edu

+-----------------------------------------------------------------------------+
| For system policies, information, and answers to frequently asked questions |
| see:                                                                        |
|                                                                             |
|       http://www.cs.colostate.edu/~info/faq.html                            |
|                                                                             |
| To report systems problems or to request the recovery of accidentally
| deleted files, see:
|                                                                             |
|       http://www.cs.colostate.edu/cgi-bin/trouble.pl
|                                                                             |
| Use /usr/local/bin/npasswd to change your password.  (The old commands,     |
| passwd and yppasswd, have been disabled.)                                   |
+-----------------------------------------------------------------------------+

mullins@grays:~$ echo $SHELL
/bin/bash
mullins@grays:~$ cat ~/.cshrc
/bin/bash
mullins@grays:~$ grep "/bin/bash" ~/profile
export SHELL="/bin/bash"


[nslay]

No, it has bash.  Notice how I was able to launch it?  I just had ~/.bashrc containing a "link" to /etc/profile on a slackware box, so some things there weren't expected, but here's the output for you anyway:

Code: [Select]

[mullins@grays ~]$ bash
bash-3.00$ exit
exit
[mullins@grays ~]$ which bash; whereis bash
/bin/bash
bash: /bin/bash /usr/local/bin/bash.OBSOLETE /usr/local/bin/bash /usr/share/man/man1/bash.1.gz


Code: [Select]

[mullins@grays ~]$ ypchsh
Changing NIS account information for mullins on bach.cs.colostate.edu.
Please enter password:

Changing login shell for mullins on bach.cs.colostate.edu.
To accept the default, simply press return. To use the
system's default shell, type the word "none".
Login shell [/usr/local/bin/tcsh]: none
Error while changing the login shell.
The login shell has not been changed on bach.cs.colostate.edu.

I don't think I have access to change it.  Maybe I can just launch bash when I first log in?

Edit: seems to work fine doing that.  I just have to type "exit" twice. >_>

Code: [Select]

sidoh@muaddib:~$ ssh mullins@grays
mullins@grays's password:
Last login: Tue Sep  5 14:20:54 2006 from inge068209.halls.colostate.edu

+-----------------------------------------------------------------------------+
| For system policies, information, and answers to frequently asked questions |
| see:                                                                        |
|                                                                             |
|       http://www.cs.colostate.edu/~info/faq.html                            |
|                                                                             |
| To report systems problems or to request the recovery of accidentally
| deleted files, see:
|                                                                             |
|       http://www.cs.colostate.edu/cgi-bin/trouble.pl
|                                                                             |
| Use /usr/local/bin/npasswd to change your password.  (The old commands,     |
| passwd and yppasswd, have been disabled.)                                   |
+-----------------------------------------------------------------------------+

mullins@grays:~$ echo $SHELL
/bin/bash
mullins@grays:~$ cat ~/.cshrc
/bin/bash
mullins@grays:~$ grep "/bin/bash" ~/profile
export SHELL="/bin/bash"


I know FSU requires us to email the Help Desk to have our shell changed.  Maybe you have to request a shell change from some authority too?

[Sidoh]

I would imagine so, but this seems to be a valid workaround for now?

[nslay]

I would imagine so, but this seems to be a valid workaround for now?

Yeah, that works, have tcsh execute bash on startup

[iago]

I don't know if it works on tcsh, but try running "exec bash" -- exec, if it works, replaces the current running process (ie, tcsh) with the new one (bash), so you only have to exit once.

[nslay]

Sidoh, I noticed on the motd that they have you use /usr/local/bin/npasswd to change the password.  Perhaps there is a /usr/local/bin/nchsh?

[rabbit]

Now my only problem is that it doesn't show # when I su to root

[Sidoh]

Sidoh, I noticed on the motd that they have you use /usr/local/bin/npasswd to change the password.  Perhaps there is a /usr/local/bin/nchsh?

Don't think so

Code: [Select]

mullins@grays:~$ ls /usr/local/bin/nchsh
ls: /usr/local/bin/nchsh: No such file or directory
mullins@grays:~$ whereis nchsh
nchsh:


I don't know if it works on tcsh, but try running "exec bash" -- exec, if it works, replaces the current running process (ie, tcsh) with the new one (bash), so you only have to exit once.

Code: [Select]

sidoh@muaddib:~$ ssh mullins@grays
mullins@grays's password:
Last login: Tue Sep  5 18:18:30 2006 from inge068209.halls.colostate.edu

+-----------------------------------------------------------------------------+
| For system policies, information, and answers to frequently asked questions |
| see:                                                                        |
|                                                                             |
|       http://www.cs.colostate.edu/~info/faq.html                            |
|                                                                             |
| To report systems problems or to request the recovery of accidentally
| deleted files, see:
|                                                                             |
|       http://www.cs.colostate.edu/cgi-bin/trouble.pl
|                                                                             |
| Use /usr/local/bin/npasswd to change your password.  (The old commands,     |
| passwd and yppasswd, have been disabled.)                                   |
+-----------------------------------------------------------------------------+

mullins@grays:~$ cat ~/.cshrc
exec /bin/bash
mullins@grays:~$ exit
exit
Connection to grays closed.

Excellent!  Thanks much, iago!

[Sidoh]

Haha.  When I got to class today, I logged into the same Linux box I was SSH'ing (grays, as you might have guessed) and FC4 bombed right after logging in.  At first, I thought my account was disabled for some strange reason and I was all freaked out.  About two seconds after that, though, I realized I was messing around with this last night.  I just replaced ~/.cshrc with the backup of the old one I made and appended it with exec /bin/bash and it works great.    I feel sorry for all of the suckers typing pwd.  What's the advantage csh has over bash?

[Newby]

What's the advantage csh has over bash?

As far as syntax, there isn't much. There are a few different built-in commands (man builtin I think...) but the syntax is the big difference.

[iago]

I don't know, but a lot of people love csh.  I seem to remember Tmp saying he likes it.   

[Newby]

By the way, if you wanted to use bash because it shows a directory in the prompt... you can do that to the prompt in csh too.

[Sidoh]

As far as syntax, there isn't much. There are a few different built-in commands (man builtin I think...) but the syntax is the big difference.

I know the syntax is different.  I was wondering if there were significant differences in performance, robustness, etc.

I don't know, but a lot of people love csh.  I seem to remember Tmp saying he likes it.  

Every computer in the Linux labs here uses it.  There must be something...

By the way, if you wanted to use bash because it shows a directory in the prompt... you can do that to the prompt in csh too.

I want this to work with ssh too.  I don't think that will work with it?  I found their login script (it's ~/.cshrc), and the variable defining the prompt syntax (set prompt=""). Do I need to fix that?

I'd love to switch to bash, since that's what I'm familiar with.  I've tried to use for, do, etc a few times and it throws errors!  Is there a way to change it for one user?

[Joe]

I'd love to switch to bash, since that's what I'm familiar with.  I've tried to use for, do, etc a few times and it throws errors!  Is there a way to change it for one user?

Excuse me for suggesting inefficiency here, but since ~/.cshrc is in your ~ directory, you could edit that for yourself. If I understand correctly, shells have no problem running shells on top of themselves. For example, in bash, you can type csh to run csh. The same principle can be reversed to run bash over csh, no?

[Sidoh]

Excuse me for suggesting inefficiency here, but since ~/.cshrc is in your ~ directory, you could edit that for yourself. If I understand correctly, shells have no problem running shells on top of themselves. For example, in bash, you can type csh to run csh. The same principle can be reversed to run bash over csh, no?

Read the rest of the topic.

[iago]

Excuse me for suggesting inefficiency here, but since ~/.cshrc is in your ~ directory, you could edit that for yourself. If I understand correctly, shells have no problem running shells on top of themselves. For example, in bash, you can type csh to run csh. The same principle can be reversed to run bash over csh, no?

Read the rest of the topic.

Yeah, that's almost exactly how he solved the problem, except that he's using "exec" instead of just running it. 

[Joe]

Oh. I replied at the end of page 1, I think. Well, at least that gives me the right to pat myself on the back knowing I recommended (nearly) the same thing as you pros.

[Sidoh]

Oh. I replied at the end of page 1, I think. Well, at least that gives me the right to pat myself on the back knowing I recommended (nearly) the same thing as you pros.

You also earn yourself a kick in the balls for not reading the next page of replies.

[Joe]

I earn myself a kick in the balls for not noticing* the next page of replies.

[Sidoh]

I earn myself a kick in the balls for not noticing* the next page of replies.

Which, in turn, led you to not reading the next page of replies.