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: <26249482.post@talk.nabble.com>
Date: Sat, 7 Nov 2009 15:02:43 -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: <4AF4AE6A.8000701@bopp.net>
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> <786EBDA1AC46254B813E200779E7AD36617A63 AT srv1163ex1 DOT flightsafety DOT com> <4AF4A495 DOT 3060108 AT bopp DOT net> <4AF4AB61 DOT 5040704 AT cygwin DOT com> <4AF4AE6A DOT 8000701 AT bopp DOT net>
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



Jeremy Bopp writes:
> The concern posed by the instigator of this thread is that it can't be
> known from the output of "mount -p" whether or not the spaces which
> follow the listed cygdrive prefix are part of the prefix or padding for
> the outputted columns.  It should be pretty rare that someone
> intentionally uses trailing spaces in their cygdrive prefix, but I can
> understand the desire for robustness.

Yes - that was precisely my point. I am updating scripts that are used on an
open source project so I want them to be robust. If it were just for my own
use, I wouldn't even need to use "mount -p" since I know what *my* cygdrive
prefix is. But if you are writing general scripts, I think it is pretty
reasonable and basic to have a clear, easy, and robust way to know what the
root of the system is. As an analogy, imagine if in Linux root were not
always "/" and that there were no good way to robustly determine what your
particular value of root was -- certainly that would break (or at least
potentially break) many scripts.
-- 
View this message in context: http://old.nabble.com/1.7--Can-you-have-multipe-cygdrive-path-prefixes-active-at-once-tp26227605p26249482.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