From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: rename a user using setfacl -- possible? how?
Date: Wed, 17 Jul 2019 01:52:00 -0000 [thread overview]
Message-ID: <5D2E7F4B.9020606@tlinx.org> (raw)
In-Reply-To: <2ac2d302-559c-b6ba-c7e2-5ec12e1683de@SystematicSw.ab.ca>
On 2019/07/06 10:01, Brian Inglis wrote:
> On 2019-07-06 10:01, Andrey Repin wrote:
>
>>>
>>>> It should, but I strongly suggest to avoid using it outside Cygwin directory
>>>> tree to maintain maximum interoperability with Windows programs.
>>>>
>>> No problem. my cygwin directory is at 'C:\', where it
>>> has been since WinXP... (:^|)
>>>
>> THAT is a problem. A big problem.
>>
----
Forgot to get back on this. But why would the above be a problem.
It never
used to be and I have found it to be very useful.
>>>> getent passwd
>>>> getent group
>>>>
>>> those don't display GUID/UUIDs, but *nix user+group ids.
>>>
>> Try it sometime. They do.
>>
>
> Try:
> $ id user|group
> and see below for getent nsswitch changes suggested.
>
----
I tried the above, BTW, and was surprised at the changes!
Had a related question. I made changes to my /etc/password and
/etc/group
files. I seem to remember how those files were read by cygwin when it
was first starting, but I don't remember how to propagate changes in
those files into
cygwin. Is there a way to send a command to one of the demons to reread
those files?
Thanks!
--
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
next prev parent reply other threads:[~2019-07-17 1:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 19:14 L A Walsh
2019-07-06 4:45 ` Brian Inglis
2019-07-06 9:20 ` Andrey Repin
2019-07-06 9:39 ` L A Walsh
2019-07-06 10:41 ` Sam Edge
2019-07-06 16:05 ` Andrey Repin
2019-07-06 17:01 ` Brian Inglis
2019-07-17 1:52 ` L A Walsh [this message]
2019-07-17 9:05 ` Andrey Repin
2019-07-06 19:41 ` Achim Gratz
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=5D2E7F4B.9020606@tlinx.org \
--to=cygwin@tlinx.org \
--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).