When I'm ready to launch to 1.7, I'll start all over from the ground up.
Thanks for the hint about GID of 401. I've been using 401 for years. I
assumed that if installed from the ground up, I should have received a
warning abount GID of 401 conflict. An alternate, leave the conflict in
the group file with "mkpasswd" first then user will notice a problem
sooner. Thanks/
- Paul
On Feb 26 16:46, Paul McFerrin wrote:
Don't do that. Especially dont use 401 as gid. For the ownership of
the files the Cygwin uid/gid isn't important anyway. What's important
is that the SIDs are correct in passwd and group files.
When I'm looking at document:
http://cygwin.com/1.7/cygwin-ug-net/using-utils.html#passwd
it doesn't describe this procedure as what to do next when converting
an existing release to 1.7 ?? What next?? Remember, this was not a full
upgrade; just updating /bin/cygwin1.dll. I have not made a commitment
to do a full upgrade to 1.7 yet.
Don't do that.
I suggest to install 1.7 from scratch. A 1.7 installation can live
parallel to a 1.5 installation on the same machine, installed in another
directory (say, c:\cygwin-1.7), and even run parallel. 1.5 based
processes won't see 1.7 based processes running on the same machine.
After the new installation you should just check /etc/fstab and, if it
exists, /etc/fstab.d/Paul. Your 1.5 mount tbale will be imported and it
looks a bit strange to me. For instance, you're using / as cygdrive
prefix, which is not supported, and the following mount points
C:\cygwin\bin on /bin type system (binmode)
C:\cygwin\etc on /etc type system (binmode)
C:\cygwin\lib on /lib type system (binmode)
C:\cygwin\usr on /usr type system (binmode)
are superfluous and *might* break the 1.7 mount point import script.
Corinna
--
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/
