.bashrc

.bashrc

[gshang]

>First, I'm assuming bash is your assigned shell. Is this correct? To find
>out for sure do:
>
>        grep -i [your.username] /etc/passwd

It's easier to just do

echo $SHELL

>.bashrc -- These are settings exectued whenever you login, meaning you in
>particular, and not some other username. These are executed whether you
>login locally on a console, or over the Internet perhaps using ssh;
>
>.bash_profile -- These commands are executed only when you log in on a
>local console;

This is not correct.  I do not have any commands in my .bashrc file, they 
are all in .bash_profile and they get executed no matter how I login.  
Linux generally doesn't care if you're local or not.

As stated earlier, .bashrc is run by bash for shells launched later 
whereas .bash_profile is run when you log in.

Geoff.

Re: .bashrc

[Janina Sajka]

Geoff:

It is true that both /etc/profile and $HOME/.profile are sourced during 
login. However, I believe I am correct that .bash_profile is local console 
only.
 On Sun, 3 Feb 2002 gshang@uq.net.au wrote:

> >First, I'm assuming bash is your assigned shell. Is this correct? To find
> >out for sure do:
> >
> >        grep -i [your.username] /etc/passwd
> 
> It's easier to just do
> 
> echo $SHELL
> 
> >.bashrc -- These are settings exectued whenever you login, meaning you in
> >particular, and not some other username. These are executed whether you
> >login locally on a console, or over the Internet perhaps using ssh;
> >
> >.bash_profile -- These commands are executed only when you log in on a
> >local console;
> 
> This is not correct.  I do not have any commands in my .bashrc file, they 
> are all in .bash_profile and they get executed no matter how I login.  
> Linux generally doesn't care if you're local or not.
> 
> As stated earlier, .bashrc is run by bash for shells launched later 
> whereas .bash_profile is run when you log in.
> 
> Geoff.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

Re: .bashrc

[Janina Sajka]

I like the solution some of us on this list came up with a few wekks ago 
better. I think this started with Chuck. Saqib added the cool command 
syntax at the end:

1.)	Create a /etc/speakup;
2.)	Create a subdirectory in /etc/speakup for each of the synths 
available to you on your computer. If that's only one synth, that's OK;

