public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Karr <davidmichaelkarr@gmail.com>
To: L A Walsh <cygwin@tlinx.org>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Win7 system update hosed something in Cygwin
Date: Sat, 17 Aug 2019 05:31:00 -0000	[thread overview]
Message-ID: <CAA5t8VoyaUfCef0dQ4cCwQimcJA-vCDvoDz8u9vPy5CPP5xKWg@mail.gmail.com> (raw)
In-Reply-To: <CAA5t8VqUViA6Ztx+5U-kcjTebXZ2QkvQnJcRkUGZF2irBdineQ@mail.gmail.com>

On Fri, Aug 16, 2019 at 3:33 PM David Karr wrote:

> On Fri, Aug 16, 2019 at 2:17 PM L A Walsh wrote:
>
>> On 2019/08/15 18:28, David Karr wrote:
>> > I logged into my Win7 laptop and I saw it was having some connection
>> > problems, so I decided to reboot.
>> >
>> > After the reboot I found that Cygwin had some basic problems.  I
>> brought up
>> > a mintty window (C:\cygwin64\bin\mintty.exe -e /bin/bash --login) and
>> the
>> > prompt looked odd.  It wasn't the PS1 value that I set in my .bashrc. It
>> > also seemed to be saying that my current directory was "/", which is
>> not my
>> > homedir.
>> >
>> You might want to read the section in the cygwin user manual, especially
>> https://www.cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping
>>
>> If you don't have /etc/passwd or /etc/group, cygwin will generate
>> DOMAIN+USER entries dynamically each time you start cygwin (or per-boot)
>> if you have cygwin processes started at boot.  The /etc/passwd and group
>> files do not exist by default.
>>
>> If you want consistency -- same user names+id's with each boot and
>> MS-Win compatible names, you may want to create /etc/passwd
>> and /etc/group using mkpasswd, mkgroup and hand tuning.  It isn't
>> suggested for most users, but it may be something you want.
>>
>>
> I would most like to understand what changed to make this suddenly start
> happening.
>
> Also note the following:
>
> $ mkpasswd -u <myuid> -d
>
> <myuid>:*:2993517:1049089:U-ITSERVICES\<myuid>,S-1-5-21-2057499049-1289676208-1959431660-1944941:/home/<myuid>:/bin/bash
>

Well, I guess I've managed to resolve this, but I would really like to
understand why I had to do what I did.  I basically ran both mkpasswd and
mkgroup, passing "-d -c"  and writing the output to the corresponding
passwd or group file, and then rebooting.  It now appears to work just as
well as it did before.

I've been running this Cygwin installation for a long time on this laptop
without any problem like this.

--
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

  reply	other threads:[~2019-08-17  1:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16  1:28 David Karr
2019-08-16  9:01 ` Houder
2019-08-16 14:48   ` David Karr
2019-08-16 15:16     ` Houder
2019-08-16 18:31       ` Houder
2019-08-16 18:47         ` David Karr
2019-08-16 18:45       ` David Karr
2019-08-16 21:01         ` Houder
2019-08-16 21:46         ` Andrey Repin
2019-08-16 22:33           ` David Karr
2019-08-16 21:20 ` L A Walsh
2019-08-17  1:23   ` David Karr
2019-08-17  5:31     ` David Karr [this message]
2019-08-18  6:04       ` L A Walsh
2019-08-17  7:11   ` Achim Gratz
2019-08-19 12:34   ` Andrey Repin
2019-08-20 18:02     ` Win7 update may create confusing Cygwin changes L A Walsh

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=CAA5t8VoyaUfCef0dQ4cCwQimcJA-vCDvoDz8u9vPy5CPP5xKWg@mail.gmail.com \
    --to=davidmichaelkarr@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=cygwin@tlinx.org \
    /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).