public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Keen Wayne A Contr AFRL/MNGG <keenwa@eglin.af.mil>
To: "'Larry Hall (RFK Partners, Inc)'" <lhall@rfk.com>,
	Keen Wayne A Contr AFRL/MNGG <keenwa@eglin.af.mil>,
	"'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: RE: Installing Cygwin from CDROM - Crude Method
Date: Thu, 30 May 2002 17:24:00 -0000	[thread overview]
Message-ID: <30C9E24891FFD411B68A009027724CB74433FE@eg-002-015.eglin.af.mil> (raw)



I guess I didn't make what I was trying to do very clear.
In light of recent....frustrations about using setup.exe,
to generate a Cygwin install CD, I took it as an
intellectual excercise to think of a really simple
way to do the operation, that works with common Windows
tools, and well, it works.

I went with an Explorer based approach to keep it point
and click.  I know there are much better ways to perform
ftp operations, but again I was trying to keep it simple.
I always kept my own limited mental capabilities in mind
here, so if it looks dumb, now you know why.

Wayne (the ultimate dummy test) Keen



-----Original Message-----
From: Larry Hall (RFK Partners, Inc) [mailto:lhall@rfk.com]
Sent: Thursday, May 30, 2002 12:52 PM
To: Keen Wayne A Contr AFRL/MNGG; 'cygwin@cygwin.com'
Subject: Re: Installing Cygwin from CDROM - Crude Method


At 01:28 PM 5/30/2002, Keen Wayne A Contr AFRL/MNGG wrote:
>A simple and crude method that appear to work for me for creating a Cygwin
>install CD for non-networked or classified (gulp) machines.
>(Warning, this is crude and takes some connect time. It involves less
>clicks though!)
>
>(1) I use explorer to go to the ftp side of my favorite mirror house.
>(2) I download the contents of the release directory into a release
>     directory in my cygtemp directory.
>(3) Once (2) is done, I copy setup.exe and setup.ini into my
>     cygtemp directory.
>(4) I burn the Cygtemp directory to CD.  I have been able to do
>     incremental (not full) setups on machines running setup.exe
>     from the CD.
>
>Again, this is crude, and takes some time (mostly unattended).
>The process (2) downloads everything, including source, so
>you end up downloading over 500 megabytes.
>
>I do find that when the ftp process dies (and it always does at
>some point for me), I find it fairly easy to see where it died,
>and restart it where it left off. (Funny note, after one of these
>restarts this morning, thje first estimate on download time
>was 1 day, 10 hours.....next was 5 minutes)
>
>Crude and unrefined, but it seems to work, and its easy
>to say "get everything", even for an IQ challenged Ph.D.


You might like wget then, if you get lots of disconnections.  It can
reconnect automatically and pick up where it left off.  A great time
saver for the highly automated! ;-)




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/

             reply	other threads:[~2002-05-30 18:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-30 17:24 Keen Wayne A Contr AFRL/MNGG [this message]
     [not found] <30C9E24891FFD411B68A009027724CB74433FD@eg-002-015.eglin.af .mil>
2002-05-30 14:35 ` Larry Hall (RFK Partners, Inc)
2002-05-30 15:06   ` Peter A. Castro
     [not found]   ` <Pine.LNX.4.21.0205301108530.21888-100000@gremlin.fruitbat. org>
2002-05-30 16:29     ` Randall R Schulz
2002-05-30 20:41       ` Peter A. Castro
2002-05-31  8:45         ` Michael Wardle
  -- strict thread matches above, loose matches on Subject: below --
2002-05-30 14:22 Keen Wayne A Contr AFRL/MNGG

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=30C9E24891FFD411B68A009027724CB74433FE@eg-002-015.eglin.af.mil \
    --to=keenwa@eglin.af.mil \
    --cc=cygwin@cygwin.com \
    --cc=lhall@rfk.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).