From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: network installation problems (again)
Date: Fri, 01 Jan 2016 23:06:00 -0000 [thread overview]
Message-ID: <5687068A.5040209@towo.net> (raw)
In-Reply-To: <56863C56.4040203@boland.nl>
Am 01.01.2016 um 09:44 schrieb D. Boland:
> Thomas Wolff wrote:
>> Hi,
>> I am again having problems to install cygwin on a network drive. It's
>> in the same network I had similar problems before:
>> http://cygwin.com/ml/cygwin-apps/2009-11/msg00034.html
>> which were then resolved after a while.
>> The client machines are now new, running Windows 7. Domain server is
>> the old one.
>> My description log of actions and popup errors is attached below.
>> There was no way to install on the network. I could install to the C:
>> drive and move that over to the network where it would then run.
>>
>
> Happy new year, y'all!
>
> You shouldn't try to install Cygwin on a network share and execute it
> locally. That's like installing and running Linux on a Samba share.
>
> If you want to use a single Cygwin distro on all computers in your
> network, you should install it on the target host, including the
> openssh daemon. Then on the client machines, you use Putty to log on
> to the host.
I need Cygwin on the network clients, not on a server (and this has been
working for years, just with occasional install problems).
Also (if I understand your first sentence correctly), I did not try to
install centrally for client use, but to install on a client for that
client's use, just on a network drive. And in fact that's the only
option on that system which is a lab network and the local (C:) drives
are cleared after each reboot.
------
Thomas
next prev parent reply other threads:[~2016-01-01 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 16:09 Thomas Wolff
2016-01-01 8:48 ` D. Boland
2016-01-01 23:06 ` Thomas Wolff [this message]
2016-01-02 8:26 ` D. Boland
2016-01-02 12:01 ` Thomas Wolff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5687068A.5040209@towo.net \
--to=towo@towo.net \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).