X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 	tests=BAYES_00,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <26260476.post@talk.nabble.com>
Date: Sun, 8 Nov 2009 18:37:24 -0800 (PST)
From: aputerguy <nabble AT kosowsky DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: 1.7] Can you have multipe cygdrive path prefixes active at once
In-Reply-To: <4AF64144.8050000@veritech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <26227605 DOT post AT talk DOT nabble DOT com> <26227607 DOT post AT talk DOT nabble DOT com> <4AF3C9FE DOT 806 AT bopp DOT net> <26230853 DOT post AT talk DOT nabble DOT com> <4AF495B0 DOT 7090607 AT bopp DOT net> <26249511 DOT post AT talk DOT nabble DOT com> <4AF605C3 DOT 6050005 AT bopp DOT net> <4AF64144 DOT 8050000 AT veritech DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


Lee Rothstein wrote:
> Does this not do what's required (barring spaces in the
> "Cygdrive" alternative prefix):
>
> mount -p | gawk 'NR==2 { print $1 }'

Unfortunately, your method would fail if there were *any* spaces in the
pathname. Since regardless of what you say about the lack of "abject
stupidity" internal spaces are quite common in Windows (think 'Documents and
Settings', 'My Documents', 'Program Files', etc.) this would be a big and
potentially common miss.

I really think that mount should have a flag that lets you get the 'exact'
cygdrive rather than trying to parse some human readable version back into a
precise machine version.

More generally, it seems to go against the grain of the general *nix
philosophy to have a way of setting a parameter (in this case cygdrive
prefix) but not having a way to reliably read back that same prefix.

And regarding abject stupidity... *nix allows you to have some very weird
filenames (spaces, tabs, newlines, etc.) -- but there always seems to be a
reliable (though perhaps obscure) way to make sure you can recover or act on
the file name. Most importantly, in no case are you left with unresolvable
ambiguity.
-- 
View this message in context: http://old.nabble.com/1.7--Can-you-have-multipe-cygdrive-path-prefixes-active-at-once-tp26227605p26260476.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
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