On 2014-11-10 14:52, Corinna Vinschen wrote:
When I implemented the new scheme I thought it a good idea to decouple
the Cygwin home dir from the Windows home dir. However, in the today's
discussion the following two arguments came up:
- If you're using the Windows home folder setting to maintain file
server based home directories, you typically want that these
directories are used for Cygwin stuff as well (central administration,
central backup).
Having to maintain the home directories twice, once in the
homeDirectory, once in the unixHomeDirectory entry is quite a hassle,
especially given that unixHomeDirectory does not support variable
substitution (e.g. "/home/%USERNAME%" won't work).
- If you're already using AD as NIS server, unixHomeDirectory is already
used for UNIX machines. Trying to align the unixHomeDirectory for
Cygwin to homeDirectory for all the rest of Windows will potentially
become impossible then.
These arguments are quite serious and it questions the "good idea" part
of this change a lot.
What do you think?
Shall the "db" entries utilize the Windows home folder if it exits(*)
and drop using the unixHomeDirectory? It seems inevitable...
If one uses the same program, one native Windows and one Cygwin, they
would then potentially cause conflicting/incompatible config dot-files
in the same directory (line endings, path conventions, etc.).
Yaakov
--
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
