RE: Windows 2000 - HOMEDRIVE,HOMEPATH vs. USERPROFILE
Hi Derek, > From: Derek Price > > It sounds to me like we probably want to ignore USERPROFILE, then, and > just use the home dir settings. The commit characteristics of network profiles are indeed scary. Home directory commit characteristics are common to UNIX & Windows and seems the only choice to guarantee consistent behavior. The patch I'm working on supports compile time configuration and I recommend CVS Project not enable USERPROFILE support. > How does the home directory get set to > something other than "undefined" in your examples? The user interface is a dialog box tab sheet common to the workstation "Computer Management" and domain controller "Active Directory Users and Computer" Microsoft Management Console (MMC) applications. See the JPEG file attachment for the workstation dialog box. > Is there an API to > read it from the system or must all applications rely on malleable > environment variables for this information? An API must exist to support the MMC applications. I don't know if the API is public and it's querying security requirements. Local Administrator group membership is extremely common on workstations. Domain Administrator group membership is extremely rare. > Cheers, > Derek ___ Bug-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-cvs
Re: Windows 2000 - HOMEDRIVE,HOMEPATH vs. USERPROFILE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It sounds to me like we probably want to ignore USERPROFILE, then, and just use the home dir settings. How does the home directory get set to something other than "undefined" in your examples? Is there an API to read it from the system or must all applications rely on malleable environment variables for this information? Cheers, Derek -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (Cygwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCnK6RLD1OTBfyMaQRAnWqAKC/KHPySouyvYPIcS+eCfXAOnRXWgCfbjT0 whrOdCPGQpoGKGn1J85SME8= =4gdk -END PGP SIGNATURE- ___ Bug-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-cvs
RE: Windows 2000 - HOMEDRIVE,HOMEPATH vs. USERPROFILE
Hi Derek, A few more observations follow: > From: Conrad T. Pino [mailto:[EMAIL PROTECTED] > > > Based on these observations, how do Windows and UNIX differ to CVS? > > UNIX user profile (.profile,.bash_profile) files are always in $HOME. > > UNIX user profile changes are effective AND committed when changed. UNIX $HOME changes are effective AND committed when changed. > > Windows user profile is always local and independent of Home Folder. > > Windows Home Folder is synchronized with the user profile only when: > > Home Folder is undefined > Home Folder local path == %USERPROFILE% > > Windows user profile changes are effective when changed and committed > ONLY when user the logs off. The last sentence above needs clarification as follows: Windows local user profile changes are effective AND committed when changed. Windows network user profile changes are effective when changed and committed ONLY when user the logs off. Windows network user profile commits may not persist as expected when used on multiple machines: Login to workstation one, copy network profile to local drive. Login to workstation two, copy network profile to local drive. Modify user profile on workstation two. Logoff workstation two, copy local drive to network profile, network profile has workstation two modification. Logoff workstation one, copy local drive to network profile, workstation two modification to network profile is lost since the Microsoft help file says: If you use a roaming profile on more than one computer simultaneously, it will preserve the settings from the last computer that logs off. Windows Home Folder changes are effective AND committed when changed. > Conrad ___ Bug-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-cvs
