On Nov 11 11:05, Achim Gratz wrote: > Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes: > > One possible, but not naturally useful default behaviour is what > > the current code does: > > > > 1. Utilize the unixHomeDirectory AD attribute. > > 2. If unixHomeDirectory is empty, fall back to /home/$USER. > [...] > > Default to /home/$USER unless a specific AD attribute is specified in some > configuration file (maybe nsswitch.conf, maybe something else) and that > attribute is non-empty. > > > 1. Always use /home/$USER and let the admins come up with a matching > > mount point scheme. > > Would work for me, but then the configuration of those mount points would > need to be directable somehow. > > > Another: > > > > 1. Add a setting to /etc/nsswitch.conf which allows to specify one of > > the above: > > > > home: [unix|win|home]... > > > > - "unix" means, set pw_dir to unixHomeDirectory > > - "win" means, set pw_dir to homeDirectory > > - "home" means, set pw_dir to /home/$USER > > - Multiple entries are possible. > > - Default in the absence of this setting is: always set pw_dir to > > /home/$USER. > > Looks good, but maybe allow the AD attribute to be explicitly named (e.g. > cygwinHomeDirectory).
Cygwin schema extension? :) > For local accounts maybe some environment variable or > registry key should be available as a configuration option. I'm not that concerned about SAM accounts. Typically they have no problem with /home/$USER anyway, and they have the SAM description field to add cygwin-specific data. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpE01c0ou7c2.pgp
Description: PGP signature
