bash not reading ~/.bashrc
Why is it that when I switch to a text console with Ctl-Alt-F1 that bash does not read in my ~/.bashrc? When I pull up a terminal in X it works fine (all my command aliases are there). And when I log in to a text console, if explicitly type in the command 'bash' at the bash prompt, the new shell reads it in. But the top level shell from text login does not read it. Any ideas? -Roberto Sanchez _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash not reading ~/.bashrc
the ~/.bashrc file is read by non-login shells (i.e. xterm or eterm). the ~/.bash_profile file is read by login(1) when you log in to the console. jordan On Fri, 21 Feb 2003 16:53:07 -0500 Roberto Sanchez [EMAIL PROTECTED] wrote: Why is it that when I switch to a text console with Ctl-Alt-F1 that bash does not read in my ~/.bashrc? When I pull up a terminal in X it works fine (all my command aliases are there). And when I log in to a text console, if explicitly type in the command 'bash' at the bash prompt, the new shell reads it in. But the top level shell from text login does not read it. Any ideas? -Roberto Sanchez _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash not reading ~/.bashrc
Roberto Sanchez said: Why is it that when I switch to a text console with Ctl-Alt-F1 that bash does not read in my ~/.bashrc? I think .bashrc is for non-login shells? logging into a console or logging in via ssh/telnet/etc is a login shell. you probably want ~/.profile ? see the bash manpage nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash not reading ~/.bashrc
Roberto Sanchez wrote: Why is it that when I switch to a text console with Ctl-Alt-F1 that bash does not read in my ~/.bashrc? When I pull up a terminal in X it works fine (all my command aliases are there). And when I log in to a text console, if explicitly type in the command 'bash' at the bash prompt, the new shell reads it in. But the top level shell from text login does not read it. Any ideas? Depends exactly what you mean. Switching to a text console, by itself, does not cause bash to start running, so there's no reason it should read .bashrc then. If what you really mean is that .bashrc is not read when you login on a text console, then that's covered by bash's man page, which you really ought to read. .bash_profile or .profile is read by login shells; .bashrc is read only by non-login shells. If you want .bashrc to be read by all shells, then you need to put . ~./bashrc in your .bash_profile or .profile to make it happen. Craig pgp0.pgp Description: PGP signature
Re: bash not reading ~/.bashrc
If what you really mean is that .bashrc is not read when you login on a text console, then that's covered by bash's man page, which you really ought to read. .bash_profile or .profile is read by login shells; .bashrc is read only by non-login shells. If you want .bashrc to be read by all shells, then you need to put . ~./bashrc in your .bash_profile or .profile to make it happen. I have this in my .bash_profile. I think it was there, but commented out, by default. # Get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash, but no .bashrc??
Hi, here, users have different profiles etc.. So I'm using bash interractive. Change your /etc/profile like that: f [ $BASH ]; then # PS1='\u@\h:\w\$ ' bash -i else if [ `id -u` -eq 0 ]; then PS1='# ' else PS1='$ ' fi fi and your user .bashrc would be executed on login. mess-mate On Fri, 24 Jan 2003 15:52:53 -0500 Andy Estes [EMAIL PROTECTED] wrote: | I am running Debian Woody (3.0r1). The default shell for my user account is | bash, and I can verify this by typing 'ps' once I am logged on. However, | the contents of my .bashrc do not get executed by default. If I explicitely | invoke bash (typing 'bash' at the shell), .bashrc is executed properly, but | if I simply log in (locally or remotely), it doesn't happen. Can anyone | explain what is going on here? | | -Andy | | | -- | To UNSUBSCRIBE, email to [EMAIL PROTECTED] | with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] | -- Computers are like air conditioners, they are useless when you open Windows. msg26142/pgp0.pgp Description: PGP signature
bash, but no .bashrc??
I am running Debian Woody (3.0r1). The default shell for my user account is bash, and I can verify this by typing 'ps' once I am logged on. However, the contents of my .bashrc do not get executed by default. If I explicitely invoke bash (typing 'bash' at the shell), .bashrc is executed properly, but if I simply log in (locally or remotely), it doesn't happen. Can anyone explain what is going on here? -Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash, but no .bashrc??
On Fri, Jan 24, 2003 at 03:52:53PM -0500, Andy Estes wrote: I am running Debian Woody (3.0r1). The default shell for my user account is bash, and I can verify this by typing 'ps' once I am logged on. However, the contents of my .bashrc do not get executed by default. If I explicitely invoke bash (typing 'bash' at the shell), .bashrc is executed properly, but if I simply log in (locally or remotely), it doesn't happen. Can anyone explain what is going on here? if [ -f ~/.bashrc ]; then source ~/.bashrc fi Add that to your ~/.bash_profile -- :wq Matthew Daubenspeck http://www.oddprocess.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash, but no .bashrc??
On Fri, Jan 24, 2003 at 03:52:53PM -0500, Andy Estes wrote: I am running Debian Woody (3.0r1). The default shell for my user account is bash, and I can verify this by typing 'ps' once I am logged on. However, the contents of my .bashrc do not get executed by default. If I explicitely invoke bash (typing 'bash' at the shell), .bashrc is executed properly, but if I simply log in (locally or remotely), it doesn't happen. Can anyone explain what is going on here? 1) install the bash-doc package, then read the section about bash startup files in info bash 2) fix your problem with putting '. ~/.bashrc' (without the '') in ~/.bash_profile mfg, Stephen Rüger -- Jede Nation spottet über die andere, und alle haben recht. -- Schopenhauer msg26035/pgp0.pgp Description: PGP signature
Re: bash, but no .bashrc??
On Fri, Jan 24, 2003 at 03:52:53PM -0500, Andy Estes wrote: I am running Debian Woody (3.0r1). The default shell for my user account is bash, and I can verify this by typing 'ps' once I am logged on. However, the contents of my .bashrc do not get executed by default. If I explicitely invoke bash (typing 'bash' at the shell), .bashrc is executed properly, but if I simply log in (locally or remotely), it doesn't happen. Can anyone explain what is going on here? Take a look at ~/.bash_profile. ~/.bashrc is used for non-login shells. -- Seneca [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash, but no .bashrc??
On 24 January 2003 at 15:52, Andy Estes [EMAIL PROTECTED] wrote: I am running Debian Woody (3.0r1). The default shell for my user account is bash, and I can verify this by typing 'ps' once I am logged on. However, the contents of my .bashrc do not get executed by default. If I explicitely invoke bash (typing 'bash' at the shell), .bashrc is executed properly, but if I simply log in (locally or remotely), it doesn't happen. Can anyone explain what is going on here? You need to read the bash man page. Specifically, the section labelled INVOCATION. -- Stephen W. Juranich [EMAIL PROTECTED] Electrical Engineering http://students.washington.edu/sjuranic University of Washingtonhttp://ssli.ee.washington.edu/ssli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash, but no .bashrc??
On Fri, Jan 24, 2003 at 03:52:53PM -0500, Andy Estes wrote: I am running Debian Woody (3.0r1). The default shell for my user account is bash, and I can verify this by typing 'ps' once I am logged on. However, the contents of my .bashrc do not get executed by default. Uncomment the three lines in the default ~/.bash_profile that source ~/.bashrc; you'll see them. The reason this doesn't happen automatically is that some people like to keep login and non-login shells with separate startup files, while some people prefer them to be the same. See the INVOCATION section of 'man bash' for more. Cheers, -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash, but no .bashrc??
If I explicitely invoke bash (typing 'bash' at the shell), .bashrc is executed properly, but if I simply log in (locally or remotely), it doesn't happen. Can anyone explain what is going on here? When bash is invoked as login-shell, it executes the commandos in.bash_profile, if that exists (if not it searches for .bash_login and finally for .profile). .bashrc is not being looked at. To enable processing of your .bashrc, simply comment out the following lines in your .bash_profile: ## include .bashrc if it exists: #if [ -f ~/.bashrc ]; then #source ~/.bashrc #fi greetings, Johannes Zarl -- More than machinery we need humanity -- Charlie Chaplin, The Great Dictator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bash, but no .bashrc??
Hello aloow line . .bashrc on Ur's .bashr-profile or .rpofile file ! David Dumoerize -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
