Feature Branch - windows-NT/pwd.h windows-NT/unistd.h

Hi Derek, File windows-NT/pwd.h declares several functions that are declared in unistd.h according to the NetBSD man pages. Since I created windows-NT/unistd.c do you object in principle to migrations from pwd.c to unistd.c? If you agree, I'll enumerate the functions to migrate for review

Windows 2000 - HOMEDRIVE,HOMEPATH vs. USERPROFILE

Hi Derek, I ran tests on Windows 2000 and here's what I've learned so far: * User accounts have two flavors: Local and Domain * Both user account types support local or network user profiles * Both user account types support Home folder options * User profile type (local vs. network) seems

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.

Re: windows-NT/pwd.c - struct passwd - Home Directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Conrad T. Pino wrote: What I don't understand is why . is a reasonable home directory according to the getpwuid implementation: static char *home_dir = .; /* we feel (no|every)where at home */ I don't agree that it is. I think it was a poor,

Re: Feature Branch - windows-NT/pwd.h windows-NT/unistd.h

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Conrad T. Pino wrote: Hi Derek, File windows-NT/pwd.h declares several functions that are declared in unistd.h according to the NetBSD man pages. Since I created windows-NT/unistd.c do you object in principle to migrations from pwd.c to unistd.c?

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

Re: CVS update: /ccvs/windows-NT/sys/

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: #ifdef _MSC_VER #pragma once /* Compatable with Visual C++ 6.0 - cl.exe 12.00 */ #if _MSC_VER != 1200 #pragma message ( Please email Microsoft's sys/types.h ) #pragma message ( file to [EMAIL PROTECTED] ) #endif /* _MSC_VER

Re: CVS update: /ccvs/windows-NT/

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Log: * unistd.c, unistd.c: Add new usleep function using my_usleep logic taken from woe32.c file. * woe32.c, woe32.h: Add new (woe32_home_dir,woe32_shell) functions. * woe32.c: Modify woe32_nanosleep to use unistd.h

RE: windows-NT/pwd.c - struct passwd - Home Directory

Hi Derek, From: Derek Price What I don't understand is why . is a reasonable home directory according to the getpwuid implementation: static char *home_dir = .; /* we feel (no|every)where at home */ I don't agree that it is. I think it was a poor, arbitrary implementation decision

Re: OpenBSD 3.6 sparc64 stable crash

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tue, 31 May 2005 19:26:43 EDT Tue, 31 May 2005 19:26:30 EDT Alex Core was generated by `cvs'. Program terminated with signal 10, Bus Alex error. Alex #0 0x0014f148 in run_add_arg_p (iargc=0x7a8000, Alex iarg_allocated=0x7a8004,

Re: OpenBSD 3.6 sparc64 stable crash

[resend of message, unsigned because the gpg signing corrupted the patch.] Alex Core was generated by `cvs'. Program terminated with signal 10, Bus Alex error. Alex #0 0x0014f148 in run_add_arg_p (iargc=0x7a8000, Alex iarg_allocated=0x7a8004, iargv=0x7a7ff8, s=0x293838 diff) at

RE: CVS update: /ccvs/windows-NT/

Hi Derek, From: Derek Price Log: * unistd.c, unistd.c: Add new usleep function using my_usleep logic taken from woe32.c file. * woe32.c, woe32.h: Add new (woe32_home_dir,woe32_shell) functions. * woe32.c: Modify woe32_nanosleep to use unistd.h usleep. Glancing at lib/nanosleep.c,