There is apparently a bug in mkpasswd. (I was tracking to see if setup.exe was the culprit).
On this machine (and others have been reported too) mkpasswd returns a
bad home path, which leads to somewhat strange behaviour.
The two attached cygchecks, from Fergus, show the environment with a bad
/etc/passwd (.chk) and with a good one (.out).
Hopefully this gives a clue as to why mkpasswd misbehaves, I haven't had
time to look at source yet.
Rob
===
----- Original Message -----
From: "fergus at bonhard dot uklinux dot net"
<[EMAIL PROTECTED]>
To: "Robert Collins" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, January 28, 2002 12:40 AM
Subject: Re: After new install, start in /usr/bin/{myname} not in
/home/{myname}
>
> > As for the incorrect /etc/passwd creation (which is IMO the actual
fault
> > you are seeing) can you send me the output of "mkpasswd -l"?
>
> Hey: interesting. Look at this:
>
> ~> mkpasswd -l
> Fergus::500:544::Fergus:/bin/bash
> ~> cat /etc/passwd
> Fergus::500:544::/home/Fergus:/bin/bash
>
> (This is _after_ I've edited the file /etc/passwd. In "failed setup"
mode
> the file /etc/passwd contains exactly the output from mkpasswd -l
above.)
>
> OK. Now I'll see whether I can be more ghelpful in describing what the
> prototype new setup.exe gives me.
>
> Fergus
>
>
cygcheck.out
Description: Binary data
cygcheck.chk
Description: Binary data
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
