On 7 July 2016 at 08:06, Lisi Reisz wrote:
>
> So have you followed the suggestion to test whether it is in fact bash that
> you are in fact using?
>
> lisi@Tux-II:~$ echo $SHELL
> /bin/bash
> lisi@Tux-II:~$
In case anyone is unaware, it might be generally helpful to clarify what
this test actual
> On Jul 6, 2016, at 11:33 PM, Peter Ludikovsky wrote:
>
> No, chsh changes the login shell for the user within /etc/passwd. It
> won't affect any currently active shells.
>
> What happens when you do an
> /bin/bash --login
> That should start a login shell. If you still only get the tab
> cha
No, chsh changes the login shell for the user within /etc/passwd. It
won't affect any currently active shells.
What happens when you do an
/bin/bash --login
That should start a login shell. If you still only get the tab
character, check if you've got the line
set -o vi
in /etc/profile, /etc/ba
> On Jul 6, 2016, at 10:38 PM, Peter Ludikovsky wrote:
>
> After an chsh, you have to log out & in again.
I thought of that -- I logged out and back in, no joy. I rebooted, same thing.
I wasn't too surprised. I assumed that rebooting the machine would just put
stuff back the way it was. And t
After an chsh, you have to log out & in again.
Am 07.07.2016 um 00:17 schrieb Glenn English:
>
>> On Jul 6, 2016, at 4:06 PM, Lisi Reisz wrote:
>>
>> So have you followed the suggestion to test whether it is in fact bash that
>> you are in fact using?
>
> Yes. And I wasn't -- it was dash.
>
>
> On Jul 6, 2016, at 5:59 PM, deloptes wrote:
>
> What is the default for the user in /etc/passwd ?
Good question. Another very likely error. And I'd answer it if the massively
obsolete box wasn't powered down and in the give-away bin :-)
I'll look into it tomorrow.
--
Glenn English
Glenn English wrote:
>
>> On Jul 6, 2016, at 4:06 PM, Lisi Reisz wrote:
>
> There were far too many 'sh's in scripts in /etc, so I changes /bin/sh
> from pointing at dash to pointing at bash.
What is the default for the user in /etc/passwd ?
>
> That fixed it.
>
> Lisi, as usual, found the
> On Jul 6, 2016, at 4:06 PM, Lisi Reisz wrote:
There were far too many 'sh's in scripts in /etc, so I changes /bin/sh from
pointing at dash to pointing at bash.
That fixed it.
Lisi, as usual, found the problem :-)
--
Glenn English
> On Jul 6, 2016, at 4:06 PM, Lisi Reisz wrote:
>
> lisi@Tux-II:~$ echo $SHELL
> /bin/bash
> lisi@Tux-II:~$
Ahah! As root, echo $SHELL says /bin/bash. As a user, it says /bin/sh. And sh
is dash. That explains a *lot*. Maybe.
I'll see if I can find the dastardly script that does that.
Thanks
> On Jul 6, 2016, at 4:06 PM, Lisi Reisz wrote:
>
> So have you followed the suggestion to test whether it is in fact bash that
> you are in fact using?
Yes. And I wasn't -- it was dash.
So I:
'chsh -s /bin/bash'
'ls Do\t'
and got a tab.
> lisi@Tux-II:~$ echo $SHELL
> /bin/bash
> lisi@Tux-
On Wednesday 06 July 2016 22:52:58 Glenn English wrote:
> > On Jul 6, 2016, at 2:29 PM, Charlie Kravetz
> > wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > There should be a set of commands towards the bottom
> > of /etc/bash.bashrc to enable completion. The commands are
> On Jul 6, 2016, at 3:16 PM, Sven Arvidsson wrote:
>
> Are you sure that your user uses bash for the login shell? There was a
> transition from bash to dash some releases ago.
Nope. According to 'man sh', it's dash. I understood that dash is a fixed bash.
But why would it work for root and no
> On Jul 6, 2016, at 2:29 PM, Charlie Kravetz
> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> There should be a set of commands towards the bottom
> of /etc/bash.bashrc to enable completion. The commands are:
>
> # enable bash completion in interactive shells
> #if ! shopt
On Wed, 2016-07-06 at 14:29 -0600, Charlie Kravetz wrote:
> On Wed, 6 Jul 2016 13:48:24 -0600
> Glenn English wrote:
>
> >
> > I put wheezy on a 386 computer last night ('aptitude dist-upgrade'
> > from squeeze -- it'd been in the junk box for a while), and when I
> > hit tab, bash just gives me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 6 Jul 2016 13:48:24 -0600
Glenn English wrote:
>I put wheezy on a 386 computer last night ('aptitude dist-upgrade' from
>squeeze -- it'd been in the junk box for a while), and when I hit tab, bash
>just gives me a tab -- I have to type th
I put wheezy on a 386 computer last night ('aptitude dist-upgrade' from squeeze
-- it'd been in the junk box for a while), and when I hit tab, bash just gives
me a tab -- I have to type the whole command manually. This happens only for
the user; root works fine.
I've copied the .* scripts (the
16 matches
Mail list logo
