This is the mail archive of the
mailing list for the Cygwin project.
Re: UNC and POSIX paths
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 18 Jun 2013 10:36:44 -0400
- Subject: Re: UNC and POSIX paths
- References: <kpn4kk$p88$1 at ger dot gmane dot org> <036c01ce6b6d$0ada5090$208ef1b0$ at malth dot us> <kpnfp7$urd$1 at ger dot gmane dot org> <03b201ce6b83$c5b62720$51227560$ at malth dot us> <51BF534E dot 2030200 at cygwin dot com> <044001ce6bca$16c79ef0$4456dcd0$ at malth dot us> <20130618044230 dot GA6062 at ednor dot casa dot cgf dot cx> <048c01ce6be7$5aea3940$10beabc0$ at malth dot us> <20130618102632 dot GC27405 at calimero dot vinschen dot de> <20130618143009 dot GA5406 at ednor dot casa dot cgf dot cx>
- Reply-to: cygwin at cygwin dot com
On Tue, Jun 18, 2013 at 10:30:09AM -0400, Christopher Faylor wrote:
>On Tue, Jun 18, 2013 at 12:26:32PM +0200, Corinna Vinschen wrote:
>>On Jun 17 22:47, email@example.com wrote:
>>> On Mon, 17 Jun 2013, at 21:42, Christopher Faylor thusly quipped:
>>> > On Mon, Jun 17, 2013 at 07:18:12PM -0700, firstname.lastname@example.org wrote:
>>> >> BTW, along the same lines, I stated previously it would break
>>> >> http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob_plain;f=m4/doub
>>> >> le-sl ash-root.m4. Turns out I was wrong, the m4 has a hard-coded list
>>> >> of platforms. So, I have to say, I can't think of one technical or
>>> >> merit-based reason this shouldn't be done, aside from the fact that
>>> >> it's annoying to hear it endlessly brought up on the mailing list (a
>>> >> problem which an implementation would, in fact, solve, not exacerbate).
>>> > I can't quite follow the logic here but if you're saying that if we no
>>> > treated // as /, people who want to use //usr/local/bin would not
>>> > you're right. That doesn't mean that a whole new class of complainer
>>> would not
>>> > show up, however.
>>> > I can say with absolute certainty that there is one person who would
>>> I was imagining a less intrusive hypothetical approach.
>>> For example, perhaps a CYGWIN=nounc flag that would simply turn the feature
>>> off, or a way to deactivate in fstab -- in short, anything reversible, and,
>>> by default, preserving the existing behavior. Prune-grafting "//" to "/smb"
>>> might have been a good idea had it been done at cygwin's inception, but I
>>> think it's probably too late now.
>>A mount table approach along the lines of the cygdrive prefix handling
>>might not be such a bad thing, after all. Something along these lines
>> none /mnt cygdrive binary,posix=0,user 0 0
>> none /unc uncdrive binary,posix=0 0 0
>>This would also fix the somewhat special feature that unc paths get the
>>same default flag treatment as cygdrive paths.
>That's what I was proposing earlier in the thread. It's a SHTDI
>proposal, of course.
And, it nontrivially complicates path handling since we'd have to make
decisions about whether to honor // or not.
If we do consider this, I think we should take a step back and think
about revamping path handling to allow hooks for things like /dev,
/proc, /cygdrive rather than having to special case them.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple