Thomas Wolff writes:
> Is there a canonical solution to this problem, other than running chown
> -R $USER ~ ?
Be careful with any recursive option, it can descend into paths you
really don't want it to go. If what you need to do is any more
difficult than just taking ownership using the new SID,
On 2017-12-07 00:50, Thomas Wolff wrote:
> I had to delete a corrupted Windows account and recreate it.
> For cygwin, the new account, although with the same name, has a different
> user id.
That id is the Cygwin hash of the Windows user id registry key; compare entries
from:
$ getent pass
On Dec 7 09:12, cyg Simple wrote:
> On 12/7/2017 2:50 AM, Thomas Wolff wrote:
> > I had to delete a corrupted Windows account and recreate it.
> > For cygwin, the new account, although with the same name, has a
> > different user id.
> > Of course, this creates access problems for existing files (
On 12/7/2017 2:50 AM, Thomas Wolff wrote:
> I had to delete a corrupted Windows account and recreate it.
> For cygwin, the new account, although with the same name, has a
> different user id.
> Of course, this creates access problems for existing files (even if they
> appear to have the same user i
4 matches
Mail list logo
