At 07:55 AM 9/27/02 -0700, you wrote:
>>If he has made bash non-executable then I don't see how this will work either.
>
>I doubt the box will ever boot since /etc/inittab calls /etc/rc.d/rc.sysinit
>and the first line of sysinit is:
>
>#!/bin/bash
>
>or
>
>#!/bin/sh
>
>It is probably time to break out the alternative boot media and fix the file
>permissions...
>
>Two questions Alan:
>
>1) What dist. are you running?
>
>2) Is /bin/sh a hard link to /bin/bash? On my Mandrake boxes it is a soft
>link. (ls -i will show the inode number of the file)
>
>
>- --
>KevinO
>
>Matz's Law:
>~ A conclusion is the place where you got tired of thinking.
>
Insightful, Kevin.
I logged out of the computer and could not log back in. Permission errors
on bash. So the next time I try to boot it will have to be alternative
boot media, ie. a rescue CD.
To answer your questions:
1) Red Hat 7.3
2) Since I can't get to that box right now, I don't know. But checking a
box here at work, ls -l output is:
#ls -l sh
lrwxrwxrwx 1 root root 4 Jul 8 02:03 sh -> bash
#ls -l bash
-rwxr-xr-x 1 root root 541096 Apr 12 09:09 bash
So, what you are saying is that I changed bash to be non-executable? So
the procedure would be to boot from alternative media as root, get to the
/bin directory and change bash back to the correct permissions. Right?
Boy, I really should not be using chmod until I understand it!
Alan
(text/plain)