This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1
- From: Andrey Repin <anrdaemon at yandex dot ru>
- To: "Kiehl, Horst" <h dot p dot kiehl at fz-juelich dot de>, cygwin at cygwin dot com
- Date: Wed, 5 Aug 2015 19:46:46 +0300
- Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1
- Authentication-results: sourceware.org; auth=none
- References: <announce dot 20150803131950 dot GA18878 at calimero dot vinschen dot de> <55BFB64C dot 1010802 at towo dot net> <20150803192940 dot GA19315 at calimero dot vinschen dot de> <loom dot 20150804T094839-714 at post dot gmane dot org> <895515CC-6BB7-41E7-AEA5-30FBBE071153 at etr-usa dot com> <87wpxac2bj dot fsf at Rainer dot invalid> <20150805075435 dot GP17917 at calimero dot vinschen dot de> <3f1d63803e3546f28d65e0fc7957a204 at IBTEXCHMB1 dot ibt dot kfa-juelich dot de>
- Reply-to: cygwin at cygwin dot com
Greetings, Kiehl, Horst!
> Corinna Vinschen wrote:
>> The problem the fix was *supposed* to fix (but it didn't) was to disallow
>> incoming $HOME values which are non-POSIX or non-absolute paths. These
>> $HOME values should be disregarded.
>> So the idea was:
>> set HOME=foo <- ignored, set HOME from passwd DB entry
>> set HOME=C:/foo <- same
>> set HOME=//foo/bar <- same
>> set HOME=/foo/bar <- valid, taken
> The second case, IMHO, *is* an absolute path in the context of Windows:
> So my assumption as a user would be that Cygwin would use this value for
> HOME in its (cygpath-) translated form: /cygdrive/c/foo
> This way I could continue to use my Windows profile directory
> (%USERPROFILE%) as my Cygwin home directory (with the definition of
> HOME=%USERPROFILE% and the symbolic link /home -> cygdrive/c/Users to
> keep ssh working)
Use fstab ?
C:/Users /home bind noacl,binary,exec,posix=0 0 0
> as well as e.g. continue to use the Windows port of
> GNU Emacs which consults the HOME variable too.
> In other words, if Cygwin would continue to use HOME=/cygdrive/c/foo as
> the conversion of HOME=C:/foo, this would follow the principle of least
> surprise, IMHO.
> (Just thinking ... would even the third case (HOME=//foo/bar) be a valid
> scenario? Does Cygwin "technically allow" the home directory to be on
> the network? If there is a POSIX-compliant translation of //foo/bar, it
> might be a better choice than ignoring the value.)
Technically, there's no restriction.
And I can imagine an AD environment, where it is actually desirable to have it
on the network.
With best regards,
Wednesday, August 5, 2015 19:43:02
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple