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 Message-Id: <3.0.5.32.20030505074207.029745e0@mail.earthlink.net> X-Sender: rwcitek AT mail DOT earthlink DOT net Date: Mon, 05 May 2003 07:42:07 -0500 To: From: Robert Citek Subject: Re: Portable Cygwin on a CD Cc: In-Reply-To: <000701c312ef$08448da0$6fc82486@medschool.dundee.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hello Fergus, At 11:13 AM 5/5/2003 +0100, fergus AT bonhard DOT uklinux DOT net wrote: >I've a requirement, or at least, a desire, to run a Cygwin application >whilst sitting at other people's Windows machines, without formally >installing Cygwin on those machines. I was just thinking about something similar last night while putting PuTTY and FreeDOS on a USB stick: why not put cygwin on the stick? >The only not entirely simple aspect of the thing is, or seems to be, the >requirement to type the command > > mount -f "l:/" "/" > >at some point after starting up. I've tried any number of ways of automating >this to take place early in /etc/profile or ~/.bash_profile (mount -f >"$HOMEDRIVE" "/" or whatever, but HOMEDRIVE isn't known until it's mounted >...). The requirement for this line is basically that Cygwin needs to be >told the drive letter of the CD drive. (Or, if Cygwin doesn't, then system() >calls from within the application certainly do.) A couple of thoughts without testing: 1 - create a Windows batch file to set your environment before calling bash 2 - don't use a login shell I'll experiment on this end and share my notes if I discover anything interesting. >(Quick thought: if I put everything under l:\Cygwin rather than l:\, would >that make a difference at all?) Don't know, but don't see why that would make a difference. Regards, - Robert -- 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/