public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Group Permissions on root folders problem (Windows 10 TP build 10061)
Date: Thu, 10 Sep 2015 17:27:00 -0000	[thread overview]
Message-ID: <55F1BD86.1090001@redhat.com> (raw)
In-Reply-To: <20150910172348.GB26699@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

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.000000000 +0900
>> +++ cygwin-service-installation-helper.sh	2015-09-10 18:16:38.185042300 +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,,*}" != "${LOGONSERVER,,*}" ]
>> +      if [ "\\\\${COMPUTERNAME,,*}" != "${LOGONSERVER,,*}" \
>> +	   -a "${LOGONSERVER}" != "\\\\MicrosoftAccount" ]
>>        then
>>  	# Lowercase of USERDOMAIN
>>        	csih_PRIVILEGED_USERNAME="${COMPUTERNAME,,*}+${username}"
> 
> Thanks a lot, much appreciated.  Patch applied.

[ ... -a ... ] is not portable; there are some inherently ambiguous
situations that it cannot handle. POSIX recommends that you spell it [
... ] && [ ... ] instead.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2015-09-10 17:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMH9mcFEL3mao+m-DEYM84kC1HOPeSBpZXD+mDf0USobF9oY7g@mail.gmail.com>
2015-06-16 13:23 ` Brian Buchanan
2015-06-16 15:58   ` Corinna Vinschen
2015-09-05  6:59     ` Takashi Yano
2015-09-06 11:44       ` Corinna Vinschen
2015-09-10 11:05         ` Takashi Yano
2015-09-10 17:23           ` Corinna Vinschen
2015-09-10 17:27             ` Eric Blake [this message]
2015-09-10 17:31               ` Corinna Vinschen
2015-09-10 17:36                 ` Eric Blake
2015-09-10 17:49                   ` Corinna Vinschen
2015-09-11  0:50                   ` Andrey Repin
2015-09-11  1:24                     ` Eric Blake
2015-09-11  2:05                       ` Andrey Repin
2015-09-11 10:04         ` Takashi Yano
2015-09-11 11:10           ` Corinna Vinschen
2015-09-11 12:33             ` Takashi Yano
2015-09-11 15:18               ` Corinna Vinschen
     [not found]     ` <DJzl1r0012qVqVd01Jzm3c>
2015-09-10 15:49       ` David A Cobb
2015-09-10 16:07         ` Ken Brown
2015-09-10 17:29           ` Corinna Vinschen
     [not found]         ` <FU891r01R2qVqVd01U8Bkq>
2015-09-10 20:41           ` David A Cobb
2015-04-29 14:45 Brian Buchanan
2015-04-30  8:24 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55F1BD86.1090001@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).