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
Message-ID: <000901c313d5$e9f1b700$6fc82486@medschool.dundee.ac.uk>
Reply-To: <fergus AT bonhard DOT uklinux DOT net>
From: <fergus AT bonhard DOT uklinux DOT net>
To: <cygwin AT cygwin DOT com>
Cc: <fergus AT bonhard DOT uklinux DOT net>
Subject: Re: Portable Cygwin on a CD
Date: Tue, 6 May 2003 14:46:36 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

The contributions over the past few days have helped a lot to make things
clearer, and better. Thank you.

1. There was a suggestion that the CD might usefully start with a
autorun.inf file. I feel a bit nervy about this. Two reasons: a. if the host
machine has Cygwin available then I would be inclined first to investigate
using that version, as the platform for any application I might be
interested in running; b. and if the host machine may even be _running_
Cygwin at the time the CD is inserted, what would be the potential confusion
arising from an autorun script which would be something like "\bin\rxvt -e
/bin/bash --login -i" or whatever?

So the way I've got things set up at the moment is rather meagre on the
automation. But it works (well, I think) as follows:

2. If the host machine does not have Cygwin, then insert the CD and

    Start -> Run -> f:\bin\rxvt {switches}-e /bin/bash --login -i
    mount -bfu f:/ /
    {do stuff}
    umount -A
    ^D

3. If the host machine does have Cygwin, then try starting it up, inserting
the CD, and

    cd f:/usr/local/
    {do stuff}
    ^D

which might work well, or not ...

4. In my case (and maybe others) this doesn't work at all well because when
I attempt to {do stuff}, things are in the wrong place. So instead I start
the host version of Cygwin with the intention of immediately (though
temporarily) disabling it and utilising the CD-bound "local" resource as
follows:

    Start the host version of Cygwin
    mount -m > a:/mount.tmp # or somewhere convenient
    umount -A
    {insert the CD}
    f:/bin/mount -bfu f:/ /
    {do stuff}
    umount -A
    f:/bin/bash a:/mount.tmp # to recover the host setup
    ^D

Personally I do not mind the explicit mount-ing and umount-ing, explicit
references to the CD driveletter f:, etc. Actually the thought of
irretrievably (or even retrievably) hosing the host Cygwin installation is
frightening enough to make this explicit rather mechanical approach
preferable to something automated, however elegant that approach would
undeniably be.

Fergus


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