Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <00F8D6E8AB0DD3118F1A006008186C96035177@server1.axonet.com.au> From: Andrew Dalgleish To: "'cygwin-developers AT sourceware DOT cygnus DOT com'" Subject: RE: A trick for installing cygwin natively Date: Wed, 8 Sep 1999 13:43:51 +1000 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain > Yes. That's pretty much it. As soon as you install a cygwin1.dll in > your newly created /bin, Windows will try to use it iff you're also > running /bin/sh from that directory. If you aren't running any > programs from that directory then everything works fine. [Andrew Dalgleish] (Not sent to the list) So what are installing into /bin? Just the winsup files? I try to make everything match the spirit of the Filesystem Hierarchy Standard, but it doesn't mention cygwin1.dll :-) Cheers Andrew