3.)	Launch linux with each of your synths, one at a time. Tweak your 
setteings as you want them by default. Then do:

	cp -a /proc/speakup/* /etc/speakup/[synthname]
	chmod -R 755 /etc/speakup/*

NOTE:	You may delete any files in /etc/speakup/[yoursynth] that weren't 
modified by you as you set your defaults, but no damage if you don't;

4.)	Now for the cool part. Create an alias in one of your login files. 
I put the following in my .bash_profile:

alias s="cp /etc/speakup/`cat /proc/speakup/synth`/* /proc/speakup"
s

The first of these two lines defines an alias I've called "s" but you can 
call it anything you like, obviously. I guess I'm into terse aliases for 
commands I might want to give often. The second line calls this alias so 
that My defaults are set after I login. Thereafter, to return to defaults, 
I simply type s and press enter.

This works like a charm for me. Your mileage may vary, of course.



 On Sun, 3 Feb 2002, Shaun Oliver wrote:

> just a thought,
> try creating a .bash_profile file
> and adding the various speakup parameters in there.
> or better yet, make it part of the boot process.
> eg, try adding those speech lines to your /etc/rc.d/rc.local,
> or if you run a distribution such as debian,
> try creating a 2 or 3 line shell script in your /etc/init.d directory
> called speakup and make it executable and then create a symlink to it in
> /etc/rc2.d and call it something like S10speakup
> hth
> Shaun..
> On Sat, 2 Feb 2002,
> Richard Wells wrote:
> 
> > How do I get my user account to see the .bashrc in the account's directory
> > and execute any changes such as different speakup parameters? If i type
> > "bash" after I log in the .bashrc file loads configuration but if I don't,
> > it seems to be ignored.
> >
> > Thanks for help with this.
> >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> 

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

Re: .bashrc

[Thomas Ward]

Hi, usually I put all my speakup settings in the rc.local file. that way it
gets setup on startup, and is the same across all user accounts.

----- Original Message -----
From: Shaun Oliver <shauno@goanna.net.au>
To: <speakup@braille.uwo.ca>
Sent: Sunday, February 03, 2002 4:33 AM
Subject: Re: .bashrc


> just a thought,
> try creating a .bash_profile file
> and adding the various speakup parameters in there.
> or better yet, make it part of the boot process.
> eg, try adding those speech lines to your /etc/rc.d/rc.local,
> or if you run a distribution such as debian,
> try creating a 2 or 3 line shell script in your /etc/init.d directory
> called speakup and make it executable and then create a symlink to it in
> /etc/rc2.d and call it something like S10speakup
> hth
> Shaun..
> On Sat, 2 Feb 2002,
> Richard Wells wrote:
>
> > How do I get my user account to see the .bashrc in the account's
directory
> > and execute any changes such as different speakup parameters? If i type
> > "bash" after I log in the .bashrc file loads configuration but if I
don't,
> > it seems to be ignored.
> >
> > Thanks for help with this.
> >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> --
> Shaun Oliver
>
> Marriage is a three ring circus:
> engagement ring, wedding ring, and suffering.
>                 -- Roger Price
>
> Email: shauno@goanna.net.au
> Icq: 76958435
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

Re: .bashrc

[Shaun Oliver]

just a thought,
try creating a .bash_profile file
and adding the various speakup parameters in there.
or better yet, make it part of the boot process.
eg, try adding those speech lines to your /etc/rc.d/rc.local,
or if you run a distribution such as debian,
try creating a 2 or 3 line shell script in your /etc/init.d directory
called speakup and make it executable and then create a symlink to it in
/etc/rc2.d and call it something like S10speakup
hth
Shaun..
On Sat, 2 Feb 2002,
Richard Wells wrote:

> How do I get my user account to see the .bashrc in the account's directory
> and execute any changes such as different speakup parameters? If i type
> "bash" after I log in the .bashrc file loads configuration but if I don't,
> it seems to be ignored.
>
> Thanks for help with this.
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
Shaun Oliver

Marriage is a three ring circus:
engagement ring, wedding ring, and suffering.
                -- Roger Price

Email: shauno@goanna.net.au
Icq: 76958435

.bashrc

[gshang]

>It is true that both /etc/profile and $HOME/.profile are sourced during
>login. However, I believe I am correct that .bash_profile is local console
>only.

Not on my system.  I don't have a .profile, and my .bash_profile executes 
wherever I login from, after /etc/profile.  the other user on my system 
always uses it remotely and this is the case for her as well.

Geoff.

Re: .bashrc

[Janina Sajka]

Hi, Richard:

To learn what Redhat image does what, look at the yet unlinked 
installation howto at:

	http://www.linux-speakup.org/ftp/disks/redhat/HOWTO_INSTALL.html

The explanation of each of the 5 CDR images is in there.

As for csh and tcsh -- I haven't used them since the days of shell-based 
netcom. And, that's been a few years! <grin>

Point of fact, though, one can always jump back and forth as much as one 
wishes. Simply type bash or tcsh or zsh (for that matter) to change shells 
on the fly. You set your personal default in /etc/passwd
 On Sat, 2 Feb 
2002, Richard Wells wrote:

> Hi janina! You and Kirk gave me the answers I needed. Thank you very much for your complete explanation of how these configurations are handled by bash. Most of my Linux/Unix to this point has been on the shell side on Solaris but never on the system administrator or root side. I am playing with Slackware now but I may be switching to Redhat soon. I got five C images from the Speakup site. My main concern now is to know which one does which job.
> 
> While we're on the subject of bash and such, how do you feel about csh and tcsh? Some have told me that they are more powerful than bash. I would be interested in hearing pro and con on this from this group.
> 
> Thanks
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

Re: .bashrc

[Richard Wells]

Hi janina! You and Kirk gave me the answers I needed. Thank you very much for your complete explanation of how these configurations are handled by bash. Most of my Linux/Unix to this point has been on the shell side on Solaris but never on the system administrator or root side. I am playing with Slackware now but I may be switching to Redhat soon. I got five C images from the Speakup site. My main concern now is to know which one does which job.

While we're on the subject of bash and such, how do you feel about csh and tcsh? Some have told me that they are more powerful than bash. I would be interested in hearing pro and con on this from this group.

Thanks


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: .bashrc

[Dave Hunt]

How concise and helpful!  Thanks!

My default shell is bash; I like it.  

-Dave
On Sat, 2 Feb 2002, Janina Sajka 
wrote:

> Now, there are a chain of files involved in getting your environment set 
> up. There are system wide setup files in /etc, namely /etc/bashrc and 
> /etc/profile. Also, you have files in your home directory which set up 
> your shell environment. They're hidden files so you don't see them with a 
> simple ls. Instead do:
> 
> 	ls .bash*
> 
> You'll probably see:
...

Re: .bashrc

[Janina Sajka]

Hi, Dave:

First, I'm assuming bash is your assigned shell. Is this correct? To find 
out for sure do:

	grep -i [your.username] /etc/passwd

If your shell prompt is a $ sign (dollar sign), you're pretty likely in 
bash by default. That's usually the case these days.

Now, there are a chain of files involved in getting your environment set 
up. There are system wide setup files in /etc, namely /etc/bashrc and 
/etc/profile. Also, you have files in your home directory which set up 
your shell environment. They're hidden files so you don't see them with a 
simple ls. Instead do:

	ls .bash*

You'll probably see:

.bash_logout
.bashrc
.bash_profile
.bash_history
[

Briefly, here's what these are for:

.bash_logout -- as you might guess, these are commands executed when you 
logout with a Ctrl-d (or some such);

.bashrc -- These are settings exectued whenever you login, meaning you in 
particular, and not some other username. These are executed whether you 
login locally on a console, or over the Internet perhaps using ssh;
 
.bash_profile -- These commands are executed only when you log in on a 
local console;

.bash_history -- This is a cache of commands you've given to the system. 
This is how bash knows what commands you gave the last time you logged in. 
These are what you see when you use the up and down arrows;

Lastly, let me say that bash has a lot of wonderful features to offer. 
Bash scripts, for example, are even more powerful and capable than the 
batch programming language in DOS. To learn about bash, look for the 
Bash Prompt HOWTO available at:

http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Bash-Prompt-HOWTO.html

 [
 On Sat, 2 Feb 2002, Richard Wells wrote:

> So do I need to create a file in my user directory called .profile or profile to put the configurations I want into? There is still a lot I don't understand about this stuff yet.
> 
> Thanks
> 
> ----- Original Message ----- 
> From: "Dave Hunt" <wx1g@mediaone.net>
> To: <speakup@braille.uwo.ca>
> Sent: Saturday, February 02, 2002 2:59 PM
> Subject: Re: .bashrc
> 
> 
> Hi,
> 
> You could put "source .bashrc" in your account's ".profile".  Better., I 
> think, is to put those commands you want executed at login by the user in 
> question directly into her/his ".profile".  A user's ".bashrc" is for 
> shells launched after login, e. g. by "screen".
> 
> -Dave
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

Re: .bashrc

[Dave Hunt]

You can put a file in your user's home directory called ".profile".  If 
you used, for instance, the "adduser" script in Redhat, you get a stock 
".profile" in each user's directory, usually "/home/<username>".  The 
commands here are executed at login.  If you wish the commands to be run 
by all users at login, put them in "/etc/profile".  You should already 
have such a file.

-Dave

Re: .bashrc

[Kirk Reiser]

Hi Richard: .bashrc is used on non-login shells.  For shells you wish
to login on meaning just about all you want to edit .bash_profile.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: .bashrc

[Richard Wells]

So do I need to create a file in my user directory called .profile or profile to put the configurations I want into? There is still a lot I don't understand about this stuff yet.

Thanks

----- Original Message ----- 
From: "Dave Hunt" <wx1g@mediaone.net>
To: <speakup@braille.uwo.ca>
Sent: Saturday, February 02, 2002 2:59 PM
Subject: Re: .bashrc


Hi,

You could put "source .bashrc" in your account's ".profile".  Better., I 
think, is to put those commands you want executed at login by the user in 
question directly into her/his ".profile".  A user's ".bashrc" is for 
shells launched after login, e. g. by "screen".

-Dave



_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: .bashrc

[Dave Hunt]

Hi,

You could put "source .bashrc" in your account's ".profile".  Better., I 
think, is to put those commands you want executed at login by the user in 
question directly into her/his ".profile".  A user's ".bashrc" is for 
shells launched after login, e. g. by "screen".

-Dave

.bashrc

[Richard Wells]

How do I get my user account to see the .bashrc in the account's directory
and execute any changes such as different speakup parameters? If i type
"bash" after I log in the .bashrc file loads configuration but if I don't,
it seems to be ignored.

Thanks for help with this.


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com