On 26.12.2024 14:03, Greg Wooledge wrote:
On Thu, Dec 26, 2024 at 10:56:31 +, Chris Green wrote:
hen...@privatembox.com wrote:
>
> So, since I am using a login shell, and I have .bashrc created. thus I
> have to create a .profile to include .bashrc? Am I right?
>
Yes, I thin
On 2024-12-26, hen...@privatembox.com wrote:
> Hello
>
> I have these settings in .bashrc of my home dir:
>
> $ cat .bashrc
> export TF_CPP_MIN_LOG_LEVEL=3
> export CUDA_VISIBLE_DEVICES=-1
>
> but every time after i login the system, the settings are not activated.
&g
On Thu, Dec 26, 2024 at 10:56:31 +, Chris Green wrote:
> hen...@privatembox.com wrote:
> >
> > So, since I am using a login shell, and I have .bashrc created. thus I
> > have to create a .profile to include .bashrc? Am I right?
> >
> Yes, I think that's
> Sent: Thursday, December 26, 2024 at 5:56 AM
> From: "Chris Green"
> To: debian-user@lists.debian.org
> Subject: Re: bashrc question
>
> hen...@privatembox.com wrote:
> >
> > So, since I am using a login shell, and I have .bashrc created. thus I
hen...@privatembox.com wrote:
>
> So, since I am using a login shell, and I have .bashrc created. thus I
> have to create a .profile to include .bashrc? Am I right?
>
Yes, I think that's the right way round.
I use ssh a lot and have a 'standard' configuration for
On 26.12.2024 04:52, Greg Wooledge wrote:
On Thu, Dec 26, 2024 at 04:16:17 +0100, hen...@privatembox.com wrote:
Hello
I have these settings in .bashrc of my home dir:
$ cat .bashrc
export TF_CPP_MIN_LOG_LEVEL=3
export CUDA_VISIBLE_DEVICES=-1
but every time after i login the system, the
On Thu, Dec 26, 2024 at 04:16:17 +0100, hen...@privatembox.com wrote:
> Hello
>
> I have these settings in .bashrc of my home dir:
>
> $ cat .bashrc
> export TF_CPP_MIN_LOG_LEVEL=3
> export CUDA_VISIBLE_DEVICES=-1
>
> but every time after i login the system, the sett
On Thursday, 26-12-2024 at 14:16 hen...@privatembox.com wrote:
> Hello
>
> I have these settings in .bashrc of my home dir:
>
> $ cat .bashrc
> export TF_CPP_MIN_LOG_LEVEL=3
> export CUDA_VISIBLE_DEVICES=-1
>
> but every time after i login the system, the settings
Hello
I have these settings in .bashrc of my home dir:
$ cat .bashrc
export TF_CPP_MIN_LOG_LEVEL=3
export CUDA_VISIBLE_DEVICES=-1
but every time after i login the system, the settings are not activated.
I have to source it by hand to make it work.
what's wrong with me?
Thanks.
Thanks a lot @Will Mengarini
On Wed, Jan 12, 2022 at 8:21 PM Will Mengarini wrote:
> * Yamada??? [22-01/12=We 20:10 +0800]:
> > Do you mean if .bash_profile exists, .bashrc will be ignored?
>
> Sometimes. From `man bash`:
> When bash is invoked as an interactive lo
* Yamada??? [22-01/12=We 20:10 +0800]:
> Do you mean if .bash_profile exists, .bashrc will be ignored?
Sometimes. From `man bash`:
When bash is invoked as an interactive login shell, or as a
non-interactive shell with the --login option, it first reads
and executes commands from the f
* Yamada??? [22-01/12=We 19:49 +0800]:
> I have a .bashrc file in my home dir, whose content is shown as follows.
> But every time I log into the system, I have to source this file by hand.
>
> $ which scala
> /usr/bin/scala
>
> $ cat .bashrc
> #THIS MUST BE AT THE END O
Do you mean if .bash_profile exists, .bashrc will be ignored?
Thanks.
On Wed, Jan 12, 2022 at 8:07 PM Will Mengarini wrote:
> * Yamada??? [22-01/12=We 19:49 +0800]:
> > I have a .bashrc file in my home dir, whose content is shown as follows.
> > But every time I log into the sy
Hello list
I have a .bashrc file in my home dir, whose content is shown as follows.
But every time I log into the system, I have to source this file by hand.
$ which scala
/usr/bin/scala
$ cat .bashrc
#THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!!
export SDKMAN_DIR="$HOME/.s
me of the alias statements
in my user .bashrc are no longer working!.
The strange thing is that some still are working. Also, if I enter the
complete path to an executable whose alias is NOT working, the
executable works Reentering the alias statement in .bashrc does not
restore the fun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Stephen P. Molnar wrote:
> The subject line tells it all!? Debian Stretch (64bit).
>
> Without warning, or any other indications, some of the alias statements
> in my user .bashrc are no longer working!.
>
> The strange thing is t
The subject line tells it all!? Debian Stretch (64bit).
Without warning, or any other indications, some of the alias statements
in my user .bashrc are no longer working!.
The strange thing is that some still are working. Also, if I enter the
complete path to an executable whose alias is NOT
Thanks for the reply.
Adding the lines from your .bash_profile to mine restored the
functionality of .bashrc.
I don't have any backups of .bash_profile, but I would guess the the HEX
installation script woped out the origional .bash_profile. ( I try to
never assume anything as we all
On Wed, Apr 25, 2018 at 10:49:52PM +0300, Abdullah Ramazanoglu wrote:
> It seems like when ~/.bash_profile did not exist, then ~/.bashrc is called
> directly.
That's not correct.
As a LOGIN shell, bash reads ONE file, searching among the following items
in sequence:
a) ~/.bas
On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote:
> Bu bumbling about I discovered
> the it is necessary to source .bashrc inorder to recticate the alias lines
> in .bashrc (note: commenting out the added lines in .bash_profile did not
> solve the problem).
>
&g
On Wed, 25 Apr 2018 15:34:02 -0400 Stephen P. Molnar said:
> What's going on what is the fix?
It seems like when ~/.bash_profile did not exist, then ~/.bashrc is called
directly. However, when ~/.bash_profile did exist, then it is called *instead
of* ~/.bashrc and it is up to ~/.bash_pr
Hello,
On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote:
> Whie the additional lines are necessary for the execution of HEX they seem
> to have wiped oour all of the alias entries I have in .bashrc. Rebooting
> the system does not eliminate the problem! Bu bumblin
EX_VERSION=8.0.0
export PATH=${PATH}:${HEX_ROOT}/bin
export HEX_CACHE=/home/comp/Apps/Hex/hex_cache
Whie the additional lines are necessary for the execution of HEX they
seem to have wiped oour all of the alias entries I have in .bashrc.
Rebooting the system does not eliminate the problem! B
Hello José,
José Luis Segura Lucas wrote:
> I don't remember to write or generate "by hand" this ~/.profile. Is it
> created automatically?
It should be created automatically from the files in /etc/skel/ if
you are using useradd or adduser (the former with the --create-home
option).
Best regard
On Sat, Jun 23, 2012 at 05:24:59PM +0200, José Luis Segura Lucas wrote:
> You are right: I have the ~/.profile file missing. I don't know how can
> I miss this file, but it didn't exist at all. I copied this from another
> computer and it works.
tal% less .profile
# ~/.profile: executed by the com
y ~/.profile has a section like the following:
>
> # if running bash
> if [ -n "$BASH_VERSION" ]; then
> # include .bashrc if it exists
> if [ -f "$HOME/.bashrc" ]; then
> . "$HOME/.bashrc"
> fi
> fi
>
> which is also in t
Hello José,
José Luis Segura Lucas wrote:
> In one (and only one) of then, when I open a terminal or connect by SSH,
> my bash load the default system configuration from /etc/bash.bashrc,
> instead of reading, as usual, ~/.bashrc.
>
> I can think that I don't really have a
, as usual, ~/.bashrc.
I can think that I don't really have a ~/.bashrc (or have a mispelling
on the file name), but if I run bash from the terminal, my configuration
file in ~/.bashrc is loaded.
I add an "echo" on each files before sending you my problem to check
that the
> something)
After I copy .bashrc and .profile to my $HOME directory, and setup owner
for these files to be owned by user: by me, everything back to the
normal. Thanks!
OK, I edited these files and add some lines there, like:
EDITOR=emacsclient; export EDITOR
--
Regards, Paul Chany
h
Csanyi Pal:
>
> When I installed 64bit Debian GNU/Linux Squeeze, I used my $HOME
> directory with it's dot files too.
>
> So, I think the .bashrc and .bash_profile remain in the state in which
> was on Gentoo.
Yes, that's how it should be. Debian package managers mus
0 at 10:29, Csanyi Pal wrote:
> Hi,
>
> I was tried Gentoo Linux system but after a while I come back to Debian
> GNU/Linux system again on my PC Box.
>
> So, in my /home/csanyipal/ directory there remain some dot files from
> Gentoo system, eg.: .bashrc, .bash_profile.
>
&
Hi,
I was tried Gentoo Linux system but after a while I come back to Debian
GNU/Linux system again on my PC Box.
So, in my /home/csanyipal/ directory there remain some dot files from
Gentoo system, eg.: .bashrc, .bash_profile.
When I installed 64bit Debian GNU/Linux Squeeze, I used my $HOME
Boyd Stephen Smith Jr. wrote:
> On Wednesday 19 November 2008, tyler <[EMAIL PROTECTED]> wrote
> about 'Re: Which files do what: .bashrc and friends':
>>I believe .profile and .bash_profile are synonyms, so you'd only use one
>>or the other.
>
> .pro
ell exits, bash reads and executes commands from the
file ~/.bash_logout, if it exists.
When an interactive shell that is not a login shell is started, bash
reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if
these files exist. This may be inhibited by us
Mike McCarty <[EMAIL PROTECTED]>:
> Dotan Cohen wrote:
> >
> > .bashrc
>
> Run once for each interactive shell, after .profile
... if called by .profile or .bash_profile.
A long time ago, this was automatic (a la ksh and ENV; if ENV =
~/.kshrc, then ~/.kshrc was ru
Dotan Cohen a écrit :
Thanks in advance. If there are any good docs that explain this, I'd
love to see them. I have not been able to google anything recent that
is relevant to Debian.
Quick'n dirty solution :
Another way to know, even if it does not cover all cases, is to put the
following li
27;.
If K Display Manager (kdm) is installed file "/etc/kde3/kdm/Xsession"
executes user's login shell, for example "$HOME/.bash_profile" which in
turn might source .bashrc too.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
"Boyd Stephen Smith Jr." <[EMAIL PROTECTED]> writes:
> On Wednesday 19 November 2008, "Dotan Cohen" <[EMAIL PROTECTED]> wrote about
> 'Re: Which files do
> what: .bashrc and friends':
>>1) Is a login shell run when the user logs
On Wednesday 19 November 2008, "Dotan Cohen" <[EMAIL PROTECTED]> wrote about
'Re: Which files do
what: .bashrc and friends':
>1) Is a login shell run when the user logs onto KDE (even though he
>does not see a konsole window)?
Nope a login shell is when bash is
On Wednesday 19 November 2008, tyler <[EMAIL PROTECTED]> wrote
about 'Re: Which files do what: .bashrc and friends':
>I believe .profile and .bash_profile are synonyms, so you'd only use one
>or the other.
.profile is only used by bash when it cannot find .bash_profi
I believe equivalent to .profile
.bashrc
Run once for each interactive shell, after .profile
The main difference between .profile and .bashrc is that
.profile only gets run when you start a "login shell",
but .bashrc gets run for all shells.
So, for example, if you use
$ su -
hen logging in / starting a Konsole:
>>>
>>> .profile
>>> .bash_history
>>> .bash_logout
>>> .bash_profile
>>> .bashrc
>>>
>>> Thanks in advance. If there are any good docs that explain this, I'd
>>> love to see them. I ha
2008/11/19 tyler <[EMAIL PROTECTED]>:
> "Dotan Cohen" <[EMAIL PROTECTED]> writes:
>
>> On a Debian-based system running KDE 3.5.10 I see several files that
>> are used when logging in / starting a Konsole:
>>
>> .profile
>> .bash_history
&
"Dotan Cohen" <[EMAIL PROTECTED]> writes:
> On a Debian-based system running KDE 3.5.10 I see several files that
> are used when logging in / starting a Konsole:
>
> .profile
> .bash_history
> .bash_logout
> .bash_profile
> .bashrc
>
> Thanks in ad
On a Debian-based system running KDE 3.5.10 I see several files that
are used when logging in / starting a Konsole:
.profile
.bash_history
.bash_logout
.bash_profile
.bashrc
I imagine three times these files might be used:
1) When logging in
2) When starting Konsole
3) When running a shell
ctory to my system. My .bash_profile and .bashrc files were the
default files loaded during the install. However, my PATH remains
unchanged when I log on even though the .bash_profile file has the
lines to add my ~/bin directory. I can make the change manually after
I've logged on and can execut
; >> dedicated PC with all the default settings. I have added a ~/bin
> >> directory to my system. My .bash_profile and .bashrc files were the
> >> default files loaded during the install. However, my PATH remains
> >> unchanged when I log on even though the .ba
>> directory to my system. My .bash_profile and .bashrc files were the
>> default files loaded during the install. However, my PATH remains
>> unchanged when I log on even though the .bash_profile file has the
>> lines to add my ~/bin directory. I can make the change manual
On Saturday 12 January 2008 20:50 John Salmon wrote:
> I'm a new user to Debian Linux. I have the latest version loaded on a
> dedicated PC with all the default settings. I have added a ~/bin directory
> to my system. My .bash_profile and .bashrc files were the default files
>
I'm a new user to Debian Linux. I have the latest version loaded on a
dedicated PC with all the default settings. I have added a ~/bin directory
to my system. My .bash_profile and .bashrc files were the default files
loaded during the install. However, my PATH remains unchanged when I l
On 09/18/2007 10:08 AM, Kent West wrote:
I've just discovered that a stable install (4.0, (with rdiff-backup
pulled from testing)) has a wonky (that's a technical term, you
understand ... ;-) ) /etc/skel/bashrc apparently.
[...]
I don't see anything particularly odd in /etc/s
On Tue, Sep 18, 2007 at 10:08:35 -0500, Kent West wrote:
> I've just discovered that a stable install (4.0, (with rdiff-backup pulled
> from testing)) has a wonky (that's a technical term, you understand ... ;-)
> ) /etc/skel/bashrc apparently.
>
> If I ssh in as a fres
I've just discovered that a stable install (4.0, (with rdiff-backup
pulled from testing)) has a wonky (that's a technical term, you
understand ... ;-) ) /etc/skel/bashrc apparently.
If I ssh in as a freshly-created user and then run the "set" command, I
get pages and pag
On Tue, Aug 21, 2007 at 04:14:04PM -0700, Dr. Jennifer Nussbaum wrote:
>
> PS1='\h\w $ '; export PS1
>
> So, nothing fancy. How do i get my coloured "ls" back,
> and my "#" prompt as sudo'ed root?
Use \$ rather than a plain $ to get # as root.
A.
--
Ansgar Esztermann
Researcher & Sysadmin
sudo'ed to root, i
> would get the usual "#" prompt as root.
>
> I then copied over my (straightforward) .bashrc file,
> and now i dont have the colored output and sudoing to
> root
> leaves me with a "$" prompt. (I do reset my PS1 line,
> but i dont know
over my (straightforward) .bashrc file,
and now i dont have the colored output and sudoing to
root
leaves me with a "$" prompt. (I do reset my PS1 line,
but i dont know how to have a different one for root,
keeping
the "#".) Can someone give me a suggestion? My
complete
.bashrc,
On Tue, Dec 26, 2006 at 10:53:27AM +0100, Lorenzo Bettini wrote..
> >I remember that the files are read like
> >
> >/etc/profile - > ~/.bash_profile -> ~/.bashrc -> ~./profile
> >
> >but the bashrc file should be created by default without you
>
Ali Jawad wrote:
I remember that the files are read like
/etc/profile - > ~/.bash_profile -> ~/.bashrc -> ~./profile
but the bashrc file should be created by default without you having to
insert it..
that's what I thought too, but neither .bashrc nor .bash_profile were
created
Marc Shapiro wrote:
Lorenzo Bettini wrote:
Hi
on the standard user's home I use everyday I have the .bashrc file
that is read upon login.
Now I created a brand new user (with adduser), but the .bashrc file I
inserted in his home is never read upon login... in /etc/profile and
I remember that the files are read like
/etc/profile - > ~/.bash_profile -> ~/.bashrc -> ~./profile
but the bashrc file should be created by default without you having to
insert it..
On 12/25/06, Lorenzo Bettini <[EMAIL PROTECTED]> wrote:
Hi
on the standard user's home I
Lorenzo Bettini wrote:
Hi
on the standard user's home I use everyday I have the .bashrc file
that is read upon login.
Now I created a brand new user (with adduser), but the .bashrc file I
inserted in his home is never read upon login... in /etc/profile and
/etc/bash.profile the .bash
Hi
on the standard user's home I use everyday I have the .bashrc file that
is read upon login.
Now I created a brand new user (with adduser), but the .bashrc file I
inserted in his home is never read upon login... in /etc/profile and
/etc/bash.profile the .bashrc is actually never
On Sunday 07 May 2006 18:33, Henrique G. Abreu wrote:
> try
> #!/bin/sh
> it may work
> Henrique
hi Henrique,
i had tried that (described in my original post), and it did not work.
On the other hand, what does work,
is taking all the different variable definitions and export lines and putting
I created a file with these lines,
chmoded 755 the file
(and tried with and without adding
#!/usr/bin/sh
as the first line ) and it did not help.
try
#!/bin/sh
it may work
Henrique
>
> even if I run it, it only sets the variables within the run shell
> it does not source the variables for the father (mother) shell
>
> How can I do this?
Duh,
source filename
works just like like in the c shell where i saw it used before
sorry to bother ...
>
> Thanks
> Mitchekk
--
Hi,
I want to set a few shell variables that I occasionally want to set up.
I dont want them set always.
Thats why I can't put them in .bashrc
thus I want to temporarily
export PATH=/home/mlaks/stable-gtk/local/bin:$PATH
export \
LD_LIBRARY_PATH=/home/mlaks/stable_gtk/local/lib:
>
>I am running sid with kde3.5. I have some aliases in /etc/bash.bashrc.
>In konsole as user if I type alias I get all aliases. But in root
>konsole, I don't get aliaes. Why?
>
>
>
>
Hmm, I dunno. My bash.bashrc on my desktop just has "source /root/bash"
in it. The /root/bash file has all my al
can do what you want in these files ..
>
> # after /etc/profile, search in order for the first executable:
> ~/.bash_profile
> ~/.bash_login
> ~/.profile - not read if the files exists before it
>
> ~/.bashrc i
e ...
>>
>> - if you're confused .. do NOT change files in anything other
>> than your own home directory "/home/you"
>
>
> My solution to this nonsense is to have a file
>
> /home/me/my_startup
Might he need to do this in his .bashrc (
Alvin Oga wrote:
hi ya
forgot-who started it
Is there a good system for setting variables, aliases, etc that need to be
set for user X, whether I log in at a login prompt or using su? I'm
confused by all the different .profile options (there are at least 3 for
bash, why is that?)
why ?
in
~/.profile - not read if the files exists before it
~/.bashrc interactive shell read it if it exists
~/.morebashfiles ??
more user stuff
~/.aliasalways put aliases outside of bash files
x27;t know if there is such a system/program but I can help you clear things up.Each of these files are read by bash at different times:.bash_profile is executed when you login.
Stuff you put in there might be your PATH and other important environment variables..bashrc is used for non login she
[EMAIL PROTECTED]:~$ cat .bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If running interactively, then:
if [ "$PS1" ]; then
# don't put duplicate lines in the history.
On Sun, 04 Jan 2004 08:17:26 -0500, Russ Schneider wrote:
> I have changed the files /etc/bash.bashrc and /etc/profile to my liking.
>
> Problem is, when I create new users, the files .bashrc and .bash_profile
> are created in their home directory and they are created with ele
On Sun, Jan 04, 2004 at 08:36:41 -0500, Russ Schneider wrote:
> When the system copies those files for a new user, they're all owned by
> root:root.
That's sounds like a bug. Please file a report using reportbug.
Ray
--
People don't respond to any events as real people facing events would.
Othe
On Sun, 4 Jan 2004, J.H.M. Dassen (Ray) wrote:
> Edit the skeleton files in /etc/skel/ . (They're marked as conffiles so the
> package management system will not accidentally overwrite your changes).
Great! But I noticed something.
When the system copies those files for a new user, they're all
On Sun, Jan 04, 2004 at 08:17:26 -0500, Russ Schneider wrote:
> What generates .bashrc and .bash_profile for each new user?
adduser(1) by copying from /etc/skel/ .
> Is it something I can alter so it writes them the way I want them?
Edit the skeleton files in /etc/skel/ . (They'r
I have changed the files /etc/bash.bashrc and /etc/profile to my liking.
Problem is, when I create new users, the files .bashrc and .bash_profile
are created in their home directory and they are created with elements
that supercede those two previous files.
What generates .bashrc and
--- Roberto Sanchez <[EMAIL PROTECTED]> wrote:
> I have a machine running Debian Woody. I made some
> changes to my ~/.bashrc
> file, but the changes aren't taking. The changes I
> made to root's ~/.bashrc
> work like a champ, but not for my regular user
> a
Hi!
On Fri Aug 22, 2003 at 05:59:26PM +0200, Roberto Sanchez wrote:
> I have a machine running Debian Woody. I made some changes to my ~/.bashrc
> file, but the changes aren't taking. The changes I made to root's ~/.bashrc
> work like a champ, but not for my regular user acc
I have a machine running Debian Woody. I made some changes to my ~/.bashrc
file, but the changes aren't taking. The changes I made to root's ~/.bashrc
work like a champ, but not for my regular user account. I can access the
server via SSH, and basically, it works for root (whethe
On Wed, Jul 30, 2003 at 12:27:00AM +0200, Andreas Janssen wrote:
> Hello
>
> Robin Gerard (<[EMAIL PROTECTED]>) wrote:
>
> > I would like to understand why, when I set LANG to C, in
> > /etc/environment and LANG to fr_FR.ISO-8859-1 in my .bashrc, after the
>
Hello
Robin Gerard (<[EMAIL PROTECTED]>) wrote:
> I would like to understand why, when I set LANG to C, in
> /etc/environment and LANG to fr_FR.ISO-8859-1 in my .bashrc, after the
> login, I can't write te letters with accents.
Are you talking about a login shell? .bashrc i
Hello,
I would like to understand why, when I set LANG to C, in /etc/environment
and LANG to fr_FR.ISO-8859-1 in my .bashrc, after the login, I can't write
te letters with accents.
( However if I launch mutt, for example, the messages send by mutt are in
French. )
On the other hand, if
On Sun, Jul 13, 2003 at 08:21:34PM +0200, Sebastian Kapfer wrote:
> On Sun, 13 Jul 2003 19:30:10 +0200, Robin Gerard wrote:
Thanks.
PS1="${cyan}[$TIME [EMAIL PROTECTED] \[${YELLOW}\#$NC\]] \[\w\$ "
did the trick.
--
Gerard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
On Sun, 13 Jul 2003 19:30:10 +0200, Robin Gerard wrote:
> with this PS1 I get:
>
> [18:31 : 0.16]
> [EMAIL PROTECTED] 1] ~$
>
> but if I write a very long command the cursor remains on the same line and
> overlaps the prompt.
>From "man bash":
> \[ begin a sequence of non‐printing chara
Hello,
I encountered a trifling problem in my .bashrc:
.
.
# Define some colors:
RED='\e[1;31m'
cyan='\e[0;36m'
CYAN='\e[1;36m'
YELLOW='\e[1;33m
> 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 .
> 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 .bash
Roberto Sanchez wrote:
> Why is it that when I switch to a text console with -- 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
>
Roberto Sanchez said:
> Why is it that when I switch to a text console with -- 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 manp
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 wit
Why is it that when I switch to a text console with -- 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
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='$ '
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]
> 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
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.
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
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
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
1 - 100 of 208 matches
Mail list logo
