UNIX for Dummies Questions & Answers

The ln command creates a second entry in the directory table and gives it a new name. The i parameter to ls is reporting the inode start for each of the programs in the directory. If you just run ls -l, most of the entries have a number 1 in the second field but there some that have a higher number.

I see your ksh has four directory entries pointing to the same inode number (178). Try this command and post the output:

Code:

$ ls -li | grep "^ 178 "

It's possible that your sh program got renamed. This will show you all four directory entries that are pointing to inode 178. Mine are:

Code:

AIX:stctivprd01$ ls -li *sh | grep "^ 6340 "
 6340 -r-xr-xr-x   4 bin      bin          243428 Mar 03 2005  ksh
 6340 -r-xr-xr-x   4 bin      bin          243428 Mar 03 2005  psh
 6340 -r-xr-xr-x   4 bin      bin          243428 Mar 03 2005  sh
 6340 -r-xr-xr-x   4 bin      bin          243428 Mar 03 2005  tsh

So ksh, psh, sh, and tsh are all the same program.

The ln command will just add another entry to your directory and point it to 178. So run:

Code:

# ln ksh sh

And that will fix this aspect of the problem.

Carl

you are a star ! lol

that sorted the problem. i cant believe that sh is just a link/copy of ksh. so why would they run differently. i'm sure i read somewhere that these two were linked. wish i'd looked at that further.

it probably did get renamed but all ok now though.

man works as well !! lol

brilliant and thanks a lot mate. just gotta figure out how to rerun a command i've just typed in at the command prompt now - daft a lol

Well if you're running ksh, try:

Code:

$ set -o vi

Then you can just hit escape + k and scroll back through your commands

Happy to help.

Carl

thats great. can u just tell me what does set -o vi do???

its obviously setting some environment variable to the editor vi ??

only one other thing - i was still trying to make this monitor program but now im getting
==============================================================
# make
rm -f config.h 2> /dev/null
make all
cc -Dmon_notdef -DCOMPPROG=\"/usr/bin/gzip\" -DHIGHLIGHT=A_STANDOUT -
DMON_VERSION=\"2.1.9\" -DMON_DATE=\"26feb2001\" -o get_odm get_odm.c -s -lodm -D
MAIN
/usr/bin/sh: cc: not found.
make: 1254-004 The error code from the last command is 127.


Stop.
make: 1254-004 The error code from the last command is 2.


Stop.
#

actually -- just looked it up - doesnt this mean im missing the cc compiler ?? have tried running cc and gcc and getting "not found".

do i need to install it from somewhere then ?

set -o vi sets one of the ksh options. In this case it configures ksh to let you use vi like commands on the command line. So you can use the vi move commands to move around in your history. esc puts you into command mode. Then you can use the vi letters to move. k for up, j for down, h for left, l for right. You can also use several of the others. Search works too. Hit esc /for and you'll go back to the last command that began with 'for'.

If you're more familiar with emacs, you can use set -o emacs I believe and use emacs commands to move around.

Your make command shows you don't have a c compiler (which you noted). That's typical for most of the old school unixes (unices?). IBM may offer a freely downloadable c compiler. If not, you can go to the AIX tool site and probably retrieve the gcc compiler. I'm a Solaris admin mainly so I haven't had to use this site.

http://aixpdslib.seas.ucla.edu/index.html

Carl

thats great - cheers for your help Carl, has saved me having to look like a total idiot infront of my colleagues lol.

just a slight one :-)

i'll get the gcc and get that installed and go from there.

Many thanks again