Even if you reasonably well hide c:\program files from me, I still don't like
it. :)
> You should use the uninstaller to delete uwin since it will also
Both automated and manual uninstall have a tendency to leave stuff behind.
I know I'm taking some risk.
> The drives will become /x where x is the drive letter.
Understood.
I can/will also setup symlinks for common paths, so that my Win32 \dev2 is
/dev2 in UWin.
("dev" for development, but "dev" for "device" is already taken, oh well)
I don't know Cygwin went with such a verbose /cygdrive/c.
Maybe to allow for the file or directory /c that isn't the same thing?
I think MinGWin is same as UWin here, though using its runtime is discouraged,
it's really a Posix system only for building/running gcc, and then for building
native Win32.
I think Interix/ServicesForUnix uses /dev/something.
> native_command "$(winpath unixpath)"
Understood, thanks.
There this nagging thing that the systems are SO SO CLOSE in so many ways, but
yet not quite enough such as to be able to avoid translation to really handle
many important cases correctly. :(
For example "/" is a valid Win32 path that sometimes means the same thing as in
Posix, but not always -- i.e. on a single drive/volume system.
(and yes, I understand that even / on Posix isn't the root of a drive or
volume, but of a "namespace".)
> When in uwin, use UNIX conventions, for example> PATH is a colon separated
> list and / is the separator, not \.
Understood, thanks.
- Jay
> Date: Fri, 11 Apr 2008 21:33:07 -0400> From: [EMAIL PROTECTED]> To: [EMAIL
> PROTECTED]; [email protected]> Subject: Re: [uwin-users] non
> specific errors from uwin setup>
> [snip snip snip, quoted above]> > David Korn> [EMAIL PROTECTED]
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
