> The -u flag to mkpasswd (and -g flag to mkgroup) are your > friends. See > the User's Guide. > > The thing is that if you're the only user in your domain using the > machine, you can simply run "mkpasswd -l -c > /etc/passwd" > (or "mkpasswd > -l -d -u YOURUSERNAME > /etc/passwd").
I did the variation with "-l -c" to recreate /etc/passwd, because "-d" would hang the shell. I also recreated /etc/group without all the domain stuff. Actually you are right, I am the only user of this machine. > > Incidentally, a group named "mkpasswd" does not exist. Do > you think I > > should do a chgrp to all directories below / which now have group > > mkpasswd? What group would be suitable? Maybe Administrators? > > Just bring your /etc/passwd and /etc/group files up-to-date. See > <http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-ids>. There is one sentence on this page which might be a hint to the problem in question: "if the login group of the current user isn't in /etc/group, it will be named 'mkgroup'" Now after recreation of group and passwd, I have: ~ $ id uid=121833(fischron) gid=10513(mkgroup_l_d) groups=544(Administrators),545(Users),10513(mkgroup_l_d) ~ $ grep fischron /etc/passwd fischron:unused_by_nt/2000/xp:121833:10513:fischron,U-EU\fischron,S-1-5- 21-2052111302-842925246-682003330-111833:/cygdrive/h:/bin/bash ~ $ grep 10513 /etc/group mkgroup_l_d:S-1-5-21-2052111302-842925246-682003330-513:10513: so I have now group mkgroup_l_d (I guess this should suggest "local domain"?), and not "mkgroup". Is this better? > I think your main problem wasn't with permissions, but with > postinstall > scripts not running properly. See if running them fixes the problem. Yes, I will, and keep the results posted. Ronald -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
