Quote:
Originally Posted by
methyl
@jlliagre
This is verifiable fact.
You misunderstood my reply. I was more commenting the "but not ksh" part of your sentence. Bash has indeed a character by character read feature, but as far as I know isn't "raw" in the sense it cannot read or store binary data (specifically nulls) so wouldn't be suitable for the expected task.
Quote:
The O/P states that bash is still working. I picked up the bash "read" idea from the IBM website after googling the library filename (which we finally got accurately in post #15). Found a thread where they were responding to someone in a similar situation. Renaming this library is a technique to get certain software such as Apache running on AIX when a replacement library is installed further down the library search path. However you have to do things in precisely the right order or you are in a mess.
Unfortunately the promising thread petered out when that O/P rebooted the computer and an unrelated can of worms opened due to having two system discs at different releases of AIX with the wrong one as the default boot.
Can you post a link to that thread ?
Quote:
I picked on "ftp" and "rcp" as ideas because they were not on a list I found of dependencies for the high level library. This does not mean that it will work, but it is worth a try. Given access to the O/S we could find out what libraries each binary requires and look for a loophole.
Either they bundle libc (i.e. are statically linked) or they are dynamically linked and obviously need libc.a which itself demand libcrypt.a. The OP stated there was no statically linked executables on that AIX release. This lead me to conclude that way can't work (just like mounting a removable media fails).
Quote:
On the permissions front we won't need execute permissions but we could need world read.
May be. That depends on AIX implementation. On Solaris shared libraries are required to be executable, on Gnu/Linux, they aren't.
Quote:
Depends on what the default umask is in the first place.
If setting the x bit is required with AIX, the umask won't help. "umask" allows to remove bits that otherwise would have been set, not the other way around. A shell do not create executable files.