This is the mail archive of the
mailing list for the Cygwin project.
RE: Why the rash of people bypassing setup.exe to install?
- From: "Dieter Meinert" <DMeinert at RosenInspection dot net>
- To: <cygwin at cygwin dot com>
- Date: Mon, 17 Feb 2003 09:58:51 +0100
- Subject: RE: Why the rash of people bypassing setup.exe to install?
-----BEGIN PGP SIGNED MESSAGE-----
I was going through all this thread wondering if noone
would see the (to me as a late Un*x guy) obvious:
Consider a slooooooooooooooooooooow net connection, e.g by
14.4 K Modem, or as Hannu does,
several hosts to be updated. The natural thing to me
appears to download the tar file, unpack
it somewhere, probably on a CD, and then run setup on your
This would account for a load on the tar files while setup
isn't really triggered on the mirrors.
In this context I'd consider it a bad, at least confusing,
idea to rename the tar.bz2 files to something else.
|=> -----Original Message-----
|=> From: Hannu E K Nevalainen (garbage mail)
|=> Sent: Sunday, February 16, 2003 5:06 PM
|=> To: firstname.lastname@example.org
|=> Subject: RE: Why the rash of people bypassing setup.exe
|to install? =>
|=> > On Fri, Feb 14, 2003 at 05:31:05PM -0500, Rolf
|Campbell wrote: => > >Well, I maintain an internal mirror
|for my company, and => I use a custom
|=> > >python script to parse our custom setup.ini and
|fetch the needed => > packages.
|=> > >But, I never used sources.redhat.com.
|=> > So, translation: "I have no insight into the problem
|but => I thought I'd
|=> > send email anyway."
|=> > cgf
|=> Sorry Christopher, but did you really READ what he
|said: => AFAICT it is
|=> something like:
|=> I've got LOADS OF COMPUTERS(or some such) that I wish
|to => have fully updated
|=> CYGWIN installations on; this is what I've decided to
|do as => I feel it is
|=> Take a bunch of the above, running setup.exe on their
|own, => and all of the
|=> mirrors will have a huge network load when a number of
|=> updates appear.
|=> Here comes more of "I have no insight" to rant on; just
| => shoot (I wouldn't be
|=> too surprised as I haven't read much of the FAQ's and
|=> Seems to me as there is more interest in cygwin than
|you expected. => setup.exe COULD have some shortcomings
|here: e.g. the
|=> possibility to have a
|=> company-local "mini-mirror" that (updated by some kind
|of => scripting) can be
|=> used by local machines as source for updating the
|installed => cygwin copies.
|=> NOTE: "scripting" implies AUTOMATIC, e.g. with *no*
|user => intervention at
|=> To have the thing below work AUTOMATICALLLY, with
|minimal user => intervention:
|=> [cygwin mirror] --Internet--> [local mirror] --LAN-->
|[any => # of cygwin
|=> Another side of all this:
|=> Users tend to not read more than necessary. I've been
|=> there myself. Also
|=> taking note of how my friends and work mates act at
|these occasions. => The larger the amount of descriptive
|text you have the => larger the amount of
|=> FAQ's generated. In other words: I believe there is
|some => kind of quadratic
|=> (y=x^2) relation between README quality and FAQ amount
|;-) => [i.e. too little
|=> (or too much) text -> high amount of FAQ's]
|=> May I suggest that you(the cygwin dev group) add a
|bullet list on => www.cygwin.com in the following style,
|at the very top of the page: =>
|=> THE EASY WAY TO INSTALL CYGWIN
|=> 1 ) download "setup.exe" (Cygwin Package
|=> Manager or whatever)
|=> 2a) run "setup.exe"
|=> 2b) decide where to put "local mirror"
|=> (.e.g. C:\cygwin\mirror\)
|=> 2d) decide "which mirror" to get packages from
|=> (e.g. ftp://ftp.blah.net)
|=> 2d) hit "GO"
|=> At most FIVE items or so, I'd say.
|=> /Hannu E K Nevalainen, Mariefred, Sweden - undergrad
|who => shld be do'in his
|=> Unsubscribe info:
|http://cygwin.com/ml/#unsubscribe-simple => Bug reporting:
|=> Documentation: http://cygwin.com/docs.html
|=> FAQ: http://cygwin.com/faq/
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html