public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Harold L Hunt <huntharo@msu.edu>
To: cygwin@cygwin.com
Subject: Re: Cygwin CD question
Date: Mon, 13 May 2002 14:08:00 -0000	[thread overview]
Message-ID: <200205131853.g4DIr9k17100@pilot16.cl.msu.edu> (raw)

Larry,

Geez, you forgot to offer to sell him the Brooklyn Bridge, like I did :)

Harold

"Larry Hall (RFK Partners, Inc)" <lhall@rfk.com> said:

> At 02:31 PM 5/13/2002, William V. Nicholson wrote:
> 
> >I notice from the information on the Redhat website and in the FAQ that
> >there is no Cygwin CD.  I am interested in using Cygwin; but I don't
> >believe I require the Cygwin license for my applications.  I have
> >previously used Cygwin by downloading it; but I encountered some
> >difficulties with the setup program, especially for downloading source
> >code.  (It crashed when I chose the source code option for some packages.)
> 
> 
> If you haven't tried it recently, try it again.  Report specifics of any
> problems you may encounter here.
> 
> 
> >Actually, one reason that I am interested in using Cygwin is in order to
> >run free integrity checking software like Tripwire and ViperDB that works
> >under Unix.  (There is a Tripwire for Windows; but it isn't free.)  
> 
> 
> You must realize that Cygwin doesn't allow you to run a generic UNIX binary,
> right?  Cygwin is a layer over Win32 providing a POSIX environment, not a 
> UNIX binary emulator.
> 
> 
> >There
> >are security issues with downloading Cygwin before installing ViperDB or
> >similar software under Cygwin and that is why I am interested in obtaining
> >Cygwin by CD.  (My current workaround is just to download Cygwin using the
> >fastest connection available and then burn a CD although that doesn't
> >solve the problem with downloading source code),
> 
> 
> Actually, if you're having some problem with setup that can't be solved, you
> can download Cygwin in it's entirety using wget or similar tools.  From 
that,
> you can burn a CD and/or install locally.  Anyone providing such a CD to you
> would take a similar approach.
> 
> 
> 
> 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/
> 
> 




--
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-13 18:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-13 14:08 Harold L Hunt [this message]
2002-05-13 14:13 ` Larry Hall (RFK Partners, Inc)
  -- strict thread matches above, loose matches on Subject: below --
2002-05-13 19:45 Robert Collins
2002-05-13 14:02 Harold L Hunt
2002-05-13 14:58 ` William V. Nicholson
2002-05-13 16:29   ` cygwin " Christopher Faylor
2002-05-13 22:33     ` Gary R. Van Sickle
2002-05-13 13:11 Cygwin " William V. Nicholson
2002-05-13 13:25 ` Larry Hall (RFK Partners, Inc)
2002-05-13 14:50   ` William V. Nicholson

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=200205131853.g4DIr9k17100@pilot16.cl.msu.edu \
    --to=huntharo@msu.edu \
    --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).