1:34 p.m.
All:
Since installing bash-3, whenever I su - to another user (root or
whoever) I no longer have any of the aliases available (i.e. ll, l.,
etc. ).
The offending script appears to be /etc/bashrc. the last thing it does
is:
if [ "x$SHLVL" != "x1" ]; then # We're not a login shell
for i in /etc/profile.d/*.sh; do
if [ -r "$i" ]; then
. $i
fi
done
unset i
fi
fi
which sources all of the *.sh scripts in /etc/profile.d but apparently
this only happens when bash is run therefore I lose all of them if I su
- to root
So does this need fixing or is it just a pain?
Scott
P.S.
3:33 p.m.
On Tue, Aug 03, 2004 at 11:34:30AM -0700, Scott Talbot wrote:
Since installing bash-3,
A timing coincidence, I bet.
whenever I su - to another user (root or
whoever) I no longer have any of the aliases available (i.e. ll, l.,
etc. ).
Most likely not "any" but ll, l. and ls and this happens only
if you are doing that in a terminal window and not a text console.
Add 'TERM gnome' to your /etc/DIR_COLORS and the problem will
vanish. If you want details then look at a "what is eating
dircolors?" thread on this list.
If this is something else then I am not seeing it.
Michal
5:34 p.m.
On Tue, 2004-08-03 at 14:33 -0600, Michal Jaegermann wrote:
On Tue, Aug 03, 2004 at 11:34:30AM -0700, Scott Talbot wrote:
>
> Since installing bash-3,
A timing coincidence, I bet.
> whenever I su - to another user (root or
> whoever) I no longer have any of the aliases available (i.e. ll, l.,
> etc. ).
Most likely not "any" but ll, l. and ls and this happens only
if you are doing that in a terminal window and not a text console.
Add 'TERM gnome' to your /etc/DIR_COLORS and the problem will
vanish. If you want details then look at a "what is eating
dircolors?" thread on this list.
If this is something else then I am not seeing it.
Michal
Michal:
Thank you for your swift resolution. Adding the 'TERM gnome' line
turned the tide.
Scott
4:20 a.m.
On Tue, Aug 03, 2004 at 09:05:08PM -0600, Michal Jaegermann wrote:
On Tue, Aug 03, 2004 at 03:34:33PM -0700, Scott Talbot wrote:
>
> Michal:
>
> Thank you for your swift resolution. Adding the 'TERM gnome' line
> turned the tide.
You better file report on bugzilla. :-)
Why is TERM ever set to gnome in the first place? That's the question
I'd like to see the answer to..
Tim.
*/
10:15 a.m.
Why is TERM ever set to gnome in the first place?
The recent bunch of GNOME updates had this side-effect. What
precisely is responsible for that I did not try to track down yet.
When I had notice that my first reaction was "Sigh! Here comes the
big trouble. Somebody was not thinking about implications". OTOH
the last part is nothing new or unusual from user-interface guys and
I thought that there is possibly some deeper purpose to it. It is
not that hard to reverse in a one stroke but so far I was resisting
the tempation for testing purposes. :-)
That's the question I'd like to see the answer to..
I am all ears!
Michal
7241
days inactive
7242
days old
6 comments
4 participants
participants (4)
-
Bill Nottingham -
Michal Jaegermann -
Oldman -
Tim Waugh