*BSD News Article 2111


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!uunet!cs.utexas.edu!torn!cunews!knuth!ebx
From: ebx@scs.carleton.ca (edmond bo xiao)
Subject: Re: pwd, can't exec
Message-ID: <1992Jul20.172455.22802@cunews.carleton.ca>
Sender: news@cunews.carleton.ca (News Administrator)
Reply-To: ebx@scs.carleton.ca
Organization: School of Computer Science, Carleton University, Ottawa, Canada
References: <1992Jul20.121010.27904@Urmel.Informatik.RWTH-Aachen.DE>
Date: Mon, 20 Jul 1992 17:24:55 GMT
Lines: 22

In article 27904@Urmel.Informatik.RWTH-Aachen.DE, kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:
>When you type 'pwd' - and this is some kind of saying 'ahem' with your
>fingers - the system  responds with 'can't exec /bin/pwd'.
>After that a subsequent ls makes you think you have an empty directory.
>
>Only a ^C sends you back to 'normal life'. Anyone else observing this 
>and possibly having a cure for this behaviour?
> 

Yes, it heppened to me. But ONLY with Tiny386BSD. After I installed bindist
it's gone.

Another command I suspected different between Tiny386BSD and bindist
was 'shutdown'. I can do "shutdown -to386bsd' in Tiny386bsd but not 
'shutdown -todos' in normal 386bsd. Response was the command usage asking
a time of 'now' or '+n'.

edmond