DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=WqMuJte5E5X+aj4+8o4ggmSK4xMZo8VdyQ6qkzU3Ek4wwbNGxOz6A
	Vr748efe1z4bjAJPifrrsZOB4irtGAo1WCJgLRkCsSymRGqusrvu11+J0moFk0HX
	z4ETc7AHVLnApj9BspC3WMEAArnzgUbwDgENLBfw0idIGX+xRY29d0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 10 Sep 2015 19:31:28 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Group Permissions on root folders problem (Windows 10 TP build 10061)
Message-ID: <20150910173128.GD26699@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAMH9mcFEL3mao+m-DEYM84kC1HOPeSBpZXD+mDf0USobF9oY7g@mail.gmail.com> <CAMH9mcFOKjvjiFvvk1ju0ZxBDK28MaktdnYwj5_CjvbgnpVO4A@mail.gmail.com> <20150616155843.GE31537@calimero.vinschen.de> <20150905155916.8403bea8d4f631c1f7a314e3@nifty.ne.jp> <20150906114444.GA27066@calimero.vinschen.de> <20150910200439.bf06449af4f1e6efcb76676e@nifty.ne.jp> <20150910172348.GB26699@calimero.vinschen.de> <55F1BD86.1090001@redhat.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="sXc4Kmr5FA7axrvy"
Content-Disposition: inline
In-Reply-To: <55F1BD86.1090001@redhat.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--sXc4Kmr5FA7axrvy
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sep 10 11:27, Eric Blake wrote:
> On 09/10/2015 11:23 AM, Corinna Vinschen wrote:
> > On Sep 10 20:04, Takashi Yano wrote:
> >> Hi Corinna,
> >>
> >>> However, I have not the faintest idea why the cyg_server stuff doesn't
> >>> work.  Anybody willing to track this down in the csih helper script?
> >>
> >> I had looked into csih script, and found a patch below solves
> >> the second problem.
> >>>> b) Creating sshd service using cyg_server
> >>
> >> --- cygwin-service-installation-helper.sh.orig	2015-02-24 04:57:56.000=
000000 +0900
> >> +++ cygwin-service-installation-helper.sh	2015-09-10 18:16:38.18504230=
0 +0900
> >> @@ -2867,7 +2867,8 @@
> >>      if ! csih_use_file_etc "passwd"
> >>      then
> >>        # This test succeeds on domain member machines only, not on DCs.
> >> -      if [ "\\\\${COMPUTERNAME,,*}" !=3D "${LOGONSERVER,,*}" ]
> >> +      if [ "\\\\${COMPUTERNAME,,*}" !=3D "${LOGONSERVER,,*}" \
> >> +	   -a "${LOGONSERVER}" !=3D "\\\\MicrosoftAccount" ]
> >>        then
> >>  	# Lowercase of USERDOMAIN
> >>        	csih_PRIVILEGED_USERNAME=3D"${COMPUTERNAME,,*}+${username}"
> >=20
> > Thanks a lot, much appreciated.  Patch applied.
>=20
> [ ... -a ... ] is not portable; there are some inherently ambiguous
> situations that it cannot handle. POSIX recommends that you spell it [
> ... ] && [ ... ] instead.

Does this matter in this very situation?  This is always running under
bash, btw.  Bash's a requirement for the csih helper script.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--sXc4Kmr5FA7axrvy
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJV8b5wAAoJEPU2Bp2uRE+gy/IP/jWJHtd06CYBZ2qpzKpHzx2B
otKfMBonmU4f7MkRZUD8hzJVeOGV8kkHyO1sATZTR5E80DqWhlQA/nn4Uk6Jo9nW
4yJMzeu3IQYgTLAs9Mq8RCT55CO3JRg/21ztuMOy8bBSmGprrEfIB9lNqtg0pad7
7AIt19uUJaLZXd9XUXpDHz4kyhP0xlT9kJNzQx4QZjlLFxbk221q8OkYR8ljPrwL
DoV/LVlAPaFajqQQlASHMTAN9R5xQL5D4755qzaxRQUwcQhFggZa3nbyD0D2UetV
+05yGa37tLXW3sJgKLIsXPqjbleuHIjMHw485lSpP5swH0HbVFn+KfKhw2ckrrPj
8U1uwLVasUn/zt8YAYWLtjp0K2cOXqGuY4KaAPNaKE4KRnwvFbZykKx5uJhPrYM2
800I4mDgBn1t5nWb7cskS3rvz5wj8tI6koa6SbdbRj5G/MH2EZk2ukca0SWZwkrM
ij86lNc2mx5x1FrIBoBoLGc1zhCzadRH7xE6V1NrVw854QIenyiNqh/tjuzbsoeY
hmO1i1TM76ex8n7mezmpf50lfvyDLtr4NBezD37nZPait3KvG2m28ESE1JCW7Toq
gS9bsLhll+0WL1r+lnhfGbDI3q6qpqTqDzKVZ9ukOQ2Qe16ArTuo1WnOO94PvPsN
VgfFlP8AJYGjN0GfH6Xd
=TnK+
-----END PGP SIGNATURE-----

--sXc4Kmr5FA7axrvy--