SciFi wrote:
> Bob Proulx wrote:
> $ strings bash | grep profile
> noprofile
> /etc/profile
> ~/.profile
> ~/.bash_profile
That looks good at least.
> > $ sudo chmod 0644 /etc/profile
> I *know* that!
> What I was striving for was to get at all the problems to be sure it
> is executable if need
Thank you for getting back to this.
Just a quick followup & acknowledgement,
then I will investigate details.
On Sat, 11 Aug 2007 18:22:44 -0600, Bob Proulx wrote:
> SciFi wrote:
>> Bob Proulx wrote:
>> > Is this a self-compiled binary?
>>
>> Yes, I do not use pkg-mgrs such as fink or macports,
SciFi wrote:
> Bob Proulx wrote:
> > Is this a self-compiled binary?
>
> Yes, I do not use pkg-mgrs such as fink or macports, maybe only for
> clues when a regular build bombs (straight from the tarballs).
If you have self compiled it then it should be possible to debug it.
What is the value of S
Hi and thank you for taking time.
On Wed, 08 Aug 2007 21:33:44 -0600, Bob Proulx wrote:
>
> SciFi wrote:
>> Got bash-3.2 patchlevel 17 running on MacOSX in place of Apple's:
>
> Is this a self-compiled binary?
Yes, I do not use pkg-mgrs such as fink or macports, maybe only for
clues when a reg
SciFi wrote:
> Got bash-3.2 patchlevel 17 running on MacOSX in place of Apple's:
Is this a self-compiled binary?
> I'm unable to get it to run the (login) startup files at all in any
> way-shape-form. If the startup file was being executed, the PS1
> prompt should change as a very visible clue (
Hi,
Got bash-3.2 patchlevel 17 running on MacOSX in place of Apple's:
-bash-3.2$ which bash
/bin/bash
-bash-3.2$ file /bin/bash
/bin/bash: symbolic link to `/usr/bin/bash'
-bash-3.2$ file /usr/bin/bash
/usr/bin/bash: Mach-O executable i386
-bash-3.2$ ls -al /usr/bin/bash
-rwxr-xr-x 1 root whe
