This is the mail archive of the
mailing list for the Cygwin project.
RE: Why does cygwin 1.1.2 hide /usr/bin?
- 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?
- From: Peter Ring <PRI at cddk dot dk>
- Date: Tue, 27 Jun 2000 11:00:42 +0200
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
From: Dave Arnold [mailto:email@example.com]
Sent: Tuesday, June 27, 2000 2:04 AM
To: Peter Ring; 'Ross Smith'; firstname.lastname@example.org
Subject: Re: Why does cygwin 1.1.2 hide /usr/bin?
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
Just curious, in case I decide to try this someday.
Want to unsubscribe from this list?
Send a message to email@example.com