Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: localhost.localdomain: ronald owned process doing -bs Date: Mon, 5 May 2003 17:01:16 +0200 (CEST) From: Ronald Landheer-Cieslak X-X-Sender: ronald AT localhost DOT localdomain To: cygwin AT cygwin DOT com Subject: Re: Portable Cygwin on a CD In-Reply-To: <5iscbv435f123kdjetfe471ffvohcn7204@4ax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 5 May 2003, Sam Edge wrote: > Ronald Landheer-Cieslak wrote in > > in gmane.os.cygwin on Mon, 5 May 2003 14:26:12 +0200 (CEST): > > I'm thinking "autorun".. don't know why (yet).. > Nice idea. Thanks ;) > > > The whole shebang is initiated by simply putting the CD into any Windows > > > machine and "Run"ing the command > > This is where I start thinking "autorun" > > Would it be possible (my guess is that it certainly would) to make an > > autorun.ini file that runs a simple Windows program (compiled, say, with > > the -mno-cygwin option) that > > a. looks which drive it is on (in argv[0]) > > b. runs mount > > c. runs rxvt > This sounds eminently plausible. (Autorun.inf, by the way, not > autorun.ini.) Ah - guess I'm showing how little I'm used to Windows ;) > It should probably set CYGWIN and add x:\cygwin\bin to PATH in the > environment passed to mount and rxvt and should detect and warn about > any existing Cygwin mount tables before overwriting. (A tool or command > line switch to use umount.exe to remove all the mount settings it has > generated would also be good.) If there's already an installed Cygwin installation, the autorun shouldn't do anything, IMHO - unless it restores the mountpoints when it's done: you wouldn't want to break a perfectly good Cygwin installation just by putting a CD-ROM in your CD drive.. > > > mount: /: permission denied > > I *think* that is a question of the permissions you have in the registry - > > you'll need to use user mounts to take care of that (WAG) > For this application, it'd probably be best to put the whole mount table > in HKEY_CURRENT_USER e.g. to use the "--user" mount.exe switch. That > should prevent any permission problems. Yup (that's basically the same WAG as I had). Just remember the registry keys are not there to stay (but there will always be a way to find out where Cygwin lives, because Setup needs to know that too). I think it would be a very good idea to remove the mount table once you're done (and perhaps put the old one back if there was one). If the autorun program runs the bash or rxvt, it should be easy enough to clean up once it's done.. rlc -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/