Jasen Betts,
  In a message on 6 September, to Dave Kelly, wrote :

For 'fork()' and 'getpgrp()' see the previous message to
Christopher Butler.

JB> DK> #3.
JB> DK>         unlink (new_filename);
JB> DK>
JB> DK>         if (link (old_filename, new_filename) == -1) {
JB> DK>         ^^^^
JB> DK> Is this trying to verify that 'new_filename' has been deleted
JB> DK> from the disk, since it compares to less than. Could I use
JB> DK> 'access()' instead?
JB> 
JB> it appears to erasing new_filename, and then creating a link to
JB> old_filename called new_filename so that now both old_filename and
JB> new_filename refer to the same file.

OF COURSE! "Too many late nights staring at this screen."

To me and the OS I'm use to 'link' means attach. This function is
renameing the file. AND if I would just look at the name of the 
function I would realize that, "rename_file".

My C library does not have a 'rename()', however I do have a
command line process that will do just that, so I will write the function
thus and call it 'link'.

char *argblk[] = {
   "rename",
    0,
    0,
    0,
   };

int link( oldname, newname )
char *oldname, *newname;
{
   int Pid;

   strcpy( argblk[1], oldname );
   strcpy( argblk[2], newname );

   if ((Pid = os9exec( os9forkc, argblk[0], argblk,
                       enfiron, 0, 0, 3 )) > 0 ) wait(0);
   else
       printf( "Can not rename %s to %s\n", oldname, newname );
       return (-1);
}

DUH! And all this time I could have had a V-8.

Thanks for the feed back.  
...
 * ATP/OSK 1.40 * A rag of colts.
--- T.A.G. 2.7d Standard