public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: chuck gelm <chuck@gelm.net>
To: Peter <heisspf@skyinet.net>
Cc: Ray Olszewski <ray@comarre.com>, linux-newbie@vger.kernel.org
Subject: Re: Bash will not start in Terminals
Date: Tue, 15 Mar 2005 06:37:09 -0500	[thread overview]
Message-ID: <4236C8E5.3090703@gelm.net> (raw)
In-Reply-To: <200503150746.j2F7kBBm000590@skyinet.net>

Peter wrote:
> Hi,
> 
> Peter said:
> 
>>Slackware10 kernel 2.4.26
>>
>>>For me unknown reason suddenly bash will not
>>
>>start in terminals. 
> 
> 
> The reason was that I had made a new slackware installation in which then in 
> the /etc/passwd under my user name at the end of the line there was no 
> :/bin/bash as it used to be.
> 
> I found it out when I added an arbitrary user in which then again bash was not 
> started in the terminals. Again on his passwd line there was no :/bin/bash.
> 
> So it had nothing to do with me getting too old for Linux. It's a new 
> "gimmick" in slackware which one has to find out first.
> 
> Regards

Hi, Peter:

  I use Slackware 10.0 on my laptop and I have added 4 users.
Each has '/bin/bash' at the end of the entries of /etc/passwd.

  I see the same in /etc/passwd on my Slackware 10.1 on another box.

I seem to have no such gimmick ???

Regards, Chuck



-
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-15 11:37 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
2005-03-15  7:42   ` Peter
2005-03-15  7:46   ` Peter
2005-03-15 11:37     ` chuck gelm [this message]
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=4236C8E5.3090703@gelm.net \
    --to=chuck@gelm.net \
    --cc=heisspf@skyinet.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=ray@comarre.com \
    /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