X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4B055473.3010507@bonhard.uklinux.net> Date: Thu, 19 Nov 2009 14:21:39 +0000 From: Fergus User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Cygwin ML CC: Fergus Subject: Issuing commands at the command prompt Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com It is sometimes convenient to issue Cygwin commands at the Windows command prompt, without all the accompanying paraphernalia of formal setup, installation, mounting, etc. There are lots of examples (cat, diff, grep, md5sum, find, cmp, joe). As well as being convenient, it is easy, as long as all required .dll's are co-located with the .exe's, and the directory added to the Windows path. The "mount" command is included in this useful list. In [1.5] you can type "mount -c /" at the command prompt, providing a nice shorthand to access different drives. (Actually "mount -buc /".) In [1.7] the command generates no error message but in fact fails*, the cygdrive prefix remaining unaltered. I know the mount conventions in [1.5] and [1.7] are very different but is there any reason in principle why this could not be made to work in [1.7] as it does in [1.5]? *It works directly, if prefaced by the command bash to induce a bash shell, but this significantly detracts from its immediacy and therefore usefulness. Fergus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple