public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Urdaneta, Alfonso E (N-Summitt Technologies)" <alfonso.e.urdaneta@lmco.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: suggestion/rant re: install method
Date: Wed, 29 May 2002 10:38:00 -0000	[thread overview]
Message-ID: <83201DDE9625D611B09A00508BDF889E6795CC@emss03m04.orl.lmco.com> (raw)

I just tried to download and install cygwin - and I have to say the install
is highly frustrating.

While I understand the motivation for the granular installer, I think that
you should still provide the option of a monolithic download.  Unfortunatly
many of the "mirrors" that I had to chose from only mirrored a subset of the
modules that I needed to download for my full install.

I don't know how many times I had to deal with dialogs telling me "download
failed" and then choose a different mirror only to be told "the server has
an older version of setup.ini than the one you were using, continue ?",
forcing me to go through the installer over and over and over till finally I
now have a cygwin install that is about 80% functional, and I have to go
back over it and find all the pieces that didn't come down.

One thing that you guys may not have considered is that the current
"internet-only" method is unsuitable for classified environments.  I have
worked (and I'm sure I'm not the only one) in a "secure" environment which
does not allow a live connection to the internet.  In that sort of
environment we are allowed to stick CDs into the machine to install
software, but downloading is expressly prohibited.  

By refusing to provide a "monolithic install" option that users such as
myself can download and burn to CD to be used on non-networked machines, you
have essentially made cygwin a non-option for us.  

And please, any comments such "just plug it in for the download - a firewall
is more than adequate protection" are worthless - those of use that do
government work deal with beaurocrats, not reasonable technically compentent
human beings.  

Just an example - at my last government job I was not allowed to bring a
CD-RW into the lab even though all the machines had _only_ CDROM drives. (
yes, you read that correctly, read only drives NOT a writeable ones ).

I'm also concerned about the wasted bandwith and the delays induced by
downloading.  

I have a stack of CDs that I have burned with the tools that I normally
download such as gcc, xemacs, jdk, etc.  I use these whenever I setup a new
machine.  It seems that downloading 200-300M worth of stuff per machine is
ludicrous - especially if you are going to configure 20-50 developer
workstations, which I have had to do.  Seems like an excessive drain on your
mirror sites, and the internet in general.

Alfonso.


--
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/

             reply	other threads:[~2002-05-29 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 10:38 Urdaneta, Alfonso E (N-Summitt Technologies) [this message]
2002-05-29 11:43 ` David T-G
2002-05-29 12:35   ` Christopher Faylor
2002-05-29 17:31     ` David T-G
     [not found] <83201DDE9625D611B09A00508BDF889E6795CC@emss03m04.orl.lmco. com>
2002-05-29 12:34 ` Larry Hall (RFK Partners, Inc)
2002-05-30 11:26   ` Nicholas Wourms

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=83201DDE9625D611B09A00508BDF889E6795CC@emss03m04.orl.lmco.com \
    --to=alfonso.e.urdaneta@lmco.com \
    --cc=cygwin@cygwin.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).