why bother with 'cd .' ?

why bother with 'cd .' ?

[Timothy J Luoma]

This seemed to confuse my /bin/sh:


cd . && \
  CONFIG_FILES= CONFIG_HEADERS=./config.h ./config.status
/bin/sh: .: bad directory


(now I can't tell you why it confused /bin/sh, sometimes it seems to work  
and other times it gives that error)


could we have something like

if [ "$PWD" != "$SRC_DIR" ]

	cd $SRC_DIR
fi

(using whatever the proper variables are)

It just seems like an unnecessary step which for some reason can cause confusion

TjL

Re: why bother with 'cd .' ?

[Bart Schaefer]

On Jun 1, 12:52am, Timothy J Luoma wrote:
} Subject: why bother with 'cd .' ?
}
} cd . && \
}   CONFIG_FILES= CONFIG_HEADERS=./config.h ./config.status
} /bin/sh: .: bad directory

There are two cases in which I've ever seen a problem like that.  First
is when I've had two shells running, and in one shell removed the current
working directory of the other shell.  The second is when the current
working directory is on an NFS filesystem that is "soft" mounted, and
the NFS server is having trouble (too heavily loaded, perhaps).

If you're seeing this intermittently in otherwise ordinary directories,
I suggest you get your filesystem fsck'd soon.

} could we have something like
} 
} if [ "$PWD" != "$SRC_DIR" ]
} 
} 	cd $SRC_DIR
} fi

It's $(dir_top), and the test would have to be [ $(dir_top) != . ], but
if you can't "cd ." then "./config.status" isn't likely to work either.

The whole point of using variables like $(dir_top) is so that the command
to be run doesn't need to care about the variable's value.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com