Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <c=DK%a=_%p=CD-Danmark%l=CDDKSERVER-000627090042Z-1304@cddkserver.cddk.dk>
From: Peter Ring <PRI AT cddk DOT dk>
To: "'Dave Arnold'" <avr_fan AT mailandnews DOT com>,
        "'Ross Smith'"
	 <nospam2 AT pobox DOT com>,
        "'cygwin AT sourceware DOT cygnus DOT com'"
	 <cygwin AT sourceware DOT cygnus DOT com>
Subject: RE: Why does cygwin 1.1.2 hide /usr/bin?
Date: Tue, 27 Jun 2000 11:00:42 +0200
X-Mailer:  Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

In my case, "an existing installation" means a local NTFS volume with a
more or less FHS complying file hierarchy. I do not currently mount
anything into the cygwin file system except the root (I:\ becomes /) and
a number of NTFS volumes (so that, e.g., D:\ becomes /d). I install
native ports of TeX (MikTeX), GNU Emacs, Ghostscript, Python, etc. into
this file hierarchy in much the same way these applications would be
installed on a *nix box, e.g., emacs add-ons are located in
I:\usr\local\share\emacs\site-lisp, MikTeX generates fonts and format
files to I:\var\cache, etc. etc. Also, you'll find it is a lot easier to
install Cygwin/XFree86 if you have a 'normal' file hierarchy. Me think
life is simpler this way; why re-invent the wheel? 

We use GNU and open source utilities as parts of a publishing system,
and I'll eventually put most of the cygwin file system on a network
share in order to minimize local installation and maintenance. I'm also
very pleased with the development of inetutils and the support of NT
security (thank you, Corinna!); we are finally getting away from having
to install and run everything locally on each users' box.

The cygwin distribution tarballs usually have a sensible configuration,
with a slight tendency to use '/' as the prefix in case where I'd use
'/usr' (e.g., bison gets installed in /bin). I haven't had to move
things around. Anyway, the proper thing to do would be to recompile with
another prefix.

Kind regards
Peter Ring


-----Original Message-----
From: Dave Arnold [mailto:avr_fan AT mailandnews DOT com]
Sent: Tuesday, June 27, 2000 2:04 AM
To: Peter Ring; 'Ross Smith'; cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Why does cygwin 1.1.2 hide /usr/bin?


Question:

When you untar a package yourself, you mean you're untarring updated
files over an existing installation right?  Does the directory structure
of the tar files overlay correctly into the cygnus root directory? or do
we have to do some manual moving and copying of files to the correct
location?

Just curious, in case I decide to try this someday.

/Dave

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com