public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: Bash will not start in Terminals
Date: Thu, 10 Mar 2005 18:55:46 -0800	[thread overview]
Message-ID: <5.1.0.14.1.20050310183928.0293ee08@celine> (raw)
In-Reply-To: <200503100407.j2A47Fla002077@skyinet.net>

At 12:07 PM 3/10/2005 +0800, Peter H. wrote:
>Hi,
>
>Slackware10 kernel 2.4.26
>
>For me unknown reason suddenly bash will not start in terminals.

Do you really mean that the terminal sits open but does not accept any 
input? Or do you, just possibly, mean that bash starts (you get a prompt 
and can enter commands) but it does not read its config files the way you 
expect it to?

>Therefore no
>PSI is set

PS1, perhaps?

>and commands I have in ~/.bashrc are not known unless I type bash
>in
>xterm after which PSI is set as well.

If you can type "in xterm", then *some* shell is running. If you really 
don't know what it is, start one up, then use a different one, or a console 
or remote session, to check the process list to see what shell is running.

BTW, it should also work just to run .bashrc . You might see if it does.

>If I open xterm with: "xterm -e su -l"

How are you entering this? Do you mean in another, working xterm?

Are you already root when you do this? As a non-root user, my system will 
not let me open an xterm with both logging and su ... probably to protect 
the root password.

I think this works because the bash invoked by su is not a login shell. See 
below.

>it opens with bash, w/o the -l flag
>there is no bash.
>
>How to resolve?

Is this true for all users or a specific subset of users? In particular, is 
root different from an ordinary user?

What you are seeing may be differences in behavior between login and 
non-login instances of bash. A login instance expects to run /etc/profile, 
./.bash_profile, ./.bash_login, and ./.profile ... but not ./.bash_rc 
(though it is not unusual for one of these other files to cause .bashrc to 
execute).

Overall, what you are describing sounds like a situation where bash is 
starting but is not getting some fo the settings you want it to have. This 
may mean a problem in /etc/profile or one of the user-specific bash-login 
files I listed above.

Without a followup from you, it is hard to be more specific. But all of 
this, perhaps supported by your reading the man pages for bash and xterm, 
may be enough to get you to a solution.

Good luck.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2005-03-11  2:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10  4:07 Bash will not start in Terminals Peter H.
2005-03-11  2:55 ` Ray Olszewski [this message]
2005-03-15  7:42   ` Peter
2005-03-15  7:46   ` Peter
2005-03-15 11:37     ` chuck gelm
2005-03-15 16:33     ` Richard Adams
  -- strict thread matches above, loose matches on Subject: below --
2005-03-16  0:49 Peter H.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.1.20050310183928.0293ee08@celine \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox