Re: [cobalt-users] [RAQ2] Shell Aliases

[Mike Vanecek <nospam99@xxxxxxxxxxxx>]

I posted this previously about the same issue on a Qube2; maybe it will help.

FYI & FWIW: I have been studying the relationship between /etc/profile,
/etc/bashrc/ and /?/login on the Qube2. My goal was to be able to add global
aliases (such as ed = "pico -w") for use when one telnets into the system.
According to my books, such an alias needed to go into either login or bashrc
since alias would not work in profile.

Well, this is what I have found on the Qube2. First, /etc/bashrc and
/etc/login are not processed when one does a login from a telnet session. One
can force bashrc execution by doing a . bashrc, but that defeats the whole
idea. Second, an alias in /etc/profile works just fine (issue.net and  profile
are processed).

Maybe the login process via telnet is different that a login from a connected
terminal? Maybe Cobalt's changes affect things? I still have not been able to
figure out where motd gets processed during the telnet login process.

Profile also has a loop for i in /etc/profile.d/*.sh, however, nothing is in
the profile.d directory.

In any event, look to /etc/profile, issue.net, and motd if you need to
customize the telnet login process.

As an addendum to this, however, profile does not get executed on the Qube2 if
one does a su. I have not had the time to fix that, but my guess is that
bashrc is processed on an su.

HTH

On Sun, 04 Jun 2000 00:12:10 -0700, Hostmaster <hostmaster@xxxxxxxxxx> wrote:

:>How do you get the shell to recognize an alias?
:>
:>I've added:
:>alias ll    ls -lA
:>to /etc/bashrc
:>
:>and have even tried creating .bashrc in multiple places.
:>
:>Thoughts?
:>
:>Scott


-- 

  For information on the unofficial qube mailing list, see
  http://majordomo.email-lists.com/qube-users/