From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37918 invoked by alias); 5 Aug 2015 16:50:18 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 37904 invoked by uid 89); 5 Aug 2015 16:50:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=4.5 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: smtp.ht-systems.ru Received: from smtp.ht-systems.ru (HELO smtp.ht-systems.ru) (78.110.50.177) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 05 Aug 2015 16:50:15 +0000 Received: from [95.165.144.62] (helo=darkdragon.lan) by smtp.ht-systems.ru with esmtpa (Exim 4.80.1) (envelope-from ) (Authenticated sender: postmaster@rootdir.org) id 1ZN1tJ-0001cC-SE ; Wed, 05 Aug 2015 19:50:09 +0300 Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Wed, 05 Aug 2015 16:46:46 -0000 Date: Wed, 05 Aug 2015 16:50:00 -0000 From: Andrey Repin Reply-To: cygwin@cygwin.com Message-ID: <35586722.20150805194646@yandex.ru> To: "Kiehl, Horst" , cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.2.0-1 In-Reply-To: <3f1d63803e3546f28d65e0fc7957a204@IBTEXCHMB1.ibt.kfa-juelich.de> References: <55BFB64C.1010802@towo.net> <20150803192940.GA19315@calimero.vinschen.de> <895515CC-6BB7-41E7-AEA5-30FBBE071153@etr-usa.com> <87wpxac2bj.fsf@Rainer.invalid> <20150805075435.GP17917@calimero.vinschen.de> <3f1d63803e3546f28d65e0fc7957a204@IBTEXCHMB1.ibt.kfa-juelich.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-08/txt/msg00088.txt.bz2 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: > C:/foo > 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, Andrey Repin Wednesday, August 5, 2015 19:43:02 Sorry for my terrible english... -- 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