Message-ID: <465B645B.2060004@gmail.com>
Date: Mon, 28 May 2007 17:23:07 -0600
From: morgan gangwere <0 DOT fractalus AT gmail DOT com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: registry's role, or "must I install on client madhines"
References: <46544911 DOT 4000208 AT sgi DOT com> <20070523144101 DOT GB11579 AT ednor DOT casa DOT cgf DOT cx> <4655922E DOT 8040607 AT sgi DOT com>
In-Reply-To: <4655922E.8040607@sgi.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Joseph Michaud wrote:
> Christopher Faylor wrote:
>> On Wed, May 23, 2007 at 10:00:49AM -0400, Joseph Michaud wrote:
>>> I have cygwin installed on a Windows share.  I'm trying to use it
>>> from another Windows client machine (on which it was never installed)
>>> by simply running the bash executable using the UNC path
>>> (//share/cygwin/bin/bash.exe -l -i).  This isn't working.
>>> ...
>>> The only other thing I can think of is that the registry is
>>> being set up when you do an install and that these registry entries
>>> are required when bash is invoked.
>>>
>>> Are registry entries referenced when running bash?
>>
>> Cygwin, (somewhat) like linux, sets up a mount table which creates a
>> root directory, bin directory and other directories.  You can see what's
>> created by typing "mount".
>>
>> The fact that this information is stored in the registry is irrelevant
>> (and WILL change eventually).  You should use the mount command to
>> see how things are set up.
>>
>>> Is it possible to setup cygwin so that it may be used from a share
>>> without having been installed on the client machine?
>>
>> Possibly.  You don't absolutely need the mount table (with the possible
>> exception of /tmp) but, if you want to have bash set things up
>> automatically, you will need to investigate how bash works, set the
>> appropriate environment variables, and use the appropriate command line
>> switches.
>>
>> info bash
>>
>> may help.  Also check out "man mount" paying particular attention to
>> "mount -m".
>>
> 
> Bingo!  That's the trick.  As soon as I ran the appropriate mount
> commands on my client machines (specifying //share/cygwin...)
> everything worked.
> 
> Thanks.
> 
> Joe
> 
> -- 
> 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/
> 
> 

blxt?
windows has a way to make //server/share/ mounts look like g:\ filesystems
just open up Windows Explorer and check out "Tools/Mount Network Drive"
an easy hack to make the system coherent is to use some tool like
partitionMagic to make the boot drive something like "U:\" and have
cygwin installed in "U:\Cygwin\Cygwin" - on the client machines, mount
the network drive onto "U" and it'll run like a charm.

convoluted but failsafe

just a thought,
Morgan Gangwere
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGW2RbCF9T/dUsmAgRAmnXAJ9eMWiI/i5B7htbKA9Q8qyhHL4Z5wCffpJM
mc9iam95VCfxZzf4BlQGTt8=
=FNr3
-----END PGP SIGNATURE-----

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