From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: Michael A Chase <mchase@ix.netcom.com>, cygwin@cygwin.com
Subject: Re: Where is the manual to manually install Cygwin in Windiows 2000
Date: Fri, 19 Apr 2002 12:33:00 -0000 [thread overview]
Message-ID: <4.3.1.2.20020419150707.02a3fd90@pop.ma.ultranet.com> (raw)
In-Reply-To: <E16ycs3-0006Ad-00@smtp6.mindspring.com>
At 02:12 PM 4/19/2002, Michael A Chase wrote:
>On Fri, 19 Apr 2002 10:23:56 -0400 "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> wrote:
>
> > At 09:45 PM 4/18/2002, Michael A Chase wrote:
> > >From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
> > >To: "George Hester" <hesterloli@hotmail.com>; <cygwin@cygwin.com>
> > >Sent: Thursday, April 18, 2002 18:09
> > >Subject: Re: Where is the manual to manually install Cygwin in Windiows
> > 2000
>
> > > > Really, there's really no *magic* to setup though...
> > >
> > >There are some mount points that _must_ be created for Cygwin to work
> > >reliable
> >
> >
> > I quite disagree with this point. If it were true, it would be
> > impossible
> > to move a Cygwin executable and the DLL to a machine without a Cygwin
> > install and have it work. This does work in the general case, though
> > there are specific packages for which it won't without additional
> > configuration (like the mount points you mentioned, mount type,
> > environment
> > variable settings, etc). But those are limited exceptions to the rule.
>
>Those limited exceptions generate a lot of "Cygwin is broke" messages like when
>a version of setup failed to create the /usr/bin and /usr/lib mounts a
>couple months ago.
Exactly. Which is why manual installation processes are a "use at your own
risk" approach. My point is, if you're so inclined, you *can* install
Cygwin and any of it's packages manually, without setup. Again, the only
reason I mention this is because there have been indications from folks on
this list that there is something which setup does that can't be reproduced
by any other mechanism. This is just plain false. However, I am in no
way encouraging people to use or generate an installation method other than
setup. Certainly, if one does so, this list cannot entertain questions
about installation problems based on such a procedure. I hope this message
and my previous response to this thread clarifies the installation issue for
those of all interests. I guess we'll see if that is indeed the case. ;-)
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
838 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-04-19 19:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 17:56 George Hester
2002-04-18 18:33 ` Larry Hall (RFK Partners, Inc)
2002-04-18 18:47 ` Michael A Chase
2002-04-19 7:30 ` Larry Hall (RFK Partners, Inc)
2002-04-19 11:22 ` Michael A Chase
2002-04-19 12:33 ` Larry Hall (RFK Partners, Inc) [this message]
2002-04-18 18:52 ` Where is the manual to manually install cygwin " Christopher Faylor
2002-04-18 18:46 ` Where is the manual to manually install Cygwin " Randall R Schulz
2002-04-19 5:49 Where is the manual to manually install cygwin " misi misi
2002-04-19 7:31 ` Larry Hall (RFK Partners, Inc)
2002-04-20 0:19 ` George Hester
[not found] <F68NIPukg3nOpj53XaD0000aad8@hotmail.com>
2002-04-19 9:44 ` Where is the manual to manually install Cygwin " Michael A Chase
2002-04-20 1:07 Where is the manual to manually install cygwin " Robert Collins
2002-04-20 11:11 ` George Hester
2002-04-20 11:26 ` Larry Hall (RFK Partners, Inc)
2002-04-20 16:04 ` Randall R Schulz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.3.1.2.20020419150707.02a3fd90@pop.ma.ultranet.com \
--to=lhall@rfk.com \
--cc=cygwin@cygwin.com \
--cc=mchase@ix.netcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).