Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Mailer: emacs 21.1.1 (via feedmail 8 I) To: cygwin AT cygwin DOT com Subject: Re: clisp as a shell References: From: Guy Worthington In-Reply-To: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 Date: 22 Feb 2002 13:53:51 +0800 Message-ID: Lines: 45 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii I wrote >> I typed >> clisp -q >> and got the following screen dump: >> >> 23> clisp -q >> >> [1]> >> *** - UNIX error 13 (EACCES): Permission denied >> *** - UNIX error 13 (EACCES): Permission denied >> And somebody kindly replied offlist: > Hmm there is one tool somewhere that traces the system calls, maybe > can be used to see which files it can't access.. I scanned the mailing list using the keywords "Permission denied", but couldn't find anything pertinent in the first 20+ hits. Could I have a pointer to the name of the tool? As something that is probably irrelevant, while pottering around in bash, I typed the following commands: -------------------------------------------------- 11> cmd Microsoft Windows 2000 [Version 5.00.2195] (C) Copyright 1985-2000 Microsoft Corp. c:\Documents and Settings\guyw\Local Settings\Home>clisp -q clisp -q [1]> (quit) Bye. c:\Documents and Settings\guyw\Local Settings\Home>exit exit 12> -------------------------------------------------- This make me think that I can run a 'cmd.exe' inferior shell from within bash, that allows me to run clisp. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/