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 us
[EMAIL PROTECTED] said:
> Peter use ´adduser´ to create user accounts in slack, /bin/bash is the
> default in that program.
I'll be darn. I kept on using 'useradd'.
Thanks & regards
--
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to
On Tuesday 15 March 2005 08:46, 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 wh
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
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 us
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
Hi,
Slackware10 kernel 2.4.26
For me unknown reason suddenly bash will not start in terminals. Therefore no
PSI is set and commands I have in ~/.bashrc are not known unless I type bash
in
xterm after which PSI is set as well.
If I open xterm with: "xterm -e su -l" it opens with bas
