help-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Changing user login shell to new bash release


From: Alex fxmbsw7 Ratchev
Subject: Re: Changing user login shell to new bash release
Date: Wed, 13 Oct 2021 04:06:15 +0200

when it doesnt work, like you describe, non working system
boot with init=/bin/bash or /bin/bash.bak1

On Wed, Oct 13, 2021, 04:05 Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com> wrote:

> well
> i dont say root, i say user
> but, old versions as u see are no good
>
> most scripts are
> #!/bin/bash
>
> that static path
> so look that that gets updated
>
> On Wed, Oct 13, 2021, 04:03 Khan Smith <khansmith@mail.com> wrote:
>
>>
>> *Sent:* Wednesday, October 13, 2021 at 1:54 AM
>> *From:* "Alex fxmbsw7 Ratchev" <fxmbsw7@gmail.com>
>> *To:* "Khan Smith" <khansmith@mail.com>
>> *Cc:* "help-bash" <help-bash@gnu.org>
>> *Subject:* Re: Changing user login shell to new bash release
>> look in /etc/passwd if the new path really gets used
>> or anyway on #! scripts u may only want /bin/bash
>>
>> so
>>
>> mv /bin/bash{,.bak1} ; cp /usr/local/bin/bash /bin
>>
>>
>> I never, ever change the root account's shell to be something other than
>> the system default.
>> If ever something goes wrong on my system that results in root's shell
>> being unavailable for
>> some reason, you've pretty much got a dead system at that point.
>>
>>
>>
>> On Wed, Oct 13, 2021, 02:06 Khan Smith <khansmith@mail.com> wrote:
>>
>> >
>> > I have system (Trisquel 9.0) with Bash Version 4.4.20. Have installed
>> > Bash 5.1.8 using
>> >
>> > cd build
>> > ../../../src/bash/bash-5.1.8/configure
>> > make
>> > sudo make install
>> >
>> > "which bash" is giving "/usr/local/bin/bash" and doing
>> >
>> > "/usr/local/bin/bash --version"
>> >
>> > gives
>> >
>> > GNU bash, version 5.1.8(1)-release (x86_64-pc-linux-gnu)
>> >
>> > To change my login I will be doing
>> >
>> > 1. Add /usr/local/bin/bash to the file /etc/shells"
>> > 2. Execute as myself the command "chsh -s /usr/local/bin/bash"
>> >
>> > Would the procedure be correct to do?
>> >
>>
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]