Re: [PATCH suggestion] mkpasswd: was "Re: Fw: After new install, start in /usr/bin/{myname} not in /home/{myname}"

On Thu, Jan 31, 2002 at 12:42:18PM +0100, Pavel Tsekov wrote: > > > Pavel Tsekov wrote: > > >Hello, Robert :) > > > >I've just tracked this problem. Here is what I've found: > > > >First of all the problem will appear on Win9x/ME only. > >In version 1.18 of mkpasswd.c the following change was >

[PATCH suggestion] mkpasswd: was "Re: Fw: After new install, start in /usr/bin/{myname} not in /home/{myname}"

Pavel Tsekov wrote: > Hello, Robert :) > > I've just tracked this problem. Here is what I've found: > > First of all the problem will appear on Win9x/ME only. > In version 1.18 of mkpasswd.c the following change was > made: > > - > - if (passed_home_path[0] == '\0') > - strcpy (passed_

Re: Fw: After new install, start in /usr/bin/{myname} not in /home/{myname}

Hello, Robert :) I've just tracked this problem. Here is what I've found: First of all the problem will appear on Win9x/ME only. In version 1.18 of mkpasswd.c the following change was made: - - if (passed_home_path[0] == '\0') - strcpy (passed_home_path, "/home/"); /* This takes Wind

Fw: After new install, start in /usr/bin/{myname} not in /home/{myname}

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 /