X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 19 Nov 2009 16:05:17 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Issuing commands at the command prompt Message-ID: <20091119150517.GH29173@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4B055473 DOT 3010507 AT bonhard DOT uklinux DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B055473.3010507@bonhard.uklinux.net> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Nov 19 14:21, Fergus wrote: > 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]? In Cygwin 1.7 the mount table is in /etc/fstab in the first place. The mount command does not change that file, rather, you have to change it using your favorite editor. The lifetime of re-mounts using the mount(1) command is the lifetime of the current Cygwin session of the current user. As soon as the last Cygwin process stops, the shared memory containing the mount points is destroyed and the changes are forgotten. The next Cygwin process starts with the automatic mount points plus the mount points from /etc/fstab again. It was the same when using the registry mount points in Cygwin 1.5, the only difference is that mount(1) does not change /etc/fstab, while the old mount changed the registry. If you want a user specific, persistent cygdrive prefix, just add a matching entry to the file /etc/fstab.d/$USER with $USER == the Cygwin user name of the current user. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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