[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: #! /bin/sh bash problem
From: |
Bob Proulx |
Subject: |
Re: #! /bin/sh bash problem |
Date: |
Sun, 30 Mar 2008 11:45:21 -0600 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
John B. Brown wrote:
> Thank you for that reminder of my mortality.
:-)
> Bob Proulx wrote:
> >Also, /usr/bin/bash is not a normal location for bash. Normally bash
> >would reside in /bin/bash . Perhaps you also have one there?
> >
> > ls -ld /bin/bash /usr/local/bin/bash
I suggested looking at /usr/local/bin/bash since that is another
typical location.
> (23):% ls -ld /usr/bin/bash /bin/bash /usr/local/bash
> /bin/ls: cannot access /usr/local/bash: No such file or directory
It is probably not an issue here but you looked at /usr/local/bash
instead of where I suggested. It didn't exist. I doubt the
/usr/local/bin/bash exists either. But I wanted to note that these
were different paths.
> -rwsrwsr-x 1 root root 604040 2007-09-21 16:16 /bin/bash*
How did that happen? Fix that immediately, if not sooner.
chmod a=rx,u+w /bin/bash
Then also go check other files in your bin directory to make sure you
didn't have an errant command set them all.
> -rwxr-xr-x 1 root root 2037410 2008-01-30 05:35 /usr/bin/bash*
That looks okay. But it doesn't match your previous error message.
I assume you were continuing to make changes after your last message
because this one shouldn't have given a permission denied one. I
expected to see that this wasn't executable at all.
> Argh! I guess I get to REMOVE the bash I installed in
> error in that piece of junk location.
>
> So much for compiling by myself.
>
> I must remember to set the proper --prefix in the configure
> process; dueling bashes just doesn't make it.
Careful when compiling and upgrading systems in place. A breakage can
break your entire system to the point that you might not be able to
use it to fix itself. Make sure you have a rescue process available.
Bob