Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 19 Sep 2001 18:04:30 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Seeking Cygwin installer for the Message-ID: <20010919180430.D18115@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010919214928.25844.qmail@web20003.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010919214928.25844.qmail@web20003.mail.yahoo.com> User-Agent: Mutt/1.3.21i On Wed, Sep 19, 2001 at 02:49:28PM -0700, Joshua Franklin wrote: >Read my post again. I was working on less than 10MB network space. >The installer fits on a floppy. It's basically just the dll, ash, >bash, and a few shell-utils so that somebody can figure out what cygwin >looks like without having to do the big download. Doesn't even use >full packages. It would be pointless to put that kind of minimal >functionality into setup.exe Copy setup.exe, a modified setup.ini, and whatever other packages you need. You can create your own distribution. setup.exe just reads a simple ascii file and straight tar files. It sounds like you wouldn't even have to modify sources to do what you want. cgf -- 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/