Re: problems w/ my MAC OS 10.5.7 unix?

On Jul 27, 6:56 pm, Dave Seaman <dsea...@xxxxxxxxxxxx> wrote:
On Mon, 27 Jul 2009 15:28:51 -0700 (PDT), Ken Quirici wrote:
Well I  tried 'ps' and all it showed was the korn shell - ksh.

All that tells you is that ksh was the only shell that was actually
running.  To see what other shells are available, you can try:

[Taurus:~] $ ls /bin/*sh
/bin/bash /bin/csh  /bin/ksh  /bin/sh   /bin/tcsh /bin/zsh

If ksh is your default shell, then you or someone did something to make
it so, because only tcsh and bash have ever been the OS X default shells.
You can change your login shell by using the "chsh" command. (man chsh)

I had read all this stuff on line saying the shell was bash and
downloaded (and printed - my bad) a couple of big
manuals. Live and learn.
So it's just korn?

Don't throw away those printouts.  You can make bash your shell.

That means there's no auto completion?At least there
wasn't last time I used korn on the job. But then what was
all that froofrah about getting auto completion (of a sort)
after escape THEN tab (there were those extra chars that
appeared - the ^[. My korn manual - the O'Reilly 'Learning'
from 1993 doesn't mention it. Guess it's time to visit
b&n or Amazon :-(
And what about using
./<executable-name> to execute a built executable?
That seem vanilla to y'all?

Yes.

Oh, one last thing (if you can stand it) - the auto completion
was presented not as a feature of the bash shell or korn
shell but of the version of Unix - it was definitely the
Open Source manual I was reading at the time.
The tutorial was the thng with the
./<executable>
Trying to find THAT lead me to the Open Source
Unix 03 and bash shell.

Autocompletion works in various ways.  Personally, I use the tab key
(under bash).

--
Dave Seaman
Third Circuit ignores precedent in Mumia Abu-Jamal ruling.
<http://www.indybay.org/newsitems/2008/03/29/18489281.php>

Man, that is something else! To fix it, I mean.

My ~/.profile was explicitly exec'ing bin/ksh. Fixed that. Now
autocompletion works like a charm. (I also did the chsh
thing - have to supply the full /bin/bash as the new shell,
but that also worked, except that it didn't start the shell - I
did that by fixing the .profile and running it. My prompt is
now bash-3.2$

Actually the ./ thing worked with the old korn shell, but I
want to know what's happening there so I'm going to
go over the manual, which I should do anyway. My big fat bash
shell manual :-) should help.

Thanks much!
.

Relevant Pages