Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Mon, 3 Mar 2003 19:27:40 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Robert Citek <rwcitek AT alum DOT calberkeley DOT org>
cc: cygwin AT cygwin DOT com
Subject: Re: Distributing .ISO files.
In-Reply-To: <3.0.5.32.20030303175336.01f35860@mail.earthlink.net>
Message-ID: <Pine.GSO.4.44.0303031921190.25599-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 3 Mar 2003, Robert Citek wrote:

> Hello Igor,
>
> At 06:42 PM 3/3/2003 -0500, Igor Pechtchanski wrote:
> >On Mon, 3 Mar 2003, Robert Citek wrote:
> >> [snip]
> >> In fact, I would have two items:
> >>   1) How can I redistribute Cygwin?
> >>   2) How can I create an ISO to redistribute Cygwin (probably a pointer to
> >> a how-to).  If there was a wiki or blog for this, I would be happy to
> >> contribute how I create my ISOs.
> >
> >You could simply send those instructions to this mailing list...  The FAQ
> >entry could point to your message in the archives.
>
> True.  But I'm hoping that someone will read my instructions on the web,
> laugh at them (and maybe at me, too), and make them better right on the
> spot.  Wiki is great for this.  In the mean time, I will write them up and
> post to the list.

Any corrections will also be sent to the list and linked with your message
into a thread.  The result will be not just the correct instructions, but
also the whole change history.  Can wiki do that? ;-)

Speaking of ISOs, I hope they include source... <http://cygwin.com/acronyms/#GPL>

> >You could also send a patch to the FAQ, of course.  The instructions for
> >getting Cygwin sources from CVS are at <http://cygwin.com/cvs.html>, and
> >the FAQ is in winsup/doc/faq.texinfo (and related files).
>
> I'm still getting my feet wet with the Cygwin sources, CVS, patch, etc.
> For example, I downloaded the setup module and compiled it.  Instead of a
> ~100 K file, mine was ~10 MB.  It seems to work, but obviously, I did
> something wrong.  Or is being off by 2 orders of magnitude "close enough?"

"man strip".  FYI, the stripped mingw-compiled setup.exe is just over 700k.

> >This is an open-source project.  It's much easier to get your changes
> >accepted here, especially if those changes are to the documentation (for
> >the better).  In fact, you could be awarded the honorable title of CTDW
> >(see <http://cygwin.com/acronyms/#CTDW>). ;-)
>
> Oooo.  I'll actually have a chance at being not just sexy but Ubersexy.
> Now that deserves some serious consideration.  :-)
>
> Regards,
> - Robert

Hey, it's working!  Great!  Gary, do you copy? ;-)
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


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