delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/01/08/13:16:32

From: cgf AT bbc DOT com (Christopher Faylor)
Subject: Re: combining mingw32 + cygwin32
8 Jan 1998 13:16:32 -0800 :
Message-ID: <EMH1nn.13n.cygnus.gnu-win32@bbc.com>
References: <199801080337 DOT DAA55538 AT out4 DOT ibm DOT net>
Reply-To: cgf AT bbc DOT com
To: gnu-win32 AT cygnus DOT com

In article <199801080337 DOT DAA55538 AT out4 DOT ibm DOT net>,  <vischne AT ibm DOT net> wrote:
>This directory hierarchy is also a useless appendage.  It's much simpler
>to set up a Unix file system on your C: drive, and do away with all that
>H-i386-cygwin32 excrement.  This is a Unix environment, and all the GNU
>utilities expect Unix directories.  So, why use the b18 directory structure,
>that corresponds to nothing in the real world?

I agree with this sentiment.  All of the *-i386-* stuff really complicates
things; especially if you are routinely switching between UNIX and NT.
Also, given the necessary amount of translation required for each component
of a path specification in cygwin32, every use of a subdirectory adds
an incremental time cost.

That's why I have my NT system set up to use /bin, /etc, /usr/bin,
/usr/local/bin, etc.
-- 
http://www.bbc.com/	cgf AT bbc DOT com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019