"Reuben D. Budiardja" <[EMAIL PROTECTED]> writes:
> However, I forgot to copy some files from the old home before I deleted it,
> including .bashrc. No problem, I though, I just copied it from my other
> machine. But then whenever I log in, the /home/rdonald/.ba
ald there.
>
> However, I forgot to copy some files from the old home before I deleted it,
> including .bashrc. No problem, I though, I just copied it from my other
> machine. But then whenever I log in, the /home/rdonald/.bashrc file does not
> get executed. I know this because I c
Quoting "Reuben D. Budiardja" <[EMAIL PROTECTED]>:
when you 'log in', it is not .bashrc which gets executed, but .bash_profile
.bashrc is executed when you open an xterm (or some other term emulator), when
you `su` or in some other instances, as when you telnet or ss
e/rdonald there.
>
> However, I forgot to copy some files from the old home before I deleted it,
> including .bashrc. No problem, I though, I just copied it from my other
> machine. But then whenever I log in, the /home/rdonald/.bashrc file does not
> get executed. I know this because I cu
it,
including .bashrc. No problem, I though, I just copied it from my other
machine. But then whenever I log in, the /home/rdonald/.bashrc file does not
get executed. I know this because I customize my prompt there, and I defined
some aliases. If after log in, I type 'bash' again, t
On Mon, Aug 26, 2002 at 09:23:56PM -0400, Jim wrote:
> new terminal window. I will try your trick, but I still do not
> understand why when I put the alias and set the prompt in the
> ~/.bashrc file it does not work, especially since a few here have
> posted that it works f
On Mon, Aug 26, 2002 at 11:04:16AM -0700, Samuel Flory wrote:
> Try putting the alias in .bash_profile. The .bashrc file doesn't get
> source when you login.
It does if you do:
[ -f ~/.bashrc ] && . ~/.bashrc
from ~/.bash_profile.
--
Hal Burgiss
--
redha
Jim <[EMAIL PROTECTED]> writes:
> Hal wrote:
>
>
>> > Hi all.I have added some lines to my .bashrc in
>> > an attempt to make an alias and change my prompt. Though
>> > I completely log out and back in, the changes do not take
>> &g
If I might qualify this a bit, and
based on my understanding
.bash_profile is sourced for interactive login shells only (or
other
shell started with --login option). .bashrc is not sourced
automatically in such situations (according to my reading of the
man
page anyway). But is usually
On Mon, Aug 26, 2002 at 10:29:40AM -0700, Gordon Messmer wrote:
> On Mon, 2002-08-26 at 10:01, Robert P. J. Day wrote:
> >
> > IMHO, setting the alias should go in your ~/.bashrc, while setting
> > the command line prompt should go in ~/.bash_profile.
>
> Anythi
Hi,
Am Montag, 26. August 2002 20:04 schrieb Samuel Flory:
> /etc/profile contains system wide settings.
Better to put personal system wide stuff into /etc/profile.local. At
the end of /etc/profile you just type "source /etc/profile.local" and
this file will be sourced whenever you login :-)
Try putting the alias in .bash_profile. The .bashrc file doesn't get
source when you login.
On Sun, 2002-08-25 at 19:37, James K Kroger wrote:
> Hi all.I have added some lines to my .bashrc in
> an attempt to make an alias and change my prompt. Though
> I completely log o
On Mon, 2002-08-26 at 10:01, Robert P. J. Day wrote:
>
> IMHO, setting the alias should go in your ~/.bashrc, while setting
> the command line prompt should go in ~/.bash_profile.
Anything used specifically by the interactive shell should go in
.bash_profile. That includes both you
On Mon, 26 Aug 2002, Jim wrote:
> Hal wrote:
>
>
> > > Hi all.I have added some lines to my .bashrc in
> > > an attempt to make an alias and change my prompt. Though
> > > I completely log out and back in, the changes do not take
> > > eff
Hal wrote:
> Hi all.I have added some
lines to my .bashrc in
> an attempt to make an alias and change my prompt. Though
> I completely log out and back in, the changes do not take
> effect (but xemacs does work when I type
"xemacs").
What does your ~/.bash_profile look
foo -v"
works fine in my .bashrc as well as in /etc/profile.local sourced by
/etc/profile
But did you try out the hint?
bis dahin
Martin Mewes
--
http://www.mamemu.de/ - VMware und mehr :-)
Registered Linux User:274764 - http://counter.li.org/
Der Forte Agent in Deutsch: http://agent-de.
On 25 Aug 2002, Gary A. Garibaldi wrote:
> Change alias x='xemacs' to
> alias x="xemacs"
> this should fix your .bashrc problem with alias use " "
huh? perhaps i'm still hung up on years of ksh usage, but
why should the difference in quot
--- "Gary A. Garibaldi" <[EMAIL PROTECTED]> wrote:
> Change alias x='xemacs' to
> alias x="xemacs"
> this should fix your .bashrc problem with alias use " "
In this particular case,
alias x=xemacs
or
alias x='xemacs&#
Change alias x='xemacs' to
alias x="xemacs"
this should fix your .bashrc problem with alias use " "
On Sun, 2002-08-25 at 19:37, James K Kroger wrote:
> Hi all.....I have added some lines to my .bashrc in
> an attempt to make an alias and change my p
On Sun, Aug 25, 2002 at 10:37:14PM -0400, James K Kroger wrote:
> Hi all.I have added some lines to my .bashrc in
> an attempt to make an alias and change my prompt. Though
> I completely log out and back in, the changes do not take
> effect (but xemacs does work when I type &quo
Hi all.I have added some lines to my .bashrc in
an attempt to make an alias and change my prompt. Though
I completely log out and back in, the changes do not take
effect (but xemacs does work when I type "xemacs").
Also when I type alias, the "x" is not there, but sever
[ -d ${1:-.} ] && no_path $* && eval ${2:-PATH}="$1:\$${2:-PATH}"
}
# if $1 is in path, remove it
del_path () {
no_path $* || eval ${2:-PATH}=`eval echo :'$'${2:-PATH}: |
sed -e "s;:$1:;:;g" -e "s;^:;;" -e "s;:\$;;"`
}
---
Poking around just a bit more, I find that Zshell has solved this
problem. While I've not used zsh, its documentation shows the ability
to 'typeset -U path' in a startup file. This tells the shell not to add
anything to the path that is already there. This would seem to be a
good feature to add
On 01/01/02, 10:15:34AM +1100, Cameron Simpson wrote:
> On Mon, Dec 31, 2001 at 02:03:36PM -0500, John P Verel <[EMAIL PROTECTED]> wrote:
> | So, it appears that conditional path modification is the only viable
> | option, short of major surgery. Cameron's rant is on point, IMHO.
>
> Oh, I dunno
On Mon, Dec 31, 2001 at 02:03:36PM -0500, John P Verel <[EMAIL PROTECTED]> wrote:
| So, it appears that conditional path modification is the only viable
| option, short of major surgery. Cameron's rant is on point, IMHO.
Oh, I dunno.
I don't like conditional modification much - feels tacky - it
On 12/31/01, 12:15:42AM -0500, Devon wrote:
>
> > See my note of a few minutes ago re: --noprofile option: tomorrow's
> > projects
>
> Well, that's probably more elegant, but I'd still advocate conditional
> path modification. ;)
>
Devon, et. al:
Well, turns out the --noprofile option idea d
again. That being the case, re-sourcing that file
| > shouldn't affect your path.
[... and other shell init stuff earlier in the thread ...]
Last October I ranted a bit about the startup scripts in the "Is Red Hat
heading down the wrong road?" thread. They are inefficient and overdone
(
nvironment and startup programs
> # Functions and aliases go in /etc/bashrc
> # Original Red Hat path follows:
> # PATH="$PATH:/usr/X11R6/bin"
> # Adding . 11/24, to pick up current directory for jdk problem. jpv
> PATH="$PATH:/usr/X11R6/bin:/usr/java/jdk1.3.1/bin"
houldn't affect your path.
The path modification in profile.d re: keberos is conditional, but not
in /etc/profile.
My /etc/profile looks like this:
# /etc/profile
# System wide environment and startup programs
# Functions and aliases go in /etc/bashrc
# Original Red Hat path follows:
# PA
On 12/30/01, 06:34:03PM -0600, Dave Ihnat wrote:
> On Sun, Dec 30, 2001 at 06:43:02PM -0500, John P Verel wrote:
> > As I use gnome with the gnome display manager, I end up starting
> > /etc/X11/xdm/Xsession, passing the argument "gnome-session". I have
> > this line in my Xsession, at line numbe
uot;/usr/java/jre1.3.1/bin:$PATH"
fi
That solved that problem.
Next, I installed sun's star office 6. The install of adabas added an
entry to ~/.bashrc which made a mess of my path.
The entry looked like:
# by Sun Microsystems setup
DBROOT=/home/devon/adabas
DBWORK=/home/devon/adabas/s
On Sun, Dec 30, 2001 at 06:43:02PM -0500, John P Verel wrote:
> As I use gnome with the gnome display manager, I end up starting
> /etc/X11/xdm/Xsession, passing the argument "gnome-session". I have
> this line in my Xsession, at line number 93:
>
>exec -l $SHELL -c "gnome-session"
>
>
On 12/30/01, 03:36:15PM -0600, Dave Ihnat wrote:
---snip---
> > If one logs in under X, apparently login and X BOTH start login shells.
> > I say this because what I see happening is that the path appendices from
> > my /etc/profile and my ~/.bash_profile are added twice. This does not >
> > h
I've only a few seconds right now--have to trot off--but I'm afraid you don't
quite have it.
On Sun, Dec 30, 2001 at 02:33:14PM -0500, John P Verel wrote:
> When init invokes getty, getty forks and creates (at level 5), consoles
> 1 through 6 and, for X, console 7.
Well, no. Actually, init spaw
n the Red Hat bash initialization scripts, /etc/bashrc?
>
> When one opens a gnome-terminal, after a successful X session start of
> gnome, here is what I believes happens:
>
> 1) Xsession starts a bash login session.
>
> 2) gnome-terminal starts a non-login session.
>
>
there a bug in the Red Hat bash initialization scripts, /etc/bashrc?
> [...]
> | 1) Xsession starts a bash login session.
> | 2) gnome-terminal starts a non-login session.
> [...]
> | The root of this, I think, is that last several lines in /etc/bashrc
> | which, as noted in the c
On Tue, Dec 25, 2001 at 10:44:58PM -0500, John P Verel <[EMAIL PROTECTED]> wrote:
| Is there a bug in the Red Hat bash initialization scripts, /etc/bashrc?
[...]
| 1) Xsession starts a bash login session.
| 2) gnome-terminal starts a non-login session.
[...]
| The root of this, I think, i
Is there a bug in the Red Hat bash initialization scripts, /etc/bashrc?
When one opens a gnome-terminal, after a successful X session start of
gnome, here is what I believes happens:
1) Xsession starts a bash login session.
2) gnome-terminal starts a non-login session.
This means that:
a
Hi,
I am trying to run different client VT (xterm, aterm, etc). What I want is to
have different PS1 variable for different VT client. But PS1 is set in
.bashrc, and all VT client run the same .bashrc. So how can I accomplish what
I wanna do?
Thanks in advance for any help.
Reuben D
On Tue, 25 Sep 2001 [EMAIL PROTECTED] wrote:
> -rwxr-xr-x bashrc*
> Is there any security problems?
Depends on what you have in there, whether you're using user-private home
directories (the default on Red Hat), and why you would want anyone else
to be able to execute your perso
Hi all
If the brashrc is changed to
-rwxr-xr-xbashrc*
Is there any security problems?
and
What files are control the login environment?
Many thanks
___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo
We use Tektronix X-terminals in our compay.
When we use Gnome, we donnot get a frame around the windows. Eg windows is
sticking to the desktop and cannot be moved around. There's no exit widget etc.
But when running Gnome from the graphics console everything is allright.
If we use KDE, we get
Hi,
Quick question: I am trying to understand why when I make changes to my
.bash_profile and/or .bashrc files for individual users, these
environmental changes will appear under KDE when I use eterm, but not
with the Gnome or other xterm programs. Are there other files I need to
edit? I thought
Hi,
Would anyone please tell me the relationship between xrootenv and
/root/.bashrc? Does xrootenv have precedence over .bashrc?
Thanks.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
Hi Krzysztof and Linus,
I put the statements in /etc/profile and it works perfect. The syntax &
spelling were correct in /home/.bashrc but it still didn't want to work.
Anyway, it works this way. Thanks!
Zoki.
On Mon, 11 May 1998, Cabaj, Krzysztof wrote:
->Hi,
->I propose to
> I put some aliases in /etc/bashrc as root to cut on the typing and it
> works. I did the same in /home/.bashrc as user and...it doesn't work.
> Whhha..
>
> I get an error message saying "command not found".
>
Does the user have the specified pat
On Mon, 11 May 1998, Zoki wrote:
> I put some aliases in /etc/bashrc as root to cut on the typing and it
> works. I did the same in /home/.bashrc as user and...it doesn't work.
> Whhha..
>
> I get an error message saying "command not found".
>
-BEGIN PGP SIGNED MESSAGE-
At 12:04 5/11/98 +0200, Zoki wrote:
>I put some aliases in /etc/bashrc as root to cut on the typing and it
>works. I did the same in /home/.bashrc as user and...it doesn't work.
>Whhha..
>
>I get an error message saying "c
Hi,
I propose to put aliases in the /etc/profile.
It should work correctly.
Krzysztof
> -Original Message-
> From: Linus Akerlund [SMTP:[EMAIL PROTECTED]]
> Sent: 11 maja 1998 13:18
> To: Red Hat list
> Subject: Re: Aliases in bashrc...
>
> On Mon, 11
On Mon, 11 May 1998, Zoki wrote:
> I put some aliases in /etc/bashrc as root to cut on the typing and it
> works. I did the same in /home/.bashrc as user and...it doesn't work.
> Whhha..
>
> I get an error message saying "command not found".
I sup
I put some aliases in /etc/bashrc as root to cut on the typing and it
works. I did the same in /home/.bashrc as user and...it doesn't work.
Whhha..
I get an error message saying "command not found".
Any su
LEBLIN JY <[EMAIL PROTECTED]> on Mon, Mar 09, 1998 at 03:01:06PM +0100:
> Has anybody got an idea where the mistake is ( and it is certainly stupid ).
> Here is what my .bashrc is like if it may help. Unless i make a source
> .bashrc none of the alias is available.
Bash only
Hi,
It's not very important but i've got problems with my .bashrc file : the
system
doesn't seem to take care of it.
I've checked the man and it says that the option -norc ( which obliges not
to read the .bashrc ) is default when the shell invoked is sh so maybe
that&#x
53 matches
Mail list logo